North Stars: Strategic Alignment - Handbook

Teams don't operate in a vacuum. Every flight should contribute to something larger - a direction the organisation is heading. North Stars are that direction. They're the high-level objectives that give flights purpose and connect the daily work of individual contributors to the strategic goals of the company.

What Are North Stars?

A North Star is an organisational objective that flights align toward. If you're familiar with OKRs, think of North Stars as the "O" - the Objective - without the baggage of the quarterly planning cycle, the key results negotiations, and the grading ceremony at the end.

North Stars are meant to be inspiring and directional. They describe where you're going, not how to get there. "Make onboarding take under five minutes" is a good North Star. "Implement SSO and reduce form fields by 40%" is not - that's a solution, not a direction. The solution belongs in a flight. The direction belongs in a North Star.

The key difference between North Stars and traditional goal-setting frameworks is simplicity. There's no scoring rubric. No percentage-based grading. No quarterly review where everyone pretends they're "on track" when they haven't looked at their OKRs since January. North Stars are visible, they're referenced when planning flights, and they evolve when the strategy evolves. That's it.

An organisation might have three to five active North Stars at any time. Fewer is better. If you have fifteen North Stars, you don't have North Stars - you have a wish list. The constraint forces prioritisation, which is the whole point. You can't go everywhere at once. Pick a direction and commit.

Setting North Stars

Setting meaningful North Stars is harder than it looks. The temptation is to be either too vague ("Improve the product") or too specific ("Launch feature X by Q2"). The sweet spot is a clear, measurable outcome that leaves room for multiple approaches to achieve it.

Good North Stars have a few characteristics. They're outcome-oriented - they describe what success looks like, not what to build. They're measurable, even if informally - you should be able to look at a North Star and say "yes, we're getting closer" or "no, we're not." And they're stable enough to guide multiple flights, not just one.

Here are some examples that work well:

"Reduce onboarding time to under 5 minutes" - clear outcome, measurable, multiple flights could contribute
"Reach 99.9% uptime for the core platform" - specific target, inspires reliability flights
"Make the mobile experience as capable as desktop" - directional, team understands what it means
"Enable self-serve for 80% of customer requests" - outcome-focused, doesn't prescribe the solution

And some that don't work:

"Build the API v2" - this is a project, not a direction
"Be the best product in the market" - too vague to be actionable
"Increase revenue" - every company wants this, it provides no guidance
"Migrate to microservices" - this is a technical approach, not an outcome

North Stars should be set by leadership with input from the teams. They represent strategic decisions about where the organisation is investing its energy. But they shouldn't be dictated top-down without context. The teams who will actually do the work should have a voice in shaping the direction, because they often have the best understanding of what's realistic and what's not.

Connecting Flights to North Stars

The idea is simple: each flight can connect to a North Star, creating a natural alignment chain. The organisation has strategic objectives (North Stars), teams pursue those objectives through time-bound initiatives (flights), and individuals execute the work within those initiatives (crates). Everyone can trace their daily work back to something that matters.

Flights connect to North Stars by linking each flight to the strategic objective it advances. This keeps day-to-day work visibly tethered to long-term direction.

Not every flight needs to be connected to a North Star. Infrastructure work, tech debt paydown, and tooling improvements are all valid flights that may not map cleanly to a strategic objective. That's fine. Forcing every flight to align with a North Star leads to artificial connections ("this dependency update serves our North Star of improving onboarding... somehow") or discourages important housekeeping work.

When North Stars do work well, the value shows up in aggregate. Look at the flights your team has completed over the past quarter. If most of them cluster around the same two objectives, you know those got serious investment. If a North Star has no flights near it, that's a signal - either the objective isn't actually a priority, or the team needs to plan flights that address it.

This creates alignment without mandates. Nobody is told "you must work on this North Star." Instead, teams naturally gravitate toward the objectives that matter most because the connection is visible. When the CEO asks "how are we progressing on our goal of reducing onboarding time?", you can point to three landed flights and two active ones that directly contributed - with specific crates showing the work that was done.

Avoiding Bureaucracy

The biggest risk with any strategic alignment tool is that it becomes bureaucracy. OKRs were supposed to be lightweight when Andy Grove introduced them at Intel. Now they require dedicated software, quarterly planning cycles, mid-cycle check-ins, and end-of-quarter grading ceremonies. The tool became the process.

Flights guards against this by keeping North Stars deliberately simple. There's no mandatory alignment review. There's no scoring. There's no percentage-complete tracker for North Stars. They exist as reference points - beacons that teams can orient toward - not as bureaucratic checkpoints that teams must report against.

If you find yourself scheduling a monthly "North Star alignment meeting" or creating a spreadsheet to track North Star progress across teams, you've gone too far. The alignment should happen naturally through flight planning: "We're starting a new flight. Does it connect to one of our North Stars? If so, link it. If not, that's fine too." That's the entire process.

North Stars should also evolve without drama. If the strategy changes - and it will - update the North Stars. There's no end-of-quarter ritual required. If a North Star is no longer relevant, retire it. If a new priority emerges, add it. The tool should be as dynamic as the business it serves.

The guiding principle is this: North Stars should clarify, not constrain. They answer the question "what matters most right now?" and help teams make better decisions about what to work on. The moment they start creating overhead - meetings, reports, compliance checklists - they've stopped serving the team and started serving the process. Pull back immediately when you see that happening.