r/EnterpriseArchitect • • Oct 11 '25

r/EnterpriseArchitect is back

168 Upvotes

The sub was restricted for a while due to spam and low-quality posts. It’s now being reopened with a focus on quality, signal, and real-world discussion.

We want a serious, open community for practitioners working in or adjacent to enterprise architecture, people doing actual transformation, governance, and architecture work in complex organizations.

If that sounds like you:

  • Share your challenges and what’s worked in your org.

  • Ask questions that go beyond “what’s the best framework.”

  • Bring data, structure, and experience.

If you’re new: lurk first, read the room, and post when you have something to add.


r/EnterpriseArchitect • • Feb 05 '25

Passed TOGAF EA Practitioner in 1 week without classroom training

97 Upvotes

Just thought I'd share my experience (and humblebrag), I took the combined exam

Some time ago, I tried reading the TOGAF standard end to end, but gave up because it was so dry and theoretical. Then I saw EA in practice in my org, and it gave me a better context.

This time, I started with the official practice tests and answers (I searched hard online, you can also purchase them), and referred to the TOGAF standard / series guides along the way. This gave me a feel about what the exam was about.

Next, I used the Conformance Requirements https://publications.opengroup.org/x2202 to narrow down the material further, it is like the syllabus (learning outcomes) and references the relevant sections in TOGAF Standard and Series Guides.

Level 1 in the Conformance Requirements corresponds to EA Foundation (Part 1), while Level 2 corresponds to EA Practitioner (Part 2). Go through these, for Level 1 take notes (copy paste verbatim, don't paraphrase) and byheart them. Memorize the key diagrams. See what Part 1 practice test touches on and make sure your notes cover those. Level 2 is more of reading, understanding, and applying. IMO, Level 2 wasn't really useful, I just skimmed.

For Part 2 exam, I noticed in the practice test they always put the stakeholder first, any answer that doesn't put the stakeholder first should be downvoted. You should also ask yourself which phase you are in the ADM and not go and do something off tangent and illogical. I used the scratch pad during the exam to spell out why an option was not the best answer, narrowing down to the best option. I kinda winged Part 2 down to common sense, I did not fully read all the series guides... definitely go through the Part 2 practice test and answers to get a real feel.

Prep time: 1 week, not continuously
Result: Part 1 95%, Part 2 87%

YMMV

Now, on to the harder part of landing an EA role ;) Cheers


r/EnterpriseArchitect • • Nov 03 '25

Enterprise Architecture Cheat Sheets

90 Upvotes

Fairly new to enterprise Architecture, I'm wondering if anyone knows of any good reference guides or cheat sheets to help me better understand and navigate this role? I typically learn better starting from structured information into tables or diagrams as opposed to paragraphs of text.


r/EnterpriseArchitect • • Oct 13 '26

Passed TOGAF EA Foundation (OGEA-101) with 80% — sharing my study resources and preparation

76 Upvotes

Hi everyone,

I passed the TOGAF Enterprise Architecture Foundation (OGEA-101) exam today with 80%, so I thought I'd share how I prepared in case it helps anyone else studying for it.

I spent roughly 70 hours in total, including video courses, reading, revision, practice questions, and trying to understand the concepts rather than just memorising them.

Resources I used:

I completed these three Udemy courses:

  1. Enterprise Architecture: TOGAF® 10 Beginner to Practitioner! — QuinnTech Academy

  2. Standard 10.0 - Level 1 Enterprise Architect Course — Scott Duffy

  3. Practice Test Pack for the TOGAF EA Foundation Certification — Dr. Christopher Schulz and Tobias Smuda

I also used the GitHub repository "togaf-10-study-resources" by jules-tnk, which includes references to the official TOGAF 10 material and the Foundation Study Guide.

All of these should be easy to find by searching their names.

What worked for me:

  • Understanding rather than memorising. I focused on understanding the ADM phases, their purposes, and how different architecture concepts and deliverables relate to one another.

  • Practice questions. When I got something wrong, I tried to understand why the correct answer was right rather than just remembering the answer.

  • Revisiting difficult topics. I spent extra time on areas I struggled with instead of repeatedly going through everything.

  • Connecting theory to practice. Relating concepts to real-world architecture and technology decisions helped make some of the more abstract topics easier to understand.

