Three words that get mixed up
An objective is the change you want: make business payments faster, easier and more reliable. A key result is a time-bound, measurable commitment that proves the change happened: digital adoption from 40% to 65% by Q4. A KPI is a health signal you keep watching whether or not a key result is attached to it: adoption rate, payment success rate, cost per transaction.
The difference matters at the review. A key result ends when it is met or missed and a new one is set. A KPI never ends; it stays on the dashboard to catch a slide back.
Operational and development value streams measure different things
The operational value stream is the customer's journey: initiate a payment, authenticate, clear, confirm. Its KPIs are completion time, success rate and cost per payment.
The development value stream is how the bank builds and changes the systems behind that journey: identify the need, design, build and integrate, release and learn. Its KPIs are flow time, throughput and release quality.
Agile Release Trains deliver inside the development value stream; what they deliver enables the operational one. Measuring the development stream alone shows activity, not value.
One outcome from the portfolio to the teams
| Level | Objective | Key result | KPIs to watch |
|---|---|---|---|
| Portfolio | Grow profitable digital payments | Adoption 40% → 65% | Adoption, revenue, cost per payment |
| Development value stream | Enable faster, reliable payments | Journey 5 min → 1 min | Flow time, completion time |
| Payments ART | Improve payment reliability | Success 98.5% → 99.9% | Success, latency, defects |
| Digital Channels ART | Make journeys frictionless | Abandonment 30% → 10% | Abandonment, conversion |
| Agile teams | Build and test solution increments | Stories: APIs, UX, automated tests | Cycle time, escaped defects |
A KPI can carry a key result
Digital Channels ART owns payment abandonment. The key result says 10% by Q4. The KPI reads 30% in Q1, 22% in Q2, 14% in Q3 and 9% in Q4. The key result closes in Q4; the KPI keeps being watched in Q1 of the next year, because a redesign that drifts can take the number back up.
What to inspect each quarter
- Did we achieve the targeted customer or business change?
- Are operational and solution health KPIs stable?
- Did the ARTs improve the capabilities that drive the outcome?
- What should we fund, stop, improve, or experiment with next?
A balanced measurement system
SAFe's Measure and Grow names three lenses. Outcomes: are customers and the business better off (adoption, revenue, satisfaction)? Flow: how efficiently does value move (flow time, throughput, efficiency)? Competency: can the organisation keep delivering (technical quality, business agility)? Reviewing only flow mistakes delivery for value; reviewing only outcomes hides why they moved.
Walk the example yourself at /examples/okrs-kpis, where every element is clickable, or load Northstar Bank as an example customer in the outcome dashboard.
Updated 2026-10-24. SAFe® is a registered trademark of Scaled Agile, Inc. All guides.