Outcome-Centric Trade-Off Architecture
A practical method for connecting strategic intent to architecture, execution, governance, and measurable value.
OCTA is a structured decision and execution method. It helps organisations define the outcome they are pursuing, understand the capabilities involved, make difficult choices explicitly, govern the work at the right level, and keep testing whether the investment is producing the intended value.
Why OCTA exists
Most organisations already have strategies, delivery methods, architecture standards, portfolio processes, and governance forums. The problem is what happens between them. Strategic intent becomes a project. A project becomes a technology choice. A technology choice creates operating consequences. The original outcome can become difficult to see.
OCTA provides a connecting decision layer. It does not replace enterprise architecture, Agile, product, PMO, or portfolio management. It helps those practices work together around outcomes and visible trade-offs.
Five phases
- 1Conceptual Architecture
- 2Reference Architecture
- 3Blueprint Architecture
- 4Solution Architecture
- 5Detailed Design and Benefit Realisation
The Trade-Off Engine
Applied across every phase — strategy, cost, complexity, operations, risk, and evidence quality
View the OCTA framework diagram as text
The OCTA method runs through five connected phases, in sequence:
- Conceptual Architecture
- Reference Architecture
- Blueprint Architecture
- Solution Architecture
- Detailed Design and Benefit Realisation
The Trade-Off Engine applies across every phase, making strategy, cost, complexity, operational, organisational, risk, scalability, evidence, vendor, data, and AI considerations visible throughout.
The method is iterative: evidence from benefit realisation can send any phase back for review rather than moving in one direction only.
Conceptual Architecture
Define the problem, outcome, capabilities, stakeholders, constraints, and decision context.
Reference Architecture
Set the principles, standards, patterns, guardrails, and governance expectations.
Blueprint Architecture
Describe the current state, target state, transition states, dependencies, and roadmap.
Solution Architecture
Evaluate options and define the solution that can deliver the outcome within acceptable cost, risk, complexity, and operational constraints.
Detailed Design and Benefit Realisation
Make the solution executable, establish measures, and validate whether the expected value is appearing.
The Trade-Off Engine
OCTA makes decisions visible across strategy, financial impact, implementation complexity, operations, organisation, risk, scalability, evidence quality, vendor exposure, data, and AI implications.
"Trade-offs exist whether or not they are written down. OCTA gives the organisation a disciplined way to see them, discuss them, record them, and revisit them when the evidence changes."