My biggest takeaway was that understanding the terminology and the reasoning behind the framework helped much more than memorising practice questions.

I'm sure others have managed with fewer hours, but this was simply the approach that worked for me.

Not suggesting this is the best or only way to prepare, just sharing my experience in case someone finds it useful.

For those who've completed Foundation or Practitioner, I'm curious how much of what you learned you've found useful in your day-to-day architecture work.


r/EnterpriseArchitect • • May 10 '26 Bravo

Enterprise Architecture Reference Catalog

72 Upvotes

When I started the EA practice at my company, one piece of struggle was to build a capability map from scratch. I was fortunate to get some outside help with a consultant who provided their own, based on what they had on hand for this industry and that was enough to get us started. But what if you have nothing ? There’s no global reference catalog: it’s a bit spread apart when it exists and is sometimes gated or not in the right format.

So I decided to build my own and share it with the community for anyone struggling with that blank page :

https://catalog.turbo-ea.org

9300+ capabilities categorized by industry, 1200+ business processes, all exportable in csv to be imported in any tool.

The github repo contains the claude skill to generate them from scratch from any other industry and is self discovering/self grounding to industry standards and frameworks.

It will never be complete or perfect and has no pretention to be but it will always be better than starting with nothing.


r/EnterpriseArchitect • • Jan 17 '24

TOGAF Training Material

63 Upvotes

I've recently become a certified TOGAF Enterprise Architecture Practitioner and found whilst studying for this a lot of the material can be quite.... wordy. I'm a big fan of keeping things simple and so have attempted to produce some TOGAF content that looks engaging but is also informative as to what TOGAF is all about and some of the core concepts.Hopefully this is useful for anyone learning about TOGAF... if people find it useful I can continue doing more of these.


r/EnterpriseArchitect • • Mar 04 '26

I built a free open-source ArchiMate supply chain reference model — 267 processes, 41 capabilities, 70 views [GitHub]

62 Upvotes

The Archi EA tool has been available for over a decade. In that time, no one has published a professional-quality, downloadable .archimate file reference model that you can actually load into it and use as a starting point.

I built one. [.archimate file]

ORWiki is a complete supply chain reference framework modelled in ArchiMate. Based on the ORWiki Supply Chain Reference, the open documentation of the SCOR framework. Licensed CC-BY-SA 4.0.

What's in it:

  • 267 business processes across Plan, Source, Make, Deliver, Enable

  • 41 capabilities with CMM maturity levels tagged

  • 831 relationships modelled structurally (flow, realization, composition)

  • 70 navigable views

  • Every element has a SCOR-ID and provenance tag

Browse and download:
https://github.com/BoraPerzic/ORWiki

It's v1. The gaps are real and acknowledged: some descriptions are stubs, D5 Deliver Subscription is missing, and cross-domain flow coverage varies. I flagged the gaps rather than invented content to fill them.

I'm planning community sessions to work through what this model actually needs. Comment here if you want to be involved.

Happy to discuss design decisions, ArchiMate modelling choices, or what other frameworks would be worth building next.

What reference frameworks would you most want to see in ArchiMate? Genuinely asking.


r/EnterpriseArchitect • • Nov 03 '25

Architectural debt is not just technical debt

Thumbnail
frederickvanbrabant.com
62 Upvotes

This week I wrote about my experiences with technical and architectural debt. When I was a developer we used to distinguish between code debt (temporary hacks) and architectural debt (structural decisions that bite you later). But in enterprise architecture, it goes way beyond technical implementation.

To me architectural debt is found on all layers.

Application/Infrastructure layer: This is about integration patterns, system overlap, and vendor lock-in. Not the code itself, but how applications interact with each other. Debt here directly hits operations through increased costs and slower delivery.

Business layer: This covers ownership, stewardship, and process documentation. When business processes are outdated or phantom processes exist, people work under wrong assumptions. Projects start on the back foot before they even begin. Issues here multiply operational problems.

Strategy layer: The most damaging level. If your business capability maps are outdated or misaligned, you're basing 3-5 year strategies on wrong assumptions. This blocks transformation and can make bad long-term strategy look appealing.


r/EnterpriseArchitect • • Oct 14 '26

The Ivory Tower is Emptying

57 Upvotes

(Note: This article is entirely written by a human. Thanks.)

