Shipped is not the same as worked.
The roadmap says done. The metric has not moved. Write the outcome instead of the feature, and let a weekly score tell you whether the bet is paying while there is still quarter left to spend.
A roadmap tells you what you will build, not whether it worked.
Most product goals are a shipping schedule in disguise. Three features, a date each, and the quiet assumption that shipping them is the same as moving the number. It is not, and everybody finds out at the same moment: the end.
What makes it worse is that the numbers product teams are judged on are the slowest ones in the company. Activation, retention, expansion. They tell the truth in week twelve, which is exactly one week too late to change what you build.
So write the outcome as the objective, and make sure one of its key results is something that already moves in week two.
Three objectives that are not a release plan.
Not a list to copy. A shape to copy: the outcome you are actually betting on, something that moves in week two so the bet can be read early, and the cost that outcome could quietly run up somewhere else.
New teams get to value before they get bored.
Nobody can move activation on a Tuesday. Watching twenty sessions is something a person can actually do, and it is the reason the first number will move at all.
Make the second quarter the one they stay for.
Retention flatters you. A team can renew and never open the app. The third line is what stops a win on paper from counting as a win.
Find out whether the summary feature deserves a second quarter.
The objective is not to ship the feature. It is to learn whether the feature earns another quarter. Written this way, killing it counts as success, which is the only way anyone ever actually kills anything.
Copy the shape, not the list. Three objectives by Friday, and five minutes every Monday after that.
The report card is not the lever
Activation and retention are lagging by nature. You read them, you do not move them. Put one key result on the research, the instrumentation, or the release that has to happen first, and the quarter gets something you can actually steer.
Pair adoption with what adoption can cost
A usage number with no counterweight is how a team ships something that gets used once and resented after. Put the cost next to it: support load, latency, the metric next door that quietly pays for this one.
A discovery quarter is not a scaling quarter
Hold, step or leap: say which one this is before anyone scores it. Grading a leap against an increment turns a real result into a miss, and it is the quickest way to teach a team to aim lower next time.
The craft is not ours. Learn it from the people who taught it: whatmatters.com
Bad news in week three.
The dashboard does the subtraction, and every key result that is drifting is surfaced with the reason its owner gave.
A bet that is not paying says so while there is still a quarter left to spend somewhere else. That is the entire difference between a number you manage and a number you receive.
Stop building the deck.
The exec review, the board update, the quarterly readout. The same numbers, retyped into slides, already stale by the time you present them.
Send a link to the quarter instead. It opens read-only, it carries your logo, and it is current to the minute, so the readout stops being something you have to prepare.
We already have a roadmap tool.
Keep it. It holds what you are building and when. This holds the three outcomes the building is for. One is a plan and the other is a scoreboard, and letting the plan grade itself is how roadmaps end up measuring their own completion.
Outcomes are not always in our control.
True, and that is the argument for confidence, not against outcomes. Every key result carries a number and a color. The color is where you say this is not going to make it, in week four, in public, while saying so is still cheap.
Will this turn into a status report?
Only if you write it as one. Scoring a key result takes a minute and produces one line, not a page. Everyone reads the same record, which is the thing the status report was always pretending to be.
How many objectives should we have?
Three. Occasionally four. The number is small on purpose. An objective you would not defend against the other two is not an objective, it is a wish with a metric attached.
One quarter, read in every dialect.
Every team measures something different and none of them should have to learn a second tool to say so.
Any week is week one.
Pick up the quarter you are in, or start the next one clean. Three objectives by Friday. Five minutes every Monday.
Free for one team · no credit card · see pricing