Feature Outcome Scorecard
Did the feature actually move the metric? Score baseline vs. target vs. reality - and weigh the result against the effort it took.
Shipped features
Editable estimates. Verdict = hit target (win) · ≥50% of intended movement (partial) · else miss.
Outcome summary
The actual value reached or beat the target you committed to. The hypothesis held - now protect the gain.
You captured at least half of the intended movement but fell short of target. Worth a follow-up, not a victory lap.
The metric barely moved - or moved the wrong way. The feature shipped; the outcome did not. Time to learn why.
Close the loop: did it actually move the metric?
Most teams celebrate the merge. The Feature Outcome Scorecard celebrates the result. Every feature is a bet that some metric will move - activation, latency, retention, revenue. This tool records the number before you shipped, the target you committed to, and the number afterward, then reports the delta, the percent change, and an honest win / partial / miss verdict weighed against the effort you spent.
That closed loop is the whole idea behind FeatureFactory. Work starts as a hypothesis in Plan, gets built with a target attached in Build, and is judged by what the metric actually did in Measure. A scorecard full of unverified wins is just a to-do list with confidence.
Pair this with the rest of your delivery toolkit: pick the right bets with the RICE score calculator, and understand the flow that gets features out the door with our cycle time explainer. Prioritization tells you what to build; the scorecard tells you whether it was worth it.
Frequently asked questions
Ship features that move the number
FeatureFactory is the feature factory that measures what it ships - plan the bet, build it with a target attached, and let the scorecard fill itself in from real outcomes instead of optimism.
Get early access