The playbook is so familiar it feels like physics. Pick a single metric — weekly active users, net revenue retention, time-to-value, gross merchandise volume — declare it the north star, communicate it relentlessly, and the organisation will somehow align itself around it. Every leader will know what to optimise. Every team will know how to prioritise. Strategy will simplify. Coordination will fall out of the metric.
I have watched this exact promise be made and broken in five companies in the last three years. The north star always gets picked. The alignment never quite shows up.
Where the playbook quietly fails
In practice, picking the north star is the moment the alignment effort ends, not the moment it begins. The metric goes on a slide. It gets recited at the all-hands. It appears in the quarterly board pack. And then the hundred decisions that would actually have to follow from it — which inputs matter, which trade-offs the metric implies, which work to stop in order to move it — are left as an exercise for the reader.
The CFO interprets the north star one way. The CRO interprets it another. The CPO has their own translation. Each of them is reasonable. Each of them is partial. And because the metric itself is silent on the trade-offs, the differences don't surface as disagreements — they surface as quiet misalignment three quarters later, when the teams have been pulling against each other in the name of the same number.
The north star is supposed to do the coordinating work. It can't, because a metric is not a coordination mechanism. It's a scoreboard. Scoreboards don't tell players how to play.
Why one number can't carry the weight
Three structural reasons. They show up in every company that has tried this.
The first is that a single number compresses too much to be actionable. "Weekly active users" hides which users, why they're active, whether the activity is the kind that creates retention or just noise, whether the growth is coming from the segment the company actually wants to grow, or from a segment that will churn in two quarters. The metric is a summary statistic over a distribution that contains the entire strategic question. The strategic question doesn't survive the summary.
The second is that a single number hides trade-offs that have to be made explicit to be coordinated. Two teams can both pull on the north star, and they can do it in ways that work against each other. The growth team can drive WAU up by acquiring users who churn fast. The retention team can drive WAU up by deepening engagement with users who are already sticky. Each is "aligned to the north star." Each is undoing the other's work. The metric is silent on which of them is right, because the metric was the whole answer, and the whole answer turns out to be insufficient.
The third is that a single number has no resolution. A team operating on a roadmap cannot directly act on a company-level metric. They need a translation layer: which inputs they own that move the metric, which initiatives within those inputs are worth doing, which trade-offs to make when two initiatives conflict. That layer is the actual coordination mechanism, and it is almost always missing — because everyone assumed the north star was doing the work the layer would have done.
What works instead — and why most companies skip it
A north star is genuinely useful as a unifying symbol. It is a piece of leadership communication, a way to say "this, above all the other things we could be optimising, is the thing we're trying to move." It has rhetorical value. It can focus attention in an all-hands. It has no value as an operating mechanism, and confusing the two is the delusion the title points at.
What actually does the operating work is the graph beneath the metric. Which inputs move the north star. Which initiatives move the inputs. Which teams own the initiatives. Which capacity those teams have available, and what they would have to stop doing to take this on. That graph is uncomfortable to build, because it requires the leadership team to commit to a specific causal model of how the business works — to say out loud that they believe input A drives output B by mechanism C, and to be wrong in public if that turns out to be incorrect. Most leadership teams would rather have the metric and skip the graph, because the metric is unfalsifiable in the short term and the graph isn't.
So they skip it, and the north star becomes decoration. The slide stays on the all-hands deck. The teams continue to operate on the priorities they would have operated on anyway. And six months in, somebody asks why the north star hasn't moved, and the answer turns out to be that nobody owns the inputs, because the inputs were never named.
What I'd ask of any company that's adopting one
Three questions, before the slide gets made. What are the three to five inputs we believe move this metric, and which of them are we currently investing in? For each input, which initiative is moving it this quarter, and who owns that initiative? If two initiatives conflict — if growth and retention pull against each other on the same metric — what's our adjudication rule?
If the leadership team can answer those three questions before the north star gets announced, the metric will do real work. If they can't, the announcement is a comfort exercise. Naming the star feels like deciding. Building the graph beneath it is the actual deciding, and the second is much harder than the first, which is why most companies stop at the first.
The Vindaris view
By all means name a north star. It is a useful symbol, and a company past a certain size needs symbols. But don't pretend the symbol is doing the operating work. Build the three layers underneath it — inputs, initiatives, ownership — and connect them to the capacity that actually has to do the work. If those layers exist and are live, the north star is a useful pointer to the top of a real system. If they don't, the metric is morale, not strategy.
The delusion isn't picking a north star. The delusion is thinking that picking one was the move.