Review
The phrase "outcomes over output" gets said in product rooms constantly, and most people saying it cannot give you a clean definition of either word. Seiden can. The whole book builds from a single sentence: an outcome is a change in behavior that drives business results. That definition earns its place because it gives you something you can actually point at and measure, which turns a principle most teams invoke loosely into a real management tool. What I valued most is that the book does not stop there. It extends the logic to executive goal-setting, team-level experimentation, and how to apply outcome thinking to organizational change programs. For something this short, the scope is genuinely ambitious. Worth reading once, and rereading when OKR season arrives.
Key Takeaways
The parts worth keeping
Three modes of management
| Mode | What it means |
|---|---|
| Managing output | Telling teams what to build. Features don't automatically create value, so this mode often misses the point. |
| Managing impact | Setting high-level goals like growing revenue. Correct direction, but too abstract to guide daily decisions. |
| Managing outcomes | Asking teams to create a specific behavior that drives results. Gives them room to find solutions while staying focused on delivering value. |
What executives care about
Jared Spool's five impact-level metrics:
- Increasing revenue
- Decreasing costs
- Increasing new business and market share
- Increasing revenue from existing customers
- Increasing shareholder value
Finding the right outcome
- Ask: what are the customer behaviors that drive the results we care about?
- Ask: what are the things customers do that help us predict the outcome we want?
- Leading indicators are behaviors people are doing that predict success. Outcomes function as leading indicators.
- Think of MVP as the smallest thing you can do to learn whether your hypothesis is correct.
The Magic Questions
- What are the user and customer behaviors that drive business results?
- How can we get people to do more of those behaviors?
- How do we know that we're right?
Hypothesis-driven work
- Treat ideas like assumptions. Express assumptions as hypotheses. Run experiments to test them.
- A hypothesis states what you believe and the evidence you are seeking to know whether you are right.
Frame an outcome goal as a hypothesis:
We believe that if we increase the rate at which buyers and sellers meet early in the process, it will lead to more successful transactions (as measured by X) and higher user satisfaction (as measured by NPS.)
We think we can increase the rate of early meetings [with this idea] and [with this idea] and [with this idea.] We will work on testing these ideas in Q1 of the coming year.
OKRs and roadmaps
- Outcomes help you write better OKRs: start with the business result you want, then express it as a specific, measurable customer behavior.
- Visualize the customer journey and map behaviors at each step:
- Boosters: behaviors that predict success and satisfaction
- Blockers: behaviors that predict failure and dissatisfaction
- Teams should specify the outcome they seek for the customer, the outcome they seek for the business, and the link between them.
- Organizations structured around products and channels often favor outputs over outcomes. Structure around customer journeys instead.
Applying outcomes to organizational change
- Treat your colleagues as customers
- Everything is an outcome
- Everything is an experiment
- Frame change initiatives in terms of behavior: what will people be doing differently when the change succeeds?
- Offer colleagues something of value to get them to "buy" the change you are selling.