Key takeaways
- The need determines how ADM work is configured.
- Strategy, portfolio, project, and delivery work should remain connected.
- Guardrails and experimentation can complement each other.
Four purposes of EA work
Architecture can support strategy by clarifying direction and capabilities needed over a longer horizon. It supports portfolios by connecting priorities, investment, and dependencies between initiatives. At project level, it defines the expected contribution, interfaces, and integration constraints. At solution delivery level, it provides conditions and decisions useful to implementation teams.
These purposes connect but need different detail and pacing. The ADM is configured to meet the need, using iteration and parallel work. A strategic horizon is not a fixed duration imposed by the method; it should fit enterprise decisions.
Architecture, agility, and digital enterprise
In a digital enterprise, architecture supports coherence, reuse, standards, and management of technical debt. It enables experimentation and learning rather than freezing every design choice before delivery. Design Thinking explores users’ needs; operational excellence remains essential to running services. Implementation guardrails make important constraints explicit while teams explore solutions. Agility can apply across the practice rather than only within Phase G.
- Connect products and change to business outcomes.
- Tailor the depth and duration of iterations.
- Reconsider choices using implementation and operational feedback.
TERMS TO KNOW
The terms, in context.
- Solution delivery
- Implementation of a solution under relevant architecture constraints.
- Technical debt
- Future consequences of implementation choices that complicate evolution or operations.