Busy Is Not Aligned: North Star, OKRs, and the Scoreboard That Ties Them Together

Ask five people on a busy team what the company is trying to achieve this year. You'll get five answers. Not because anyone is disengaged — everyone is working hard, shipping things, closing tickets — but because nobody has looked at the same picture recently.

This isn't a focus problem. Focus is about what one person does on a Tuesday afternoon. This is an altitude problem: the direction, the goals, and the actual numbers live at three different heights, and most teams keep them in three different places that nobody reads together.

The three altitudes

Think of alignment as three layers, each answering a different question on a different clock.

The North Star answers where are we going, and how would we know we arrived? It changes every few years, if ever.

Company OKRs answer what has to become true this year for that to happen? They change quarterly or annually.

The scoreboard answers are we actually winning right now? It changes monthly, and it is the only one of the three that can contradict you.

Collapse any two of these and something breaks. A North Star without OKRs is a poster. OKRs without a scoreboard become a status ritual where everyone reports green until the quarter ends. A scoreboard without a North Star is a dashboard of numbers with no argument about which ones matter.

Altitude one: a North Star you could lose

A North Star is one sentence describing an outcome, far enough away to be hard and specific enough to be falsifiable.

The most common mistake is writing a mission statement instead. "Empower teams to do their best work" is a mission — it's directional, it's fine, and it will never tell you that you're off course. Compare it to "$5M ARR from customers who renew without being asked." The second one can be wrong. In two years you can look at it and say: we didn't do that. That's the whole point.

The second most common mistake is picking a number you can hit by accident. Headcount, funding raised, features shipped — these grow when things go well and when things go badly. A good North Star gets harder to fake the closer you look at it.

Three tests before you commit to one:

• Could you lose? If there's no realistic version of the next two years where you miss it, it's not a target, it's a forecast.
• Does it name the outcome, not the activity? "Ship the mobile app" is activity. "Half of active usage happens on mobile" is an outcome.
• Would two people interpret it the same way? If "enterprise customer" means different things to sales and finance, define it now, not in the retro.

Altitude two: OKRs that translate direction into this year

Objectives are the qualitative bets: what has to become true. Key results are the measurable evidence that it did.

The failure mode here is so common it's almost the default: key results that are secretly task lists. "Launch the new pricing page" is not a key result. It's a project. You can complete it perfectly and be no closer to the North Star. The tell is that you can finish it by working, rather than by succeeding.

A real key result has a number that could move the wrong way. "Self-serve conversion from 2% to 5%" can go to 1.5%. That's what makes it useful — and it's also why teams quietly avoid writing them that way.

The relationship you want between altitudes is a chain where each link is a claim you could be wrong about:

• The North Star says: $5M ARR from customers who renew without being asked.
• An objective says: make self-serve the default way customers start.
• A key result says: self-serve conversion from 2% to 5%.
• A project says: cut onboarding to a single day.
• A task says: rewrite the empty-state copy.

Someone doing that last task should be able to walk the chain upward in one breath. If they can't, either the chain is broken or the task shouldn't be on the list.

Altitude three: the scoreboard that tells you the truth

OKRs are set quarterly or yearly. That's a slow feedback loop, and slow loops let a team stay confidently wrong for months. The scoreboard is what runs in between.

A scoreboard is not a dashboard. A dashboard shows you everything measurable; a scoreboard shows the handful of numbers that decide whether you win, each one owned by a person, read on a fixed cadence. If it has thirty rows, it's a dashboard and nobody reads it.

Three kinds of numbers belong on it, and mixing them up causes most scoreboard arguments:

Goal metrics have a destination. Revenue, conversion, retention. You're trying to reach a specific number by a specific date.

Guard metrics have a limit, not a destination. Churn below 3%. Support response under four hours. Client concentration under 25%. You're not trying to maximize these — you're trying to never breach them. Treating a guard like a goal is how teams end up optimizing a number nobody wanted optimized.

Track metrics are watched, not targeted. You want to know if they move sharply, but there's no number you're chasing this year.

Some metrics are healthiest inside a band rather than above a line. Gross margin below 40% means you're underpricing; above 60% often means you're underinvesting. A band says "stay between these" and reads as off-track in both directions.

