Outcome Measurement
Knowing whether the thing you built achieved what it promised.
6 to work through
-
intermediate
A nine-month consolidation retired four systems and released about 0.4 FTE of support effort in each of four teams. The programme closed as a success, verified by the delivery plan. Eleven months after the business case was signed, finance reports run cost unchanged and the £1.2m annual saving nowhere in the ledger. What failed, and which decision made it possible?
3 min answer -
intermediate
A platform ships a major architectural change and declares it successful because it was delivered on time. What should have been measured?
2 min answer -
intermediate
An engineering organisation reports velocity, deployment frequency and story points. Leadership cannot tell whether the investment is working. What is missing?
2 min answer -
advanced
A CFO asks why the architecture function should be funded when it ships no features. You have five minutes. What do you say?
2 min answer -
advanced
A marketplace wants to A/B test a change to its matching algorithm. Why is this harder than testing a button colour?
2 min answer -
advanced
How would you determine whether a migration completed six months ago was worth doing?
2 min answer
2 terms in this topic
Benefit Realisation Checkpoint
A scheduled review after go-live at which the budget holder confirms whether the claimed benefit has appeared in a named line, so that a benefit whic…
practiceOutcome Measurement
Determining whether an architectural change achieved what it was meant to — the step most often skipped, which is why the same mistakes recur.
Neighbouring topics
Business Architecture
General material on the business side of architecture.
Business Capabilities
What a business does, stated stably and independent of implementation.
Capability Mapping
Overlaying systems onto capabilities to expose duplication and gaps.
Business Processes
How work actually flows, including the handoffs nobody documented.
Value Streams
End-to-end delivery of an outcome, and where the waiting happens.
Domain Boundaries
Where the language of the business changes, and services should too.
Stakeholder Analysis
Who is affected, what they need, and who can block you late.
Product Thinking
Treating platforms and services as products with users and a lifecycle.
Business KPIs
The numbers a design is ultimately judged against.
Regulatory Constraints
Non-negotiable requirements that remove design options entirely.
Organisational Constraints
Team structure, skills and budget cycles as architectural inputs.
Time to Market
The constraint that dominates most products, and how to trade against it.
Build vs Buy
Differentiation versus table stakes, priced over five years.
Business Cases
Expressing an architecture proposal in the currency that gets funded.
Operating Models
How delivery, platform and governance functions fit together.
Team Topologies
Stream-aligned, platform, enabling and complicated-subsystem teams.
Platform as a Product
Adoption earned rather than mandated, with an owner and a roadmap.
Portfolio Prioritisation
Choosing between investments with incomparable benefits.
Business Continuity
What the business does while the system is unavailable.