Giving benefits an owner

Delivery ended at launch

The business case justified starting the work, then disappeared. Delivery was tracked closely until release, and the benefit was assumed to follow. Nobody was asked afterwards whether it had.

Changing the lifecycle

I redesigned the lifecycle so that benefits run through it rather than sitting in front of it. Each piece of work now starts with a stated benefit hypothesis and a named owner. After release, the owner revisits the benefit at set points, and the evidence goes into the portfolio review, where it informs whether related investment should persevere, pivot or stop.

Connecting the measures

Each benefit traces from the product outcome to cost, revenue or risk, so the review knows what it is checking.

Changing what leaders aim for

A new lifecycle changes little if people are still rewarded for the old thing. Product goals had been written as outputs: features shipped, releases made. I replaced them with outcome goals, and that was the larger change.

A capability programme gave product managers the practice to work this way. Coaching helped senior product leaders write goals they could genuinely be held to.

Evidence and limits

The principal change was to extend product accountability beyond delivery. The previous lifecycle gave strong visibility of whether work had shipped. The redesigned one required an explicit benefit hypothesis, a named owner and a review of the outcome after release.

I also changed how product leaders set goals, replacing delivery outputs with the business or operational outcomes they were meant to produce, and supported that change through capability development and coaching.

These are changes to organisational accountability and management practice. Their economic significance depends on what the reviews then do: whether they catch benefits that haven't arrived, trigger corrective decisions, or confirm that the intended outcomes were achieved. A new lifecycle is not the measure of success. The measure is whether it changes what leaders do when the expected benefit fails to appear.