Outcomes Over Output: Why Customer Behavior Is the Key Metric for Business Success
Source: https://www.senseandrespondpress.com/managing-outcomes ↗
Seiden's short book makes one argument clearly: the right measure of product success is not what you shipped (output) but what changed in customer behaviour (outcome).
The book is deliberately concise — under a hundred pages — and that compression is its value.
For product direction it is a useful pocket reference for the most common conversation in product organisations: the one where shipping features is confused with making progress.
Read alongside Perri's Escaping the Build Trap for the longer treatment and Doerr's Measure What Matters for the goal-setting complement.
Short enough to read in an afternoon, portable enough to carry into meetings.
Central argument
Seiden argues that product teams systematically confuse output — features shipped, releases delivered — with actual progress, and that the only honest measure of success is a change in customer behaviour that produces a business result. He distinguishes outputs (things you make), outcomes (behavioural changes you cause), and impact (business results those changes generate), and insists that product work should be planned and evaluated against outcomes rather than delivery milestones. The book's core prescription is that teams should define success by asking 'what human behaviour needs to change?' before deciding what to build.
Critique
The book's brevity, which the curator rightly identifies as a feature, is also its main limitation: Seiden asserts the primacy of behavioural outcomes without seriously engaging with cases where behaviour is genuinely hard to measure, lagging, or ambiguous — for instance, in B2B platforms where purchasing decisions involve long cycles and multiple actors whose behaviour cannot be cleanly attributed to a single product change. The framework also assumes a relatively direct line between customer behaviour and business value that does not always hold in regulated industries, network-effect products, or infrastructure tools where the 'customer' whose behaviour matters is several steps removed from the end user.
Why it matters for product
For a CPO, the outcome framing directly addresses one of the most persistent organisational dysfunctions: roadmaps that are essentially feature queues, which give engineering teams clarity on what to build but leave the organisation unable to answer whether any of it worked. Reorienting planning around behavioural outcomes forces earlier alignment between product, commercial, and executive stakeholders on what success actually looks like, and changes the nature of discovery — the question is no longer 'what should we build?' but 'what behaviour are we trying to shift and what is the smallest intervention that could shift it?'