Vision Is the Destination. Mission Is the Vehicle. Strategy Is the Route.

The team had a good vision. Genuinely good – specific, ambitious, the kind you could picture. It was a large product org run like a skunkworks, and the vision was not the problem.

The mission was hand-wavy. And there was something that approximated a strategy, except nobody could tell me what it was. Different people gave me different versions, and none of them could point at where it was written down.

So day-to-day build decisions got made by whoever spoke loudest in the room. Sometimes a founder. Sometimes a customer on a sales call. Sometimes a PM improvising in the moment because a decision was needed and no one else was going to make it.

The features weren't bad. That was the confusing part, and it's why the problem had gone unnamed for so long. Each one was defensible on its own. They just didn't add up to a coherent thing, because nothing was holding them to one.

Three words that are not interchangeable

Most companies use these three as rough synonyms, shuffle them between slides, and wonder why alignment keeps slipping. They're different objects and they answer different questions.

Vision is what the world looks like if you succeed. It is not what you do; it is the world your doing creates. That's the destination.

Mission is how you intend to make the world look that way – the work you do, the thing you build, your role in making the vision real. That's the vehicle.

Strategy is the path you've chosen through the landscape of possibilities to get there. That's the route.

Vision is the destination. Mission is the vehicle. Strategy is the route.

Once you hold them apart, the failure mode in that skunkworks becomes obvious. They had a destination and no route. Everyone agreed on where they were going and nobody could say which way they were driving, so every fork in the road got resolved by whoever was most confident in the car.

Why a missing route doesn't announce itself

Here's what makes this hard to catch from inside: a team with no stateable strategy does not feel lost. It feels busy.

Decisions still get made, at the normal rate. Work still ships. Sprints still close. The absence shows up only in aggregate, quarters later, when someone tries to explain how the last eight features relate to each other and finds they can't. The features weren't wrong. The relationship between them was never specified.

A missing vision, by contrast, announces itself constantly. People ask what we're doing here. A missing mission produces visible confusion about scope. A missing strategy is silent, because its job is to constrain choices, and an unconstrained choice doesn't feel like a failure at the moment you make it. It feels like autonomy.

The data says the same thing in flatter language

The 2026 product-management survey work lands on this from a different direction.

26.2% cite strategy not being clearly translated into roadmap criteria as a cause of misalignment – which is precisely the destination-without-a-route condition. And confidence that non-product teams understand the product strategy averages just 3 out of 5, with alignment to company goals at 3.5 and confidence in measuring business impact at 3.

The sharpest version comes from eBay's Ashay Satav, quoted in ProductPlan's report: "Most teams aren't confused by what the strategy says; they're confused by what actually gets rewarded, prioritized, and reviewed. When OKRs, roadmaps, funding decisions, and exec narratives drift even slightly, teams default to their local goals."

Default to their local goals. That's the survey's name for whoever spoke loudest. When the route isn't stated and enforced, people navigate by what's nearest – their team's metric, their director's preference, the customer who called this week. Every one of those is a reasonable local heuristic, and collectively they produce drift.

It's worth adding that 40% of teams report strategy, discovery, roadmaps and launch plans living across multiple tools with limited or no integration. A route nobody can locate is functionally the same as no route.

Pioneers, settlers, and the direction of the city

There's a framework I keep coming back to here – pioneers, settlers, and town planners.

A skunkworks project or a pilot is typically made of pioneers, which is fine and correct. What I keep seeing is a project that's the idea of a pioneer, executed entirely by pioneers, where a settler or a town planner doesn't get involved until after the fact. By then it's too late.

The better arrangement is to have the town planner make sure that the pilots getting built could actually drive toward the company's vision and mission, and align with its strategy – or at least aren't too far from it. What's the point in having pioneers working to expand the city in the wrong direction?

That's the role the missing strategy was supposed to play in the org I opened with. Not to slow the pioneers down. To make sure their expansion pointed somewhere.

What a stateable route actually sounds like

The bar I'd set is lower than most strategy documents clear, and harder than most companies manage.

A usable strategy names what you're choosing and what you're giving up, in a sentence someone can repeat without notes. "We're going deep on the workflows of mid-market operations teams, and we're not chasing enterprise procurement this year even when the deals look good." That's a route. It tells a PM facing a fork which way to turn, and – more importantly – it tells them which attractive thing to decline.

What usually exists instead is a list of goals. "Grow enterprise revenue, improve retention, expand the platform." Those are destinations wearing a route's clothes. They tell you nothing about which path, and because they're individually unobjectionable, they can't resolve a conflict between two reasonable options. Ask someone to use it to say no and watch what happens.

The compression test I like: can you state it in one sentence that contains a not? If there's no "not" in it, it isn't constraining anything, and a strategy that constrains nothing is just enthusiasm with a deadline.

How to find out which one you're missing

Ask five people, separately, not in a meeting:

1. What does the world look like if we succeed? (vision)
2. What are we building to make that happen? (mission)
3. Why this path and not the obvious alternative? (strategy)

Five consistent answers to one and two and five different answers to three is the most common result I get, and it's the skunkworks pattern exactly. If nobody can answer three without reconstructing it on the spot, you don't have a strategy – you have a set of decisions that happened to get made, and a story that gets assembled afterward to explain them.

The fix isn't a document, though it probably produces one. The fix is that the route has to be stateable by someone other than the person who wrote it, and it has to be the thing you point at when you say no. A strategy nobody invokes under pressure isn't a strategy; it's a slide.

That's the test I'd run on yours. Not whether it exists. Whether anyone has used it to turn something down this quarter.