The chapters
Outcome System Result moves from foundations to architecture to application. Each part builds on the one before. Read in order for the full argument, or jump to the chapters most relevant to your domain.
Buy the book →Outcomes are everywhere, but most teams are chasing them in the dark. Features stand in for value. Metrics stand in for meaning. And AI is beginning to act in ways most leaders aren't modeling. This part lays the groundwork for why a new approach is needed now.
Buzzwords. Outcomes is one of them. Everyone is chasing them, yet over half of software products fail to deliver them. The breakdown isn't operational. It's systemic. Our understanding of, and the way we think about outcomes, is broken. This chapter sets the stage for why a new approach is needed now.
Before you can chase outcomes, you have to decide what truly matters. Part II reframes value not as price, cost, or worth on a slide, but as something personal, contextual, and often invisible. It introduces Desired Customer Value vs. Experienced Customer Value, and shows why the gap between them determines trust, retention, and long-term success.
Why do customers buy something? Not from a pricing or branding perspective, but from First Principles. The answer, irrespective of sector: customers are buying the possibility of transformation. Cost, price, worth, and value are not the same thing, and confusing them is where most strategy fails.
Outcomes are not metrics. They are not solutions. They are not features. An outcome is a meaningful shift in a customer's operating or living circumstances. This chapter defines outcomes as forward-facing commitments to change and explains why starting with the end in mind is the foundation of every durable system.
Before organizations can deliver real value, they have to see it in motion. Part III reframes measurement as more than counting activities or watching dashboards. It introduces the BACKS framework as the core signal of transformation: Behavior, Attitude, Condition, Knowledge, and Status.
The BACKS lens. Behavior, Attitude, Condition, Knowledge, Status. Five domains where real change actually happens, and where most organizations fail to look. This chapter shows how to detect transformation as it occurs, not after it has faded.
Outputs are not outcomes, but they are not optional either. This chapter restores nuance to the outputs-vs-outcomes debate. When activity matters as evidence of progress, when it doesn't, and how to position outputs as supporting signals rather than the whole story.
To turn outcomes into reality, organizations have to move beyond isolated initiatives and start managing what actually drives performance: the system itself. Part IV introduces stocks and flows as the structural engine behind outcomes, and the systems thinking required to anchor outcomes in the real machinery of an organization.
Capacity is the constraint that shapes everything. This chapter introduces stocks and flows as the structural engine behind outcomes. How inflows and outflows shape pace and direction, why net change on a dashboard is misleading, and how resource behavior over time explains success or failure better than any one-off metric.
Loops, delays, and accumulation. This chapter moves from looking at parts of the business in isolation to thinking in systems. Why most models are incomplete, how unspoken mental maps drive decisions, why motion is so often mistaken for progress, and how to read causal feedback before it becomes a crisis.
To manage outcomes, you need more than ambition. You need a model. Part V introduces the OSR Framework as a five-tier system that turns value into performance and strategy into reality. Where OKRs ask did we complete the task, OSR asks did we move the system in the right way.
The five-tier OSR architecture in depth. Primary Outcomes, Performance Targets, Support Outcomes, Flow Rates, Milestones. How the tiers connect causally, how each one fails when isolated, and the structural reason this architecture succeeds where target-only frameworks collapse under complexity.
OKRs measure distance traveled. OSR measures the energy that causes movement. This chapter contrasts the two physics models, OKR's linear cause-and-effect versus OSR's dynamic systems with state and accumulation, and explains why one chases lagging indicators while the other shapes the system itself.
Outcomes without context drift. Value without structure stalls. Part VI is where value and outcomes finally lock together. It works through four essential questions that anchor value-driven strategy and convert abstract vision into practical, testable action.
Value is what the world experiences. Outcomes are what the system produces. The bridge between them is structural, not aspirational. This chapter walks through the divide between defining value and delivering it, and the questions every leader must answer before that bridge can hold weight.
How do we define value? What outcomes should we pursue? How do we choose our Primary Outcome? How do value and outcome align? Four questions every leader, operator, and builder must answer before designing for outcomes that hold.
From promise to performance. Outcomes do not deliver themselves. Systems do. Part VII shows OSR applied to three real-world domains: city housing, IT services, and SaaS growth. Each case starts with a Primary Outcome and builds out the full five-tier architecture.
How a multi-year homeownership program operationalized OSR. A real city, a real system: families moving from rental dependence to stable ownership through five Performance Targets, six critical flows, and one Primary Outcome. Demand-side stabilization, capacity readiness, and BACKS-based outcome design.
The operational physics of a services firm. Four performance targets that govern throughput, quality, and capacity in a flow-based business. How OSR manages the dynamic between client demand, delivery capacity, and the trust signals that determine whether services scale or stall.
The compounding architecture of product-led growth. Why information architecture, not feature velocity, determines durability. Value foundation, system mapping, and a complete five-tier OSR structure for a scaling SaaS company, including the support flows that secure the pulse of the system.
Ready to read it
Outcome System Result is the canonical text of the OSR standard. Five hundred pages, fourteen chapters, the full causal architecture for designing outcomes that accumulate.
Or buy from your favorite retailer →