A goal that has never caused anyone to say no
is not a goal.
For founders and teams who want goals that change the work. Most goals live in one document and the work lives in another. This playbook is how to make a goal actually change what your team does on Monday.
// 32 PAGES · FIVE PARTS · THREE CHECKLISTS · FREE
Seven things to know about goals.
Each is a mechanism you can plan around, and the guide is plain about the limit: goals can break a company that ignores it.
They make the trade-off explicit, in advance and in public
Every company has more good ideas than capacity, which means every company is constantly making trade-offs. The question is only whether those trade-offs are made deliberately, in the open, at a moment when everyone can think clearly — or implicitly, one interruption at a time, by whoever asked most recently and most loudly.
They separate outcome from output, which is the difference between progress and motion
Teams are very good at producing output — features shipped, campaigns launched, tickets closed — and output feels like progress because it is visible, countable and immediately satisfying.
They create alignment without adding coordination overhead
The usual response to a company that has grown out of alignment is more meetings, more status reporting and more managers relaying context.
They let you say no with a reason instead of with your authority
Declining requests is a permanent part of a founder's job and the way it is done has compounding consequences. "No, because I said so" spends relationship capital every time and teaches people to route around you or to escalate.
They make progress legible without surveillance
Founders want to know whether things are moving; teams do not want to be watched. Outcome-based goals with an honest weekly check resolve most of that tension, because the conversation is about whether the number is moving and what is in the way, rather than about what everyone did with their week.
They accumulate into an institutional memory of judgment
A year of written goals, honest scores and short retrospectives is a record of what you set out to do, what happened, and how good your estimates were.
And now the honest limit, because ignoring it is what breaks companies
OKRs are a focusing tool, and they must not be used as a performance-management tool. The instant goal attainment is tied to compensation, promotion or individual assessment, everyone in the system becomes rational about setting targets they are confident of hitting, hiding bad news until the last possible moment, and arguing about scoring.
Five parts, and a last page.
Parts one to five are the thinking and the doing, worth your time even if you never touch a piece of software. The last pages show how to keep goals and work on one surface.
What goals actually do
Decide before you write a single one
Write them so they survive real work
Run them
The checklists and the mistakes
Do it all in one place
Nine mistakes, all of them avoidable.
None is about ambition. They are failures of setup and follow-through, which is good news, because both can be set up in advance.
Writing tasks as key results
The defining error. Work delivered in full while nothing changes is the exact outcome the method exists to prevent, and a task list wearing goal formatting reintroduces it.
Having too many
A set containing everything worth doing communicates no priority and settles no conflict. If it did not hurt to write, it will not help to have.
Tying them to compensation
It is the fastest way to destroy the system. Everyone becomes rational about sandbagging and hiding bad news, and both the goals and the performance data become fiction.
Setting targets with no baseline
Without a starting number nobody can tell whether the goal is ambitious or already met, and the end-of-quarter conversation becomes an argument about interpretation.
Cascading mechanically
Decomposing every objective into sub-objectives at every level produces a bureaucracy of goals nobody reads. Align to the company objectives; do not manufacture a tree.
Leaving the goals somewhere the work is not
People work where the work is. A goals document that is not connected to the roadmap and the board is forgotten by week three, reliably.
Never killing one mid-quarter
Carrying a dead goal to week thirteen because abandoning it feels like failure costs a full quarter of effort and teaches the team that the document matters more than the outcome.
Scoring generously
It protects feelings for one afternoon and destroys the institutional memory that was the whole long-term benefit. Honest scores are the asset; good scores are not.
Skipping the weekly check
Quarterly goals reviewed quarterly cannot influence anything in between, which is where all the behaviour is. Without the weekly rhythm, do not bother writing them.
Thirty-two pages.
Yours in one click.
Five parts, three checklists and the nine mistakes. One email with the link, no drip sequence, and we do not sell the list.