THE PROBLEM
Programme information existed, but decision traceability did not travel with it.
Different stakeholders needed executive, capability, programme and engineering views. Dependencies and assumptions were distributed across repositories and documents, while uncertainty was often hidden by presentation-ready diagrams.
The architecture had to explain not only what existed, but what decision each view supported.
MY CONTRIBUTION
Connect decisions across levels without flattening the detail.
- Mapped relationships among outcomes, capabilities, requirements, programmes, alternatives and benefits.
- Analysed dependencies across more than 25 programmes and projects.
- Produced 34 decision-focused architecture figures and views for one major decision package.
- Connected executive summaries to working-level architecture evidence.
- Improved repository use, consistency and organisational handover.
THE ARCHITECTURE APPROACH
Establish the decision before the diagram.
Define the decision
Clarify who must decide what, by when and against which evidence.
Maintain traceability across levels
Link strategic outcomes to capabilities, requirements, programmes and delivery dependencies.
Represent uncertainty honestly
Separate confirmed relationships, assumptions, gaps and alternatives.
Use multiple views, one logic
Tailor the presentation to the audience without creating contradictory architectures.
OUTCOME
Decision-ready views with an auditable reasoning path.
Stakeholders could navigate from executive intent to programme dependencies and supporting architecture evidence, while gaps and assumptions remained visible for follow-up.
WHY THIS MATTERS ELSEWHERE
Complex programmes fail between layers.
The method applies to transformation portfolios, defence acquisition, regulatory change, platform consolidation and multi-supplier delivery—where decisions must remain coherent as they move across organisational boundaries.
Relevant capabilities: enterprise architecture · capability architecture · programme architecture · decision support · requirements traceability · dependency analysis · architecture governance.