As with most job fields, Enterprise Architects have been spending a considerable amount of time in self-reflection about how AI is changing what we do. Underneath it all, were really asking ourselves if were even relevant in the Age of AI.

Any architect that has been around for some time knows that this isn't new to architecture or software. For decades, EA positioned itself as a team that were the gatekeepers off upfront planning cycles, rigid multi-year blueprints, and static artifact management. Though with the introduction of AI and how it is transforming the roles of the customers of those processes and artifacts, we have to ask ourselves how much of it still matters?

Here's what I'm seeing in Enterprise Architecture organizations in many industries, countries, and markets -

  1. Static artifacts aren't worth it.

Gone are they days we toil away perfecting the ultimate artifact. The One Diagram to Rule Them All, and in the darkness of a lack of maintenance will bind them (in indecision). It will always be useful to keep an unified perspective, especially for cross-functional teams as many don't have the correct mental model to grok the entire System. However our time spent on this unified perspective should ultimately disappear. Directly human-mutated code is beginning to give way to agentic coding, so these artifacts serve as decision drivers for humans and orientation for agents. Both can be automated.

2. Centralized Review functions doesn't work.

I know this is polarizing, but hear me out. I want to acknowledge that there are agentically-enabled organizations today that run a centralized architecture review function that works as intended. However, the intent of the centralized function is that a small body of people have the strategic perspective and the incentive for long-term thinking -- and in those organizations a staggering number of impactful decisions are being made in absence of that centralized body. When I say ARBs don't work, I mean they don't capture enough important decisions to meaningfully steer a company away from preventable tragedy. We acknowledge tragedy as a cost of business and never address the root cause consistently. The reviews we'll see will be mostly automated, and embed strategy and principles into the fabric of the software itself.

3. Architecture + Agile I do thoroughly enjoy Agile Architecture. In fact, I was first introduced to the concept on LinkedIn of all places. This I believe isn't contested ground, we all generally understand that rigid upfront compliance at milestone phases isn't a methodology that drives results consistently. Continuous assessment of what the project needs includes architectural compliance, and baking that directly into your agile practice nets huge gains.

4. Orchestration over Integration

I've been there, and most (if not all) of you have too. Huge system needs to plug into dozens of smaller integrations. Some upstream, some downstream, all headache. As agents take over more of the mutation effort, direct integration work is going to diminish significantly. Designing socio-technical frameworks that incorporate the autonomous AI and the context mentioned in #2 is where we find ourselves uniquely positioned to drive.

For over 50 years, Enterprise Architecture has been akin to 19th-century cartographers - meticulously sketching static parchment maps of a continent before an expedition. By the time the map was inked, the landscape had already changed. Today, we aren't drawing maps on parchment. Were in the cockpit with live satellite telemetry. Our jobs shifts from trying to predict every mountain and river in advance to building resilient flight systems, interpreting realtime data streams, and guiding the enterprise safely through uncharted terrain.

Embracing this shift requires us to acknowledge the usefulness of rigid frameworks in the past and look ahead to continuous, adaptive architectures. The end of an era is only the beginning of a new one! Ill be creating a series of articles on the Ages of Architecture where we unpack the journey architecture has made since the beginning in epochal shifts:

- First Age: Business Systems

- Second Age: Standardized Governance and Agility

- Third Age: Autonomous Intelligence

I always love reading the reactions and thoughts from people who made it to the end. Let me know if you're seeing the same thing or if there was anything I missed! Or if you think I'm full of crap, that matters too.


r/EnterpriseArchitect • • Nov 11 '25

Megathread - Frameworks, Courses, Certifications & Resources

52 Upvotes

Welcome to the r/EnterpriseArchitect megathread!

This is your one-stop destination for all questions and discussions about:

What Belongs Here

  • Framework questions (TOGAF, ArchiMate, etc.)

  • Course recommendations and reviews

  • Certification sharing (achievements, study tips, exam experiences)

  • Learning resources (books, videos, websites, tools)

  • Career advice and job hunting tips

Guidelines

  • Search first - Your question might already be answered below

  • Be specific - The more context you provide, the better the answers

  • Share your experience - If you’ve taken a course or cert, let others know what you thought

For highly specific topics that warrant their own discussion, feel free to create a separate post. Happy learning!


r/EnterpriseArchitect • • Jun 22 '26

Is anyone actually using an EA tool that doesn't cost a fortune and isn't garbage?

