In this article, I will present three unique articulations of the product northstar.
We live in an era where the act of building has become almost frictionless. Generative AI allows us to move from concept to code at a velocity unimaginable just two years ago. But this speed introduces a tricky risk. When a team can ship features almost as fast as they can think of them, they often end up building a highly sophisticated engine for generating noise. Without a fixed point on the far horizon — a northstar — that speed merely accelerates the journey toward a random destination that neither fills a competitive void nor solves any meaningful user need.
Every organization needs to paint its future self, to render its five- to ten-year dream, in a simple, visceral way.
To see why this matters, look at the alternative. I recently worked with a marketing software firm that dedicated much of its effort to chasing "whales" - those massive enterprise customers or partners that promise a sudden windfall. This was described as "strategy" (but was actually a reactive loop.) Every quarter, the roadmap bent toward whichever large opportunity appeared most promising. In the moment it feels like momentum, but in reality, its a dangerous and distracting dependence.
There are two outcomes in this model, and neither is great. If you lose the deal, you lose revenue and time. If you win, you inherit someone else's strategy. Your product direction becomes a reflection of a single customer's idiosyncratic needs, effectively turning you into a high-priced development shop. Without a firm sense of identity and a set compass, you fail to build the differentiated moat necessary for the long haul. While this trap is most obvious in enterprise software, the lesson holds for consumer and SMB companies as well—the distractions are different, but the risk of losing your way is just as high.
The Vision vs. The Metric
A product northstar is a declaration of what your product will be in the future, expressed with enough simplicity that it becomes immediately obvious to anyone who sees it. It answers the question "Where are we going?" using metaphors that the entire organization can internalize.
It is important to distinguish the northstar vision from a northstar metric. Metrics are concrete and necessary for measurement. They tell you about scale. But saying a company will increase revenue 100X offers zero inspiration. It provides an inkling of size, but it says nothing about the journey or the reason behind the work. It doesn't inspire better decisions in ambiguous moments.
A northstar vision provides the guiding light. It provides a mental model of the future that elicits emotion and a sense of purpose. For many software companies, this means contextualizing a world five or more years ahead. It is the unwavering goal for everyone in the room. I have three ways to convey this vision. Each provides a unique lens into that long-term picture.
Three Ways to Make the Future Tangible
Over time, I've found that a strong northstar shows up in three complementary forms. Each one captures the same future from a different angle, and together they create clarity that no single artifact can.
1. The Conceptual Northstar (The Analogy)
The simplest way to describe a future state is to anchor it in something people already understand.
At a healthtech company I worked at years ago, we were trying to modernize the patient check-in process. At the time, the experience across most health systems was fragmented, paper-heavy, and inconsistent across locations.
We needed something clearer than "improve intake." Our CEO logged the most airline miles in the company and immediately saw the transformation that had happened in the airline check-in process. That became the analogy we rallied around.
By that point, most travelers had experienced a seamless, multi-device journey: check in on their phones, get real-time updates, and move through kiosks and gates without friction. It was consistent across time, location, and channel … and your data followed you in helpful ways.
That became our northstar. Not "build better forms." Not "increase completion rates." Be as seamless as airline check-in.
The effect was immediate. People across our company could easily understand it, even picture it. And more importantly, they could spot when something we were building didn't serve the long-term vision.
A useful constraint: Look outside your industry for these analogies. If another company in your space has already demonstrated the future state, you are already too late to innovate. You are simply playing catch-up (trying to be better, not different.) Winning strategies come from the gaps between industries, where expectations haven't yet been imported.
2. The Northstar Hero Flow: The Visual Journey
Once the analogy is in place, you must envision the experience. This is the hero flow. The goal here is to illustrate the capstone steps of the envisioned experience so that a viewer understands the future customer journey in three minutes or less. Details are the enemy of this endeavor.
To create a hero flow, find the largest whiteboard available and outline the 15-20 most significant steps of the journey. More than that, and you have slipped into detailed design. These steps should combine your current "hardened" features with purely conceptual future-state functionality. If most of the steps already exist, you aren't stretching your vision far enough.
"Hero" refers to hitting only the highest points of the story. "Flow" means you are imagining a singular experience rather than a collection of disparate features. Think of it like a children's book. It should envision, align, and inspire.
Back to that healthtech example. Initially, the patient intake hero flow included approximately 30% of features already in production. The other 70% were purely conceptual. We included functions like demographics and consent, which were already part of our core data strategy, while adding aspirational elements like insurance eligibility and payments. By weaving them into one story, the entire company knew which gaps to close. This asset is essential for enabling even the most dispersed teams to thrive toward a singular goal.
Here's a simple structure you can use to support your whiteboard session. Think through the following as you're visualizing the steps:
1. Reframing the Starting Point What has to be true for the experience to begin differently than it does today? Step back from channels and screens—what changes about how, when, or why the user enters this experience at all?
2. Shifting the Burden of Orchestration What does the user no longer have to figure out, sequence, or manage themselves? Where does the system take on responsibility that is currently pushed onto the user?
3. The Moment of Transformation Where does the experience clearly surpass today's alternatives in a way that resets expectations? We'll beyond marginal improvement to something that makes the old way feel severely outdated.
4. The Shape of "Done" What does completion feel like in this future state? What clarity, confidence, or forward motion does the user leave with that they don't have today?
5. Invisible System Leverage What is happening behind the scenes to make this possible? What coordination, data synthesis, or decisioning disappears from the user's view but fundamentally powers the experience?
That's it. Apply the thinking of the five items above across 15-20 visual steps of the future customer journey. If the experience you end up with feels like a cleaner version of today, you're not pushing far enough; go back to the whiteboard until you're truly stretching.
A few practical notes:
- Focus on the "what," not the "how"
- Think big. In the patient intake example, it was not about the next bit of data we could collect from a patient; it was about entirely new capabilities we could add (insurance, payments, etc.)
- Keep it visually simple—it should read more like a storyboard than a spec
3. The Product Vision Statement: Rooted in Benefit
The final piece is an inspirational product vision statement. The statement provides concrete language to support the analogy and visuals. It's where you answer three things:
- Who is this for?
- What do they get that they can't get today?
- What changes because of it?
Tesla's early vision statement provides a nice example: "Create the automobile of the future: an all-electric car that's faster, safer, and more enjoyable to drive than gasoline cars." It identified the focus (the car of the future), the benefits (speed, safety, enjoyment), and the competition (gasoline cars). The statement was specific, grounded, and immediately understandable.
When I am workshopping with clients, I prefer a structured format that keeps the message high-level but specifically calls out the top-level customer benefits. A simple template that works:
The [clear choice / default platform] for [target audience] to…
– achieve [core benefit #1] – achieve [core benefit #2] – achieve [core benefit #3]
…resulting in [meaningful outcome]
For example:
The default platform for small businesses to…
– acquire new customers predictably – deepen relationships without manual effort – automate front-office operations
…so they can grow without adding staff or increasing complexity
This is concise. It covers a deep product portfolio but remains rooted in customer benefits. The statement holds up over time because it's focused on what the customer gains, not what the company builds, what the roadmap includes, or the company's financial goals. If you get this right, it becomes a stable reference point for years to come.
Measure the Future
A well-defined northstar does a few things that are hard to replicate any other way:
- It creates consistency across teams without requiring constant coordination
- It reduces roadmap drift, especially when new opportunities emerge
- It gives marketing, sales, and product teams a shared reference point
- It makes progress measurable by how much of the future is now real
At one company, we reviewed progress each quarter by mapping shipped capabilities back to the hero flow. This was not a vanity exercise, but a way to ask a simple question:
Are we actually building the future we said we would?
In some quarters, the answer was yes. Others, less so. But the visibility alone changed behavior.
Closing Thought
Many product organizations operate with more motion than direction. The systems they build reflect the accumulation of decisions made under pressure, in response to real constraints and real opportunities.
A product northstar introduces a different kind of constraint: one that is chosen rather than imposed.
It asks the organization to commit to a view of the future that is clear enough to guide decisions and durable enough to withstand change. It doesn't simplify the work. It gives the work a shape that can hold over time. And in an environment where building has never been easier, that shape is what keeps effort from dispersing into noise.