Architecture 2 Outcomes.
A 5-pillar framework that brings business strategy and IT capability into the same workstream — until they converge on a single, executable roadmap. Every pillar produces a deliverable that leadership can sign off on. No deck-ware.
The standard EA approach is broken in three places.
After two decades of running enterprise transformations, we kept watching the same three failure modes — in different companies, different industries, different consultancies. A2O is the methodology we built to fix them.
Failure 1 — Top-Down strategy never meets Bottom-Up reality.
Most consulting engagements produce a strategy deck the IT department can’t actually execute. Or a technology assessment the business doesn’t read. A2O runs both workstreams in parallel from day one, and forces convergence at pillar 3 (Gap Analysis) before either side proceeds.
Failure 2 — Deliverables are documents instead of decisions.
Frameworks like TOGAF generate volumes of artifacts. A2O produces only what gets signed: an outcome-to-capability map, a current-state register, a gap register, a target-state design, and a 6-quarter roadmap. Five deliverables. Five signatures.
Failure 3 — Transformation ends when the consultants leave.
A2O builds the governance forum during pillar 5. The CIO and business sponsor inherit a working operating model with a KPI scorecard — not a binder. Execution outlives the engagement.
Each pillar. The artifact. The signature.
Business Outcome Mapping
The Top-Down workstream begins here. We sit with the executive sponsor, the CFO, the chief operating officer, and the lines of business. We ask one question: what outcomes is this business being measured on for the next 18 months?
Each named outcome — revenue growth in segment X, margin expansion in product Y, regulatory posture in jurisdiction Z — gets decomposed into the business capabilities required to deliver it. We use a structured capability ontology (BIZBOK-compatible, customised to your industry) so the same word means the same thing in every conversation.
- Deliverable: outcome-to-capability map. Each outcome shows the 6–12 capabilities it depends on, with capability owners named.
- Signed by: executive sponsor + CFO.
- Typical duration: 3–5 weeks.
Technical Inventory & Reality Assessment
The Bottom-Up workstream begins here. While the business workstream is mapping outcomes, our technical architects are walking the IT estate. Not the architecture diagram in the deck — the actual estate. Applications. Integrations. Data flows. Technical debt. Operating costs. SLAs. Vendor dependencies. Security posture. Cloud footprint. Talent reality.
We use automated discovery where we can (cloud asset inventories, dependency graphs, code-base scans) and structured interviews where we can’t. The output is unsentimental.
- Deliverable: current-state architecture register with technical-debt and risk overlays. Includes a colour-coded application portfolio (run / fix / replace / retire).
- Signed by: CIO + CTO.
- Typical duration: 4–6 weeks (parallel to pillar 1).
Gap Analysis & Capability Convergence
Where Top-Down meets Bottom-Up. The outcome-to-capability map (pillar 1) intersects with the current-state architecture register (pillar 2). The intersections are gaps — capability gaps, technology gaps, operating-model gaps, organisational gaps.
Each gap is quantified against the outcome it blocks: revenue at risk, margin impact, regulatory exposure, time-to-market delay. The ranking is brutal and useful. Leadership reads it and immediately knows what to fund first.
- Deliverable: ranked gap register with quantified outcome impact. Each gap shows the capability owner, the impacted outcome, the estimated cost of closure, and the cost of not closing it.
- Signed by: CIO + executive sponsor + CFO.
- Typical duration: 2–3 weeks.
Target Architecture & Operating Model
What the estate must become to close the ranked gaps. Not aspirational pictures — named technology choices, integration patterns, data architecture, security controls, and the operating-model changes (org, RACI, vendor model, governance forums) that have to accompany them.
Target architecture without target operating model is a fantasy. A2O forces both to be designed together.
- Deliverable: target-state architecture diagram + target operating model diagram + named technology choices with vendor analysis.
- Signed by: CIO + CTO + business sponsor.
- Typical duration: 4–8 weeks.
Transformation Roadmap & Governance
The execution plan. Quarter-by-quarter sequenced initiatives with dependencies, milestone outcomes, budget envelopes, and the governance forum that will review them quarterly. Each initiative carries the outcome it serves so the roadmap can be defended to the board on outcome terms, not technology terms.
We design the governance forum — the cadence, the membership, the decision rights, the escalation paths, the KPI scorecard — and hand it to the leadership team that will run it after we leave.
- Deliverable: 6-quarter executable roadmap + governance charter + KPI scorecard.
- Signed by: CIO + executive sponsor + CFO.
- Typical duration: 3–4 weeks.
One framework. Three engagement shapes.
Full A2O Engagement (16–26 weeks)
All five pillars, both workstreams, ending in the signed roadmap and governance charter. The most common shape for organisations facing a board-mandated transformation or compliance deadline.
A2O Diagnostic (6–8 weeks)
Pillars 1 + 2 + 3 only. Produces the outcome-to-capability map, current-state register, and ranked gap register. Useful when leadership wants to understand the gap before committing to a full transformation program.
A2O Embedded (12+ months)
WetzEnt architects embed in your transformation program office. We run the A2O governance cadence, refresh the gap register quarterly, and re-sequence the roadmap as the business changes. Used by organisations running multi-year transformations.