51 Upvotes

Here's my situation. I need a central app inventory, capability mapping, something to draw solution architectures that doesn't look like it's from 2005, and basic threat/control tracking so security stops asking me for spreadsheets every quarter.

We don't have the budget for a leanix or similar, and honestly we don't have the appetite for a 6 month procurement process that ends up creating more tool admin work than it solves.

But everything else I find online is either abandoned open source or some web app that looks nice in the demo and falls apart the moment you need to produce a real artifact for a SteerCo meeting.

Is anyone actually using something smaller that holds up in practice? I am genuinely curious what's out there that my team is not finding. Saw some pitches in this sub from a while ago but most of them seem quite abandoned. Also happy about any open source suggestions


r/EnterpriseArchitect • • Dec 02 '25

Choosing your starting line in enterprise architecture

Thumbnail
frederickvanbrabant.com
51 Upvotes

If you start up an enterprise architecture office, you have two types of strategies people use. Some people start by mapping everything that exists, in whatever state it happens to be. They then assess what they have and start building a gap analysis towards a better, more uniform state.

The other group of people start at the end point and work their way back. They sketch out the ideal state and map out the bare essentials towards getting there.

The big upside of the AS-IS approach is that you are working with terms and information that is familiar to the organization. People will recognize the works you are linking applications and business units to, as they probably use them themselves.

The idea of skipping the AS-IS altogether comes down to: why base our architecture on structures that are not only, very low quality, they are also probably not carried in the organization. The architecture maturity of the organization is probably very low, so why take on the burden.

My experiences has taught me mainly: If something already exists and people use it, adopt it. If everything is a mess and nobody agrees on anything, skip the archaeology and design something that makes sense to you.


r/EnterpriseArchitect • • Jul 05 '26

After 20+ Years in Enterprise Architecture, I Keep Having the Exact Same Conversations

50 Upvotes

I have two recent encounters/cases where I see that enterprise architecture as a discipline is either non-existent or not properly established. Let me lay out the context and issues and hopefully we can make some progress.

  1. Senior care corporation

The client is a senior care corporation operating more than 50 facilities, with medical staffing, logistics, operations, and all the complexity that comes with that business. The company grew from a handful of facilities to a multi-country operation. IT support grew organically and was never really planned. Management traditionally treated IT as "the guys who fix jammed printers."

Now that they have billing, accounting, payroll, training, HR systems, intranet, customer support, internal support systems, digital channels for patients and staff, integrated diagnostics, and healthcare management systems, managing and planning the application landscape is proving to be a serious challenge.

As an architecture consulting company, we proposed performing an analysis to capture the current systems landscape, map business capabilities and actual requirements, and create a gap analysis and roadmap to identify what systems are overpaid for, what capabilities are missing, and where investments should be made. Management largely perceives this approach as unnecessary overhead or lacks confidence that it would deliver tangible value.

What is particularly striking is that there is effectively no architecture governance in place. Decisions are made tactically, locally, and reactively. The organization has reached a level of complexity where organic growth and tribal knowledge are no longer sufficient, yet there is little recognition that architecture itself is a business capability that needs to be established and managed.

2. Global merchant acquirer

An established global merchant acquirer (card acceptance terminals, e-commerce, payment gateways, etc.) is undertaking several core systems migrations and replacements. Since these systems support core business capabilities, the impact and blast radius are enormous.

The interesting contrast here is that enterprise architecture teams do exist at the global corporate level. However, they largely function as governance document authors rather than active participants in delivery and transformation. They define standards, principles, and target states, but have little involvement in the trenches where critical architectural decisions are actually being made.

Problem-solving is handled by various layers of mid and senior management, multiple vendors, and delivery teams, but there is no effective architecture function coordinating target state, transition architectures, capability ownership, integration strategy, dependency management, or enterprise-wide risk assessment.

What strikes me in both cases is that the organizations are already paying the price of not having effective enterprise architecture, yet they still perceive investing in architecture as an additional cost rather than a mechanism to reduce risk, complexity, operational cost, and time-to-market.

I've been in so many of these situations throughout my career that I'm honestly baffled by how often I find myself participating in the exact same conversations. Different companies, different industries, different people—but somehow the conversations are almost identical, sometimes literally word for word.

My observation is that there is also a structural incentive problem:

