Sprint goals tell you what to do this week. They don't tell you why the work matters.

That gap is where teams quietly lose energy. The team can be hitting every sprint goal — shipping on time, closing tickets, hitting the metrics that get measured — and still feel like they're not getting anywhere. The work is happening. The point of the work isn't clear.

A north star fixes that. Not a tagline. A specific, current, named outcome the team is collectively chasing — the thing that, if you achieve it, the quarter was a success regardless of which individual sprints went well.

Why sprint goals aren't enough

Sprint goals are operational. They're useful — they create cadence, force prioritisation, give the team something concrete to organise around. They also have a shorter time horizon than most meaningful work.

The features that matter most usually take longer than a sprint. The improvements that compound take longer. The strategic shifts take much longer. If the team's understanding of "what we're trying to do" only goes as far as the current sprint goal, they have no way to make trade-offs that span sprints.

That's where local optimisation kicks in. Each sprint looks fine. The team is shipping. The work over six sprints adds up to something incoherent because there was no organising principle above the sprint level.

What a north star actually is

It's not the company mission. The mission is too abstract — "make work better" doesn't tell the team what to ship in March.

It's not an OKR. OKRs are usually quarterly and often plural. A north star is singular and time-bounded.

It's a specific outcome the team can describe in a sentence and trace their work back to. Examples that work:

"Get new-user activation from 32% to 50% by end of Q2."

"Make the core workflow under 60 seconds for power users by July."

"Get the second-purchase rate above 40% — currently 27%."

Each of these is concrete. Specific enough to know whether you hit it. Big enough to require multiple sprints. Tied to user behaviour or business value, not internal process.

Without something like this, the sprint-by-sprint cadence has no upper coordination. With it, every sprint can be evaluated against the same question: did this move us toward the north star?

What a north star changes

Three things shift when a team has one:

Trade-offs get easier. When two pieces of work compete, the question is "which one moves the north star more?". Most ties break themselves once the question is asked. Without it, the loudest voice or the most political ask wins.

The team self-coordinates. Engineers, designers, and PMs are all making small decisions every day. With a north star, those decisions converge — each person, even acting independently, is pointed in the same direction. Without one, each person's decisions optimise for their own local view of the problem.

Motivation lasts longer. Sprint goals provide short-term focus. The north star provides medium-term meaning. Teams that have one are visibly more energised over a quarter than teams that don't, because the work has a destination.

How to actually pick one

A few rules that produce useful north stars:

Tied to outcomes, not output. "Ship X features" is output. "Move metric Y to Z" is outcome. Output-style north stars produce teams that hit the output and miss the point. Outcome-style north stars produce teams that adjust the output until they get the result.

One number, not a portfolio. The temptation is to have three north stars to cover all the bases. That's a strategy document, not a north star. Pick the single most important one. Coverage is the enemy of focus.

Achievable but not easy. If the team can't see a path to it, the north star demotivates. If the path is obvious, it's not stretching anyone. The right tension is "we can see how this is possible, and it's going to take real work to get there".

Owned by the team. Not handed down from above as a fait accompli. The team should understand why this is the north star, what makes it the right one, and have had real input into the framing. North stars imposed without that conversation tend not to stick.

How it actually shows up

A few markers that the north star is doing work:

People reference it without prompting. In planning meetings. In Slack threads. In code review comments. If it's only mentioned by leadership, it hasn't taken hold yet.

The roadmap visibly serves it. Each item should map back to the north star or have an explicit reason for being on the list anyway. Items that can't be traced get discussed.

Sprint reviews compare progress. Not just "did we ship the things?". "How much closer are we to the north star?". The first is operational. The second is strategic.

The shift

Sprint goals keep the team moving. The north star tells the team where they're going.

Build both. Run sprints with goals. Run quarters with a north star. Make sure the north star is concrete enough that the team can tell whether they're getting closer.

The teams that have one ship work that adds up. The teams that don't ship work that mostly cancels out.

If you're running an operating system for fast ships, the north star is the coordination layer that makes the cadence add up to something. And strategy isn't the deck — it's the decisions you make daily — the north star is what makes the daily decisions point the same way.