Key takeaways
- An enterprise is a set of organizations sharing goals, whatever their legal status.
- EA guides effective change, linked to strategy and value.
- Governing change means first directing it, then controlling it.
- Five benefit families: decisions, operations, digital, investment, procurement.
- Done too late, EA only documents decisions already made.
What TOGAF calls an enterprise
For TOGAF, an enterprise is any group of organizations pursuing shared goals. It is therefore not a legal notion: the scope can be a whole company, one of its divisions, an administration, or a single department, but also an alliance of partners linked by a supply chain.
The term may cover the enterprise as a whole (activities, capabilities, information, technology, and governance) or just one or more areas of interest. In every case the architecture spans several systems and functional groups, and it may include customers, suppliers, and partners. The operating model helps set the nature and extent of the EA. When a group contains several enterprises, each with its own EA, a common framework encourages shared building blocks and a common repository.
- A whole company or one of its divisions
- A government agency or a single public department
- Distant organizations linked by common ownership
- States or public bodies cooperating on shared infrastructure
- A consortium, an alliance, or a supply chain
What an Enterprise Architecture is for
EA exists to guide effective change. It turns a fragmented legacy of manual and automated processes into an integrated environment that can evolve and support strategy. It ties change to strategic direction and expected value, gives enough insight into the organization to manage complexity, and limits unintended consequences.
During implementation, stakeholders use it to govern: first directing change toward the best value-creating path, then controlling it so it does not drift. A good EA balances business transformation with continuous operational efficiency, lets units innovate safely, and helps meet personal data laws that require processing to be documented in a way non-specialists can read.
It must be involved early and throughout change. Done afterwards, it merely documents or enforces decisions already taken, without shedding light on their effects.
Five families of benefits
TOGAF groups the potential benefits into five families. All of them ultimately come from better planning, earlier visibility, and better-informed designs.
- More effective strategic decisions by leaders: agility, Digital Transformation, operating model changes
- More effective business operations: lower costs, shared capabilities, a more flexible workforce, easier integration after a merger
- More effective Digital Transformation and operations: interoperability, system management, easier component replacement
- Better return on existing investment and less risk for future investment: reduced complexity, freedom to make, buy, or outsource
- Faster, simpler, and cheaper procurement: a coherent plan, multi-vendor open systems
What triggers EA work
Reasons vary: a business initiative for transformation, a technology initiative for efficiency or consolidation, a merger or acquisition whose return depends on technical gains, or managing technical debt left by agile development. What they share is change affecting several interdependent systems. The architect then addresses stakeholder concerns: refining their requirements, producing views that show how they are handled, and making trade-offs between competing concerns visible.
TERMS TO KNOW
The terms, in context.
- Enterprise
- A set of organizations with shared goals; may cover the whole organization or an area of interest.
- Enterprise Architecture
- A discipline that guides enterprise change toward its objectives and strategy.
- Operating model
- How the organization works; helps set the nature and scope of the EA.
- Technical debt
- The future cost of design shortcuts, which EA helps identify and manage.