- C-level management often does not fully comprehend the long-term implications of architectural decisions, technical debt accumulation, organizational complexity, and transformation risk.

- Mid-management is typically incentivized to deliver short-term outcomes and quick wins. Whether today's decisions create significant operational, financial, or technical problems five years from now is often somebody else's problem.

- Enterprise architects, when they exist, frequently end up either too far removed from execution to influence outcomes or too focused on governance artifacts to drive meaningful change.

It sometimes makes me wonder whether enterprise architecture has a value problem, or whether it simply has a marketing and communication problem.

At this point, I'm honestly more astounded, perplexed, and exhausted than curious. I've participated in these conversations so many times over the years that I'm genuinely baffled by how we keep ending up in exactly the same place, having exactly the same discussions, sometimes almost word for word.

I hear there is progress in enterprise architecture, but I just don't see it.


r/EnterpriseArchitect • • Jul 12 '23

Is anyone actually finding TOGAF useful, or even usable?

50 Upvotes

Hello,

I am trying to work my way thru TOGAF but I find it to be, at best, cumbersome and usually simply dangerous.

It seems, to me, what TOGAF is really good at is marketing. It is widely known and everyone uses occasional references. I find it highly inapplicable and highly useless when trying to have conversations with people. Especially gruesome is that one seems to require all kinds of reference material to have a conversation, for a conversation and effective communication people need to have a common vocabular.

  • Do people really believe that a standard, hundreds of pages long, is an appropriate framework toolset (they changed that!) for communication?

  • Am I the only one, and therefore most likely wrong, that thinks TOGAF is an abomination of a framework and it's only purpose is to generate cash-flow for The Open Group thru certifications? -- I hope I am wrong, I really do!

The EA roles I have been in where, exclusively, rooted in IT and I find it worrisome that we, as architects, move away from code and engineering. Yes, a huge part of our job is communication and simplification, yet I am concerned that the proverbial "ivory tower" is more of a reality than we like to admit. And TOGAF is a tool that, instead of removing it, embraces this ivory tower.

I see "solutions" left and right, not just in my organization, also from other organizations, where the architect draws shiny boxes and -- without any foundations -- says "This is now a solution". If you draw a box or design a solution you must be able to implement it. Yourself! Not by delegating, as an architect you need to be close enough to whatever solution you propose to actually make it happen.

No, not as a production ready state or system but at least to a state where you, yourself, ran into all the pain points and have refined your proposal to a point where it actually is a realistic approach to enhancing things.

I have not seen any resources in TOGAF, that point me to peer reviewed science, that are based on reasoning and evidence showing the toolset works. It's all self-referencing. There's no DOI or independent research that I can see that supports the applicability of TOGAF.

I'm at a point where I don't see anything in TOGAF that is applicable and useful outside of the select few that have a certification and spend their days a ... "specification" of several hundred pages.

Am I just blind and too stupid to find it?


r/EnterpriseArchitect • • Apr 03 '25

Accidentally ended up in an Enterprise Architect role and am quite frankly out of my depth

49 Upvotes

This feels a bit absured to type out but here we go.

I'm a Solution Architect with aspirations of eventually becoming an EA. I recently found a job, advertised as an SA, interview was a typical SA interview, and was lucky enough to get offered the job so accepted.

With week one out of the way, this is quite clear (to me) not an SA job at all, it's 100% an EA role. Don't get me wrong I am up for the challenge, but there is a massive disconnect between what was advertised and the expectations within the role. I am also the first architect within the organisation so perhaps their understanding of what an SA and EA does were misconstrued.

This notwithstanding, they seem like an excellent company to work for so I find myself 1. Wanting to give this a shot, 2. Nervous about this whole situation, and 3. Unsure of where to go from here.

I'm assuming the sensible option would be to vocalise these feelings and figure something out, however, that might end up being the end of my very short employment here.

Any suggestions/advice would be much appreciated.


r/EnterpriseArchitect • • Dec 20 '23

Passed TOGAF 10 combined 1 and 2 - Experience and tips

49 Upvotes

Recently passed the combined part 1 and 2 exams based on the TOGAF 10 standard and wanted to share my experience.

In terms of preparation I attended a 4 day course by an accredited TOGAF training partner. Once completed I read through the study materials provided and took the practice tests which I passed. Following this I took notes of all the study materials and focused on the areas I did not do well in the practice exams. Total study time including the training was about 5 weeks.

