Business Outcomes & Product Outcomes

A team improves the report builder until people build far more reports. Usage doubles. It is a real, measurable, hard-won change in behaviour. Renewals do not move at all.

What happened is that they achieved a product outcome that was not attached to a business one — and these are two different things that are easy to confuse because both are “outcomes”.

A product outcome is a change in what users do: more people activate, sessions get longer, fewer tickets get filed. A business outcome is a change in the health of the company: revenue, retention, cost, market share. Product outcomes are closer to your work and move sooner. Business outcomes are what the company actually needs and move later.

The trap is assuming the first automatically produces the second. In the report-builder story it did not, for a mundane reason: the people building reports were analysts, and the people deciding on renewal were executives who only ever read them. Serving the first group beautifully did nothing for the second, and the connection had never been examined because it felt obvious.

So the working method is to state both, and state the link between them out loud. “If more accounts reach first value in week one, more of them will still be paying in month three, because early value is what makes the renewal conversation easy.” Written that way, someone can disagree with the middle clause — which is the whole point. The link between a product outcome and a business outcome is an assumption, not a fact, and it is the part most worth arguing about before the quarter starts.

Teams can rarely move a business outcome directly, but they can move user behavior. That's why product teams own product outcomes.

Everything a team does forms a chain: we ship something, that changes what users do, and that changes something the business cares about. Written out, it looks like this — we shipped the onboarding checklist → more accounts reach first value → more of them are still paying in month three.

The chain looks like a plan. It is more accurate to see it as a set of claims, because the arrows are doing all the work and none of them are guaranteed.

The first arrow says the thing you built will change behaviour. It might not — people may not notice it, or may not want it. The second says the behaviour change will reach the business. It might not, for exactly the reasons in the previous lesson. Each arrow is an assumption, and a chain is only as strong as its weakest one.

This is why so many roadmap arguments feel unresolvable. Two people are usually not disagreeing about whether to build the thing; they are disagreeing about one specific arrow, without either of them saying which. Drawing the chain forces that into the open, and the conversation gets noticeably shorter.

It also tells you what to measure and in what order. If you only measure the last link, you will wait months to learn nothing useful — you will know it did not work, but not which arrow broke. Measuring each link means that when the chain fails you can point at the join, and the next attempt starts from evidence rather than from the beginning.

The first one cannot be argued with, which sounds like a strength and is the problem. Nobody will object to it, nobody can tell you it has been missed, and at the end of the quarter the team will have a genuine disagreement about whether it was achieved — with no way to settle it.

A strong target has three properties, and it is worth checking all three. It is behavioural — it describes something people do, not something they feel. It is measurable with a number you already collect or can start collecting today. And it has a baseline and a deadline, because “raise retention” without a starting point is not a target, it is a direction.

The word “happier” fails all three at once. There is no behaviour named, no instrument that reads it, and no threshold that would count as success. It is a sentiment dressed as a goal.

Setting a real number feels riskier, and it is — you can now miss it in public. That is exactly why it works. A target you can miss is the only kind that changes what a team does in week three, when there is still time to react. A target you cannot miss changes nothing until the retro, by which point the quarter is spent.