Engagement 02
Capability Modelling
For organisations whose architecture estate has fragmented into PowerPoints, spreadsheets, and people's heads.
End-to-end consolidation of strategy, capability, value stream, and execution into a single coherent system. The classic enterprise architecture work — capability models, value streams, service blueprints, governance — executed by someone who has seen what goes wrong with each piece and built the practice to compensate.
Heads of architecture rebuilding a function that has drifted.
Programme directors who need a capability lens that survives quarterly portfolio review. Operating-model owners reconciling business architecture with technology architecture and finding the two no longer match. CDO/CTO partnerships trying to build a single data model that the business actually recognises.
Less useful if the goal is a model that lives in Confluence and stays there. The work assumes the model has to drive decisions — capability investment, portfolio prioritisation, governance trade-offs — and is built backwards from that requirement.
What surfaces.
Three different capability maps living in three different places, none of them authoritative.
Value streams that describe customer journeys but never connect to the capabilities or initiatives that change them.
Initiative backlogs where no one can say which capability each item builds, or which strategic outcome the capability moves.
Business architecture and technology architecture diverging because each team built its own model in isolation.
Architecture governance that blocks rather than enables, because the model it references doesn't represent how the business actually operates.
The Capability-to-Execution Blueprint.
The named deliverable is the Capability-to-Execution Blueprint — the single integrated artefact that links strategic intent to capability investment to delivery initiative. Components produced along the way:
Enterprise capability model
L1 to L4 depth, structured for executive readability at L1 and delivery-team utility at L4. Industry-aligned where appropriate.
Value stream maps
Customer journeys connected to the capabilities that serve them and the value-creating activities inside the business.
Domain-driven design
Bounded contexts, ubiquitous language, and aggregate boundaries for the complex domains where technical and business models have drifted.
Service blueprints
Front-stage and back-stage views of how the business actually delivers value, with operational dependencies made explicit.
Initiative-to-capability mapping
Every initiative in the portfolio mapped to the capability it builds and the strategic outcome it moves. Honest scoring of capability impact.
Architecture governance design
Decision rights, escalation pathways, review cadences. Governance that enables rather than blocks because it's anchored in a model people trust.
Twelve to twenty weeks. Collaborative by necessity.
Capability models that aren't co-produced with the business don't survive contact with delivery.
Baseline what exists
Inventory existing models, frameworks, and decision artefacts. Surface what's authoritative, what's stale, and where the gaps live.
Co-produce the capability model
Working sessions with business, technology, and data owners. L1 reads true to the CFO; L4 is usable by a backlog grooming session.
Map value streams and domains
Where the customer journey crosses internal boundaries, design the seam. Where the technical model has drifted, name the bounded context that fixes it.
Re-anchor the initiative portfolio
Every initiative re-mapped to capabilities. Surplus initiatives surfaced. Gaps in strategic coverage made visible.
Stand up governance
Decision rights and cadence wired into the operating rhythm. The blueprint becomes the artefact that quarterly reviews actually use.
Business, technology, and data teams use the same words for the same things.
Delivery teams can name which capability each feature builds, which objective that capability serves, and which strategic outcome the objective moves. The "what do you actually mean by capability" arguments stop appearing on agendas. The architecture function moves from documentation backwater to decision tool the executive committee references.