Here's some observations and tips

  1. I found the official practice exams much easier than the actual exam and could pass the Part 2 practice exam without needing the open book. Part 1 exam went into more detail when requiring to identify certain diagrams or definitions. Part 2 exam was much more difficult in both determining which phase the question is in and also choosing the answer.

  2. For Part 1 you can leverage the official practice exams for topics to study. For example if the practice exam has a question on principles, study that whole topic in detail. If the practice exam refers to a diagram also take a look at level 2 or 3 diagrams if they exist.

  3. Learn to navigate the TOGAF standard for the Part 2 exam. For me this was most critical of all for passing the exam.

  4. Once you have found the correct section in the standard compare the steps or artefacts produced with the answers. The answer which aligns best should be the correct one.

  5. Try and memorise every input and output of each phase including the artefacts that may be created that form the output for the phase. This will help you identify which phase the question is referring to.

  6. Don't skimp out on the security and digital transformation components. Both will be assessed and weaved into questions.


r/EnterpriseArchitect • • Aug 06 '26

Celebrating the Togaf certifications

47 Upvotes

I got it, folks! I actually passed the TOGAF Practitioner exam a few minutes ago, and I am so happy that I wanted to share it here.

For clarification: I sat for the Foundation exam last week and decided to take the shot and also sit for the Practitioner right after.

My take: the Practitioner exam was really hard. It took me almost an hour and a half to complete the 8 questions. I went through the official TOGAF Practitioner practice questions beforehand but still didn't feel fully ready. I honestly had a bit of a mental breakdown the night before because I couldn't find good study materials. My preparation had mainly been geared toward the Foundation exam, and I tried to explain everything to myself using scenarios to make it stick.

For everyone planning to give it a try: best of luck, and be prepared for completely crazy questions and not real-life situations.


r/EnterpriseArchitect • • May 16 '24

Podcast Enterprise Architecture

46 Upvotes

Hi All,

For those interested in continuous learning as an Enterprise Architect, I'm very proud to announce my Podcast on (Enterprise) Architecture.

I wanted to improve my skills as Enterprise Architect. And there was so much info, and also missing info. This is why I decided to talk to seniors or experts, and publish this in a podcast.

Heads-up: it's in DUTCH (for the time being).

If you are only english, you can subscribe to the LinkedIn newsletter (will also be on average 1 per month): https://www.linkedin.com/build-relation/newsletter-follow?entityUrn=7216922161544859648

Let me know if you are interested in this podcast, or maybe you want me to address certain topics? I'd love your feedback!

https://www.youtube.com/@verbonden/videos


r/EnterpriseArchitect • • May 30 '21

TOGAF 9 Part 1 and Part 2 Exam Experience

44 Upvotes

I recently completed both the Part 1 and Part 2 TOGAF 9 examination and I want to give a high-level overview of my exam experience and its difficulty.

TOGAF 9 Part 1 Exam

I used the TOGAF 9 Foundation (4th edition) study guide for passing the exam. The questions in the exam are similar in terms of its format and level of difficulty to the sample practice exam in the study guide. I did not use any other materials or practice questions to prepare for the exam. I spent about 3 hours a day for about 3 weeks to prepare for the exam.

TOGAF 9 Part 2 Exam

I used the TOGAF 9 Certified (4th edition) study guide for passing the exam. I found the exam difficult and challenging. The questions are 10 times more difficult to the sample practice exam in the study guide, so you will really need to be prepared.

Even though the exam is open book (part 2), trust me you will not have any time at all to refer the PDF book they provide because they really check your practical understanding of the various processes and concepts and how it can be used practically. Out of the eight scenarios they asked in the exam, I was only confident with one scenario in term of the answer. The other seven scenarios, I was only confident 60% in relation to my response. While you can easily eliminate two of the responses, the other two responses are remarkably similar. You really need to read and understand the question (look for key words) very well before selecting the BEST response that aligns to the TOGAF standard. I hardly had any time to refer to the TOGAF standard during the exam due to lack of time. I used the entire exam time to answer the questions. There were no tricky questions. The questions are all written very well and relevant. By the time I reached the 5th question, I assumed I failed, but I kept going. When the exam was complete, I did not want to check my result, because I thought I failed. To my surprise, I passed with 95%. I spent about 3 hours a day for about 4 weeks to prepare for the exam. I did not use any additional practice questions or books to prepare for the part 2 exam. I used my experience in EA, logic, and what TOGAF guide taught me to select the BEST response.

