Enterprise Architecture has a reputation problem. Not because it lacks rigor or structure — quite the opposite. But because too often, architecture feels like something that exists next to the organization rather than within it. Diagrams live in tools, standards sit in documents, and architectural knowledge slowly fragments across folders, platforms, and people’s heads. It's kind of like an intangible scrapbook of past projects. The Architecture Repository, as described in the TOGAF® Standard, i…

Embarking on a career in Enterprise Architecture can feel a bit like being handed a map of a city you’ve never visited, and being told that every street, alley, and café is critical. You're then asked to solve a mystery. To put it in simple terms: starting your career in EA can be a challenge! There’s a lot to take in: frameworks, models, technologies, stakeholders, business strategies, and a universe of acronyms that seem to multiply when you’re not looking. If you’re just starting out in EA—or…

Enterprise Architecture has been around for decades. The discipline has profoundly shaped how organizations plan, align, and structure their strategies, systems, and operations. Frameworks such as the TOGAF Standard define four architecture domains and link them to specific architectural roles. While this approach has helped organizations organize work, it has also unintentionally reinforced rigid silos and limited the true potential of architecture as a holistic organizational capability.

The Architecture Development Method (ADM) of the TOGAF Standard describes a number of techniques a practitioner has at his disposal. Risk Management is the second-to-last technique that is described. Since it is addressed in several phases (Phase A and Phases E through H), it can be seen as an integral part of architecture development. Applying Risk Management techniques ensures that risks are identified, assessed, and mitigated as part of the architecture development process.

The Architecture Development Method (ADM) of the TOGAF Standard describes a number of techniques a practitioner has at his disposal. Risk Management is the second-to-last technique that is described. Since it is addressed in several phases (Phase A and Phases E through H), it can be seen as an integral part of architecture development. Applying Risk Management techniques ensures that risks are identified, assessed, and mitigated as part of the architecture development process.

Artificial Intelligence is often portrayed as a disruptive force — one that demands new methods, tools, and frameworks. But in practice, AI doesn’t replace traditional architecture frameworks. Instead, it enhances them. This is especially true when it comes to the TOGAF Standard’s Architecture Development Method (ADM). Rather than rewriting the playbook, AI can act as […]