How we deliver, in the FAQ

Measuring value, answered in full.

Validating that the outcome actually landed, in the currency the business uses rather than in story points.

questions in this group, each answered in full
4
pages the answers are written on, every one linked
1
questions across the whole FAQ
316

4 questions on measuring value, answered by Tenhaw, a UK AI consultancy and AI delivery partner based in London. Nothing here is a summary: each answer is the exact text from the page that owns it, and every group links back to that page for the context around it.

4 questions

How to measure value (outcome validation)

Answered on How to measure value (outcome validation), and rendered here in the same words.

Read the page these answers live on →

How long should an epic sit in value monitoring?

As long as the money takes, and you decide that when you write the epic rather than when someone asks. Divide the planned value by a realistic monthly run rate: a £200k epic earning £40k a month needs five months at minimum, plus whatever the adoption ramp adds. If an epic would take more than about two quarters to prove, schedule interim reads at thirty, sixty and ninety days and record a forecast at each one rather than going quiet until the end. The epic will sit in value monitoring long after the quarter it shipped in, which is expected: epics belong to one roadmap, but the money does not stop at the quarter boundary.

What if we cannot attribute the value cleanly?

Say so in the epic, take the strongest method you can afford, and label the number with the method that produced it. Holdout first, then staged rollout by cohort or region, then interrupted time series against the baseline trend, then a declared assumption signed off by someone with commercial ownership. A weak method that is disclosed is workable, because everyone reading the number knows what it is worth. An unlabelled claim built on an assumption is worse than no number, because it gets planned against. If attribution is impossible in principle, say that in the epic before it is approved rather than discovering it in the validation session six months later.

Does every epic need this, including tech debt and bugs?

No. The tech debt epic and the bug budget epic that open every roadmap are fixtures rather than priced contributions to an outcome, so validating them in currency invents numbers nobody believes. Track those two on burn rate instead: how much debt was linked and cleared, how many bugs were raised and closed, and whether the trend across quarters is improving or rotting. Everything else in the roadmap carries a currency share of an outcome and goes through the full validation, including epics that are enablers for later work. Price those against the value they unlock, not at zero.

How do we stop this becoming a blame exercise?

The number, not the person, and two habits keep it that way. The decision options include not realised so close it, which makes closing an epic short a normal result of the ritual rather than an escalation. And the calibration factor is an organisational figure rather than a scorecard: realising 70% of plan is common, and knowing it lets you plan headroom instead of pretending. The failure mode to watch for is the product manager who quietly stops bringing epics to the session. If attendance starts slipping, the honesty has already gone, and no amount of template will bring it back.

All how-to guides

Still have a question?

A 30-minute discovery call with James Rooney. Bring the question this page did not answer. You'll leave with a rough scope whether you engage us or not.

30 minutesWith James personallyNo obligation

Most organisations start with a fixed-price Agent-Readiness Audit · £30k–£90k · 6–8 weeks