Projections, honestly

A column that shows where a metric lands if nothing changes is the difference between a scoreboard you read and a scoreboard you act on. "Revenue is $720k" is a fact. "Revenue is $720k and lands at $880k against a $1M target" is a decision.

But be careful what you project with. Draw a line from January to today and one strange month early in the year sets the slope for everything after it — we've seen this produce a projected 69% gross margin against a 40–60% band, which is not a forecast, it's an artifact. Averaging the last three months is less clever and much harder to fool: it says if recent performance holds, here's December.

The honest trade-off is that a run-rate deliberately ignores momentum. A genuinely accelerating metric will look pessimistic. That's usually the right bias for a number you use to decide where to push — optimism is already well represented in most planning meetings.

Status, and the right to override it

Computed status is a good default and a bad final answer. A metric can be technically off-track because a large client paid three days late, or technically on-track because a one-off deal masked a bad quarter underneath.

So let the person who owns the number override the badge, and require them to say why. The number tells you what. Only a human can tell you why, and the why is the part the team actually needs.

That's also the argument for writing a short analysis under the scoreboard each month. Not a report — three or four sentences. "Monthly revenue is growing but still off-target, so we need to focus on closing new deals, ideally retainers with stable clients." Next month, that sentence is the most valuable thing on the page, because it tells you what you believed and lets you check whether you were right.

The missing link: what changes on Monday

Here's where most alignment work dies. A team writes a North Star, sets good OKRs, builds an honest scoreboard — and then everyone goes back to their inbox, because nothing in the daily surface changed.

Direction only counts if it's visible where the work happens. That's the job of a small, explicit focus list: the two or three things that matter right now, named at the company level, plus one highlighted focus per person.

Three is the number for a reason. Five priorities is not a priority list, it's an inventory. The constraint is the mechanism — being forced to drop something from the list is exactly the conversation you want to have.

What this looks like on one screen

The reason all of this normally fails isn't that teams don't believe in it. It's that the North Star lives in a slide deck, the OKRs in a spreadsheet, the scoreboard in a BI tool, and the actual work in a task manager — four artifacts, four owners, four refresh cadences, and no single moment where they're all true at once.

The KeyResults Focus Dashboard puts them on one page: the North Star statement at the top, the Top 3 Focus underneath it, each team member's highlighted focus beside that, the scoreboard with its targets and projected landings, and an urgent list for the things genuinely on fire this week. Underneath, high-priority projects in progress.

The point isn't that it's one page for aesthetic reasons. It's that when the scoreboard and the focus list are adjacent, the contradiction between them becomes impossible to ignore. You can't look at "margin: off track" sitting directly above three focus items that have nothing to do with pricing and pretend the plan is fine.

Where teams get this wrong

Too many metrics. If it doesn't change a decision, it's not a scoreboard row. Move it to analytics and stop reading it monthly.

Vanity in the North Star. Anything that only goes up is a comfort blanket, not a target.

KRs that are project lists. If you can complete it by working rather than by succeeding, it's a project. Projects are good — they just belong one layer down.

Setting it once. A North Star is stable; the focus list is not. If your Top 3 hasn't changed in six months, either you're extraordinarily disciplined or nobody's looking at it.

No owner per metric. A number owned by "the team" is owned by nobody, and it will be explained away rather than fixed.

Hiding the bad month. The temptation to override a red badge to amber is strongest exactly when the red one matters most.

Start smaller than you think

You don't need the whole system on day one. In order:

1. Write one North Star sentence. Not a workshop — a first draft you'll revise. It has to be falsifiable and it has to name an outcome.
2. Pick three metrics. One goal, one guard, one you're just watching. Give each one an owner by name and a target or a limit.
3. Backfill the last few months so the trend and the projected landing mean something immediately.
4. Name your Top 3 focus — and check them against what the scoreboard just told you, not against what you'd already decided to do.
5. Only then set formal OKRs. They're much easier to write well once you know which numbers you actually watch.

Alignment isn't a document you produce. It's the state of everyone being able to answer the same three questions — where are we going, what has to be true this year, and are we winning right now — without opening four tools to find out.