OKRs & Goal-Setting for Teams
Most teams don't lack ambition - they lack a finish line. Here's what changed when mine started writing goals we could actually score.
For my first two years as a team lead, our quarterly planning meeting was a kind of group hypnosis. We would gather in a room, someone would write "improve customer experience" on a whiteboard, everyone would nod, and we would leave feeling productive. Twelve weeks later nobody could say whether we had improved the customer experience, because nobody could say what it would have looked like if we had. We had not set a goal. We had set a mood.
The problem was not effort. My team worked hard. The problem was that we never agreed, in advance, on how we would know we had succeeded - so success became whatever happened to occur. That is a comfortable way to run a team. It is also a slow way to lose one.
The day I noticed we were busy doing nothing
The thing that finally broke the spell was a quarter where we shipped everything. Every feature on the roadmap went out the door. We celebrated. Then someone pulled up the numbers and weekly active users had not moved a point. We had completed all the activity and produced none of the outcome.
That distinction - activity versus outcome - turned out to be the whole game. "Ship five features" is something you do. "Increase weekly active users from 40 percent to 55 percent" is something that changes. You can do all the things and change nothing, and for a long time my team had been mistaking the first for the second. Motion felt like progress. The dashboard disagreed.
What an Objective and a Key Result actually are
OKRs gave us a structure for the conversation we had been avoiding. The framework is older and less trendy than it sounds: Andy Grove formalized it at Intel in the 1970s, building on Peter Drucker's Management by Objectives, and John Doerr carried it to a young Google in 1999. The structure is almost insultingly simple. An Objective is a short, qualitative statement of what you want to achieve - memorable, a little uncomfortable, no numbers in it. The Key Results are the three to five measurable outcomes that prove you got there.
Our first one looked like this. Objective: make new customers fall in love with the product in week one. Key Results: increase day-7 retention from 32 to 50 percent; cut median time-to-first-value from three days to under one; raise onboarding NPS from plus 12 to plus 35. The Objective gave us energy and a theme everyone could repeat in the hallway. The Key Results gave us something we could not argue our way out of at quarter-end.
Our first drafts were terrible, and that was the point
I want to be honest about how bad the early attempts were, because the failure modes are universal and predictable. Our biggest mistake was writing tasks and calling them Key Results. "Launch the new pricing page" felt like a goal. It is not - you can launch the page and watch conversion fall. The fix was to ask a single question of every line: could I finish this without anything in the world actually changing? If the answer was yes, it was a task, and we rewrote it as the outcome we expected the task to produce. "Launch the pricing page" became "increase visitor-to-trial conversion from 4 to 7 percent."
The second mistake was sandbagging. Quietly, we set targets we already knew we would hit, because hitting them felt good. But a goal you are certain to reach is not stretching anyone. We learned to push the number until somebody in the room felt genuine doubt, and to label which goals were promises we had to keep versus moonshots where landing at 0.7 would be a triumph. Mixing those two up silently is how teams either burn out chasing a stretch goal or quietly miss a commitment the business depended on.
Alignment is a conversation, not a cascade
The trap I most want to warn other leads away from is what I think of as the waterfall of numbers. When you try to scale OKRs across teams, the obvious move is to take the company's "grow revenue to ten million" and slice it - six million to Sales, three to Marketing, one to Partnerships - and call it alignment. It is not alignment. It is arithmetic. Nobody owns a number that was handed to them, and the people closest to the work had no say in how to move it.
What worked instead was line of sight. Leadership shared the company Objectives early, and each team asked a different question: given these, what is the most valuable thing we can contribute? My squad and the support team both pointed at the same company goal, but we chose different levers - we took trial conversion, they took early-week friction. Two teams, two distinct Key Results, one shared direction. Doerr's rough guidance that about half of a team's OKRs should come from the team itself turned out to be the difference between goals people resented and goals they authored. Ownership follows authorship.
The rhythm is the whole thing
Here is what I underestimated most: OKRs are not a document, they are a rhythm. Our first attempt failed not because the goals were badly written but because we wrote them in week one and looked at them again in week thirteen. A set-and-forget OKR is a New Year's resolution with a spreadsheet.
The fix was a 15-minute weekly check-in that is not a status report. For each Key Result we name our confidence - a number from one to ten - what moved since last week, and what is in the way. The magic is in the confidence trend. A Key Result whose confidence slides from eight to five to three over three weeks is screaming for help, and now we hear it in week four instead of discovering it at the deadline. At quarter-end we score each result from zero to one, honestly and without negotiation, then run a retrospective whose only real output is a wiser draft of next quarter's goals.
What actually changed
We are not dramatically more talented than we were three years ago. We are more honest, and we are more focused. We say no to good ideas that are not among our two or three Objectives, and we mean it. We discover trouble early enough to do something about it. Most of all, we have stopped confusing the feeling of being busy with the fact of having changed something. That shift - from "did we do things?" to "did things change?" - is small to describe and enormous to live inside. It is the difference between a team that tries hard and a team that gets somewhere.
No comments:
Post a Comment