I wrote both the part 1 and part 2 exams separately. Hope my experience will help others.


r/EnterpriseArchitect • • Jul 13 '20

This sub has been rescued!

41 Upvotes

Hi everyone, I managed to rescue this sub as the original moderator had disappeared and the sub was restricted. I hope I'm not too late and the Enterprise Architecture community is still alive on Reddit.

The sub has now been re-opened.


r/EnterpriseArchitect • • Oct 31 '25

Value of an ARB

40 Upvotes

Curious question for the group - has anyone really felt that having an architecture review board has been beneficial in the long term? What are some of your cases that you've felt were successful and why? Did ARBs in your org cause any resentment from the tech teams? Or, did you find a valuable path?

I've been in multiple ARB formats either as a gatekeeper (yes/no - to the project moving forward) or as advisors on best practices. In all cases of ARBs I experienced - they became process overhead or were abandoned only to reappear again in another form due to leadership change. I have more opinions on this - but want to hear other's thoughts....


r/EnterpriseArchitect • • May 18 '25

Built a lightweight EA tool (MVP) – would love feedback from fellow architects

39 Upvotes

Update (Sept 2025): ArchiBuddy is no longer an MVP. V1 is live and ready to use. You can try it here: archibuddy.net. It's stable and feature complete for core EA needs. Would love to hear feedback from anyone giving it a try. What works well, what doesn’t.

Cheers!

====================================================================

Hi all,

Over the past year, I’ve spent evenings and weekends building a lightweight enterprise architecture tool. It’s a fully working MVP — not perfect, but functional — and I’d love for fellow architects, IT strategists, or product owners to take it for a spin.

Core features:

  • Application, process, and information inventory

  • Reporting tools like TIME portfolio analysis, cost analysis, information flow diagrams, and process vs app mapping

  • Natural language search and AI-based recommendations

  • A survey module to ensure data quality and completeness

I'm an enterprise architect consultant — I built this based on what I needed on real projects. Existing EA tools felt bloated, expensive, or overly complex. Archibuddy tries to do less — but make it easier to get started and actually use the data.

You can test it right away: archibuddy.net

Any feedback (good, bad, brutal) is very welcome. Just keep in mind: it's a solo project, so some rough edges are to be expected.

Thanks in advance!


r/EnterpriseArchitect • • Mar 06 '25

Did I F Up?

39 Upvotes

I thought architecture was going to be me working with people to deliver technology they need. Instead it’s writing shitty docs which no one reads and is there to tick a box.

Is this normal?


r/EnterpriseArchitect • • Sep 18 '26

Thrown into an Enterprise Architecture role with no guidance — where do I start?

37 Upvotes

So I recently got extended at my internship into what is essentially an enterprise-wide architecture role. My company has no EA currently, so No formal training, no one to shadow, and my manager basically told me to treat it like a doctor diagnosing a patient — talk to people every week, ask questions, and figure out how things connect. I have background in mainly operations / project management work.

The problem is I genuinely don't know where to start. I have access to stakeholders across multiple departments, but I have no clear picture of how everything connects — what feeds what, where data goes, what breaks when something fails. It more so I have to hear everything!

But I would love to know what skills are genuinely important to know and have as someone with absolutely 0 experience. I am willing to work and learn my a** off to understand everything, this is definitely something I want to pursue as a career as I have been trying to find my niche throughout college and this has hit that itch between tech and business.

A few questions for anyone who's been in a similar situation:

  1. How do you go about mapping an enterprise technology landscape from scratch when there's no existing documentation?

  2. What questions do you ask stakeholders to get the most useful information quickly?

  3. Is there a framework or methodology you'd recommend for someone just getting started in EA work — TOGAF, something else?

  4. How do you prioritize which systems and integrations to investigate first?

  5. Any tools you'd recommend for visualizing and documenting what you find?

  6. Anything fundamental I should know?

I'm genuinely figuring this out in real time and would love to hear from people who've navigated something similar — whether as a junior architect, a consultant dropped into a new client, or someone who learned EA on the job rather than through a formal path.

Thanks in advance