The OKR Playbook Shipping is not progress. Make the goal change Monday.
You can ship an enormous amount and change nothing about your business. This guide shows how to write goals as outcomes, keep them few, attach them to the work you actually open, and check them every week, alone.
The method rarely fails. The ritual does.
A planning session. A document that looks reasonable. Then a working life that carries on exactly as before, and a generous score at the end of the quarter. Nothing in between was caused by it. What fails is almost always one of three things underneath: goals written as a list of work, too many of them to force a choice, and no weekly moment that makes you pick the goal over the other thing you fancy doing. Working alone makes it harder. There is nobody to ask whether the number moved.
None of them is "alignment".
You have more good ideas than evenings. A written goal decides what wins before the conflict arrives, so priority is not set by recency and mood.
Output feels like progress because you can see it and count it. Asking what would actually be different if it worked shows which planned work is unnecessary.
"That does not serve what I chose this quarter" costs nothing and holds up at eleven at night. "I do not feel like it" costs you every time.
The check is about whether the number is moving and what is in the way, not about what you did with your week. It catches hard work that is not producing the result.
The moment a contractor or collaborator appears, a few shared goals do much of the work of check-ins. They decide better alone and interrupt you less.
A year of goals, honest scores and short retrospectives shows whether you overestimate, which bets work and how long change really takes in your business.
One objective. Three numbers. Fifteen minutes a week.
Not a framework to admire. A small system you will still run in a bad week: goals written as outcomes, attached to your work, checked weekly and scored honestly.
Five parts, in order.
Six specific effects on how you decide, and the honest limit: a focusing tool must never become a pay or performance tool, not even for yourself.
An objective is a direction. A key result is evidence. How few to have, the cadence, committed versus aspirational, and what you are explicitly not doing.
Outcome first, then the metric. Baseline before target. Four bad patterns to spot on the page, an owner for each, and goals that live where the work is.
The weekly check on confidence, declaring a goal dead early, the mid-quarter honesty session, honest scoring, retrospectives and the warning in an all-green quarter.
Before the cycle starts, writing the key results, and running the quarter. Each line is a box you either can or cannot tick.
Nine ways this turns into overhead. All of them are failures of discipline and connection, not of framework, and every one is reversible next quarter.
What would genuinely be different in three months if this went well? Plain words. Only then ask which number would prove it.
A target with no baseline is not measurable. If you cannot name the starting value, finding it is your first key result, and often the most valuable one.
Put the outcome and the numbers at the top of the list you actually open, and put the weekly check in the calendar for the whole quarter.
- You already run a one-person business and want to scale it without losing the plot.
- You are good at shipping and suspect some of it changes nothing.
- You are willing to leave good things off the list.
- You want a small system you will still run in a bad week.
- You want a goal system to track other people's performance or set their pay.
- You want a long list of goals that covers everything worth doing.
- You want targets you are sure to hit so the quarter feels like a success.
- You will not do a weekly check. The guide says to skip the whole thing then.
A goal that never makes you say no is not a goal.
It is a description of things you were going to do anyway. Nobody will tell you that you spent six months shipping in a direction that produced nothing. Only you can ask, so the asking has to be scheduled.
Luis Gonçalves
Twenty years in digital product development. Led the agile transformation at Nokia. Teaches at Porto Business School. Has spent the last decade working with founders across Saudi Arabia, Portugal, Brazil, and the broader emerging-market startup ecosystem.
He calls himself the Dark Entrepreneur because he believes the founder world is allergic to honesty. No success theater. No highlight reels. Just the real work that has to happen.