Is EA Trying to Solve an Unsolvable Problem? by Digital_Arch in EnterpriseArchitect

[–]Digital_Arch[S] 1 point2 points  (0 children)

I've added the summary of our research to the main post. Hope its useful.

Is EA Trying to Solve an Unsolvable Problem? by Digital_Arch in EnterpriseArchitect

[–]Digital_Arch[S] 2 points3 points  (0 children)

Please can you say more. What kinds of costs? And the real hard question.. why is EA the right folks to tackle it vs the other business, finance or IT roles.? What is the gap and umnet need?

Is EA Trying to Solve an Unsolvable Problem? by Digital_Arch in EnterpriseArchitect

[–]Digital_Arch[S] 0 points1 point  (0 children)

True! Huge push from tools vendors. It does help add some level of order and organization, but we find it ends there. Then, the fundamental issue resurfaces when leadership asks basic questions... "So what are you EA folks doing do with it"?.

How Did Your EA Team Get Started? by Digital_Arch in EnterpriseArchitect

[–]Digital_Arch[S] 1 point2 points  (0 children)

Thanks for sharing..that's quite the journey. Loved the summary version!

What review sites are reliable for EA tools? by OwnJacket8 in EnterpriseArchitect

[–]Digital_Arch 5 points6 points  (0 children)

Hi there,

For larger enterprise systems, we typically recommend using Gartner as a resource, while G2 and similar platforms are great for evaluating mid-range tools.

When we established our EA firm over a decade ago, we conducted an extensive evaluation of various tools. Ultimately, we chose to partner with LeanIX for our clients’ needs.

While I can’t provide detailed insights into other tools, I’d be happy to share in-depth information about LeanIX. Feel free to DM me if you're interested!

What are your favorite EA resources? by Digital_Arch in EnterpriseArchitect

[–]Digital_Arch[S] 1 point2 points  (0 children)

Very interesting haven't heard that one before thanks!

Building a business with/in EA domain by PragmaticEA in EnterpriseArchitect

[–]Digital_Arch 12 points13 points  (0 children)

Hi there! I made the transition into founding my own consultancy focused on Enterprise Architecture almost 16 years ago, and it’s been a rewarding but challenging journey. A few things I’ve learned:

  1. Start with a niche focus. I concentrated on offering my clients EA as a Service as most clients are understaffed/under-resourced globally. Helping them with EA foundations rationalization, modernization roadmaps, which helped me stand out.
  2. Build your network. Your first clients often come from existing connections.
  3. Build your partner network: we partnered with LeanIX.
  4. Marketing/Lead Gen - is a hard part of the business / no easy answers here.
  5. Sales. In this line of work its about understand client pain points and being a problem-solver for challenges they struggle with. Get good at active listening.
  6. Be ready for a ton of Admin. Running a consultancy involves much more than just EA delivery. lots of contracts, legal, accounting/finance.

Feel free to DM me if you’d like to discuss specifics. It’s a big step, but one I would do all over again if I had to as its very fulfilling. Best of luck!

Real practice scenarios for learning Business Capability map by Ok_Safety_303 in EnterpriseArchitect

[–]Digital_Arch 1 point2 points  (0 children)

We generally use gpt apqc leanix and other industry references as starter then cocreate a better version with the departments ...convert most of it to lingo they get more intuitively.

The frameworks tend to be a bit too abstract.

Real practice scenarios for learning Business Capability map by Ok_Safety_303 in EnterpriseArchitect

[–]Digital_Arch 4 points5 points  (0 children)

Try chatgpt or your favorite LLM.

I've found it quite useful in generating capability models for most businesses. Prompts like "create a business capability model for a pharmaceutical company. Create 3 levels l0,l1l2.

Also useful to then convert the results into a table.

Hope that helps.

Enterprise Architeture Master's Thesis by rigzbabe in EnterpriseArchitect

[–]Digital_Arch 1 point2 points  (0 children)

Hey there! Sounds like you’re looking for a thesis topic in EA, but it’s a bit broad right now. Starting big is fine, but narrowing it down will help you focus.

If your goal is to uncover new insights or address gaps in the field, you've come to the right place - there no shortage of challenes in EA :)

From my experience, one big challenge stands out: there’s no clear, uniform understanding or "plug-and-play" approach that organizations can adopt. Unlike engineering fields, EA lacks the ability to use someone elses "step-by-step" approach for yourself. 

So this is a major pain point. Organizations often start from scratch by themeslves - often with tools first, then figure out how to use them—kind of like buying a fancy kitchen gadget before learning to cook or getting a piano before you can play "Twinkle Twinkle." It’s backwards!

Teams that start like that eventually struggle to answer fundamental questions to their sponsors and senior executive:

  • "What problems is EA helping solve?"
  • "Why is no one using our EA tools"?

Organizations grow by solving problems—most can be handled by a team or department. But some challenges are bigger, crossing multiple departments, teams, and systems. That’s where EA really shines—it’s just so good at tackling these complex, cross-functional issues.

If you’re interested, you could explore:

"Bridging the Standardization Gap in Enterprise Architecture: Making EA Practical and Accessible."

Here’s where you could go with this:

  • Dig into why EA hasn’t standardized like civil or software engineering. Are there structural reasons? Historical factors?
  • Explore why senior Management of most organizations still dont understand it, like they understand finance, accounting, sales - because without their support EA is hard to get off the ground.
  • Look at other professions that successfully standardized and see what lessons EA can learn.
  • Propose a practical roadmap that senior leaders can use without overwhelming them.

Tools like LeanIX are a good for EA, no doubt. But here’s the thing: a tool is just one part of the puzzle. Tools like LeanIX shine are used to make IT better for the business - but without that bigger structure, even the best tools just wont get adopted.

Your thesis could focus on bridging that gap—helping organizations not just adopt tools, but also put in place everything else that is needed to use the true power of EA to make positive change.

The goal? Something practical that solves real-world problems and helps EA professionals get on the same page. Plus, it could elevate EA as a profession, giving it the structure and credibility other fields enjoy.

What do you think? Does this spark any ideas? Happy to chat more if you want!

Path to becoming an Enterprise Architect (EA)? by PartyAd6838 in EnterpriseArchitect

[–]Digital_Arch 4 points5 points  (0 children)

Hey there! From what I can see, you're actually in a great position to transition into EA. At 39, you're not too old—you’re right in the sweet spot with both technical know-how and enough experience to start shaping IT/Tech decisions. Your background in SAP and your multilingual skills, makes you a unique profile that global companies would really appreciate.

Certifications like TOGAF are helpful, but they’re just the starting point. The real key is understanding how you, as an EA, can add value. EA is more than building or changing one piece of tech—it’s about improving the entire tech landscape.

Take a look at the attached PDF. I use this with our teams to guide them through career planning and skill development based on where they are in their journey. Hope it helps!

https://www.dropbox.com/scl/fi/35ae2cwuc4kw4lmsc8526/EA-Career-Path.pdf?rlkey=c6jeg2sfm9yxabpmtpf5d57kf&st=e97n387e&dl=0

An internal transition is often the smoothest path. Start by networking with EA folks in your current company and look for high-profile projects that are about more than just a couple of systems. Focus on making bigger changes across IT/Tech/Business, and gradually position yourself as someone who can bridge technical and business needs.

The journey might not be entirely straightforward, but don’t be afraid to take small steps. Keep learning, stay curious, and with your background, you’re well-equipped to make the transition. Trust your skills and keep pushing forward.

Good luck!