Walk into most offices and you'll find a mission statement on the wall that nobody can recite and nobody uses to decide anything. The problem usually isn't the writing. It's that the company never settled what kind of statement it was making, a reason for existing, a picture of the future, or a fight it intends to win. Those are three different jobs, and a sentence trying to do all three does none of them.

The quick version

  • Purpose is why you exist beyond making money, it barely changes. Mission is what you do now for whom. Vision is the future you're building toward. Strategic intent is the specific, ambitious win you're obsessed with, usually beyond your current means.
  • Collins & Porras split the durable part (purpose + core values) from the changeable part (a long-range goal). Hamel & Prahalad add the stretch: an intent so big it forces invention.
  • The evidence is sobering, across 20 years of studies, the link between having a mission statement and financial performance is small and inconsistent. The words don't create value; what people do with them does.
  • Write each one to pass a test: does it help someone on your team say no to something attractive this week? If not, it's decoration.

The idea in depth: four words, four jobs

The cleanest way to separate these terms comes from Jim Collins and Jerry Porras in "Building Your Company's Vision" (Harvard Business Review, September–October 1996). Their central move is to split a company's identity into two halves: a core ideology that should never change, and an envisioned future that you're deliberately trying to reach. Core ideology is itself two things, core values (the handful of tenets you'd hold "even if they became a competitive disadvantage") and core purpose (your "fundamental reason for being," beyond making money).

That last phrase is doing a lot of work. Purpose, in their framing, isn't a goal you complete; it's a star you steer by and never reach. Their example has stuck for thirty years: a purpose like "to make people happy" (Disney) can never be ticked off, which is exactly the point. So here's the test to apply: when you draft a purpose, check that it can't be finished. If your "purpose" could be achieved and crossed off a list, you've written a goal, not a purpose, and you'll be rudderless the day you hit it.

The envisioned future is where Collins and Porras put the ambition. This is the home of the BHAG, the "Big Hairy Audacious Goal," which they define in Built to Last (1994) as "an audacious 10-to-30-year goal to progress toward an envisioned future." A real BHAG, per Collins, has a clear finish line and "only a 50% to 70% probability of success", Kennedy's man-on-the-moon-by-the-decade's-end being the archetype. Which gives you the rule: a vision needs a finish line and a date. "Be the market leader" is a mood; "reach a million paying small businesses by 2032" is something a team can organise around and know whether they've hit.

"Core purpose is the organization's fundamental reason for being", and it should never change. The strategy chasing it should change constantly.

Strategic intent: the ambition that outruns your resources

If Collins and Porras give you the architecture, Gary Hamel and C.K. Prahalad give you the engine. Their 1989 article "Strategic Intent" (Harvard Business Review, May–June 1989; winner of the McKinsey Award) studied how companies like Komatsu, Canon and Honda overtook far larger Western incumbents. Their finding was uncomfortable: the winners started with ambitions "far bigger than their resources and capabilities." Canon set out to "beat Xerox." Komatsu's was "encircle Caterpillar." These weren't forecasts of what the numbers allowed, they were obsessions the whole organisation carried for decades.

This is the part conventional strategy gets backwards. Classic strategic planning asks you to fit ambition to available resources. Strategic intent deliberately creates a misfit, a gap between where you want to be and what you currently have, and uses that gap as the forcing function for invention. The stretch is the strategy. In practice that means setting a goal your current resources can't reach, then treating the shortfall as a design brief rather than a reason to back off. The question shifts from "what can we afford to attempt?" to "what would we have to become?"

The risk is obvious and worth naming. A stretch goal with no credible path is just pressure, it burns people out and breeds the kind of cut-corners behaviour that turns up in the post-mortem. Hamel and Prahalad's intent worked because it came paired with what they called "corporate challenges": concrete, near-term milestones that built the capability ladder rung by rung. Intent without a ladder is wishful thinking with a deadline.

The honest limitation: the words are not the work

Here's the part most articles on this topic skip. Decades of research have failed to show that simply having these statements makes a company perform better. The most thorough look, Sebastian Desmidt, Anita Prinzie and Adelien Decramer's "Looking for the value of mission statements: a meta-analysis of 20 years of research" (Management Decision, 2011), pooled two decades of studies and found only "a small positive relation between mission statements and measures of financial organizational performance," with effect sizes scattered widely (roughly 0.08 to 0.41) depending on how researchers measured things. Translation: on average, a small and unreliable link.

That isn't an argument for skipping the exercise. It's an argument about where the value lives. A statement on a wall changes nothing. A purpose that a team actually uses to decline a lucrative-but-off-mission deal changes the company. Cynthia Montgomery, former head of the strategy unit at Harvard Business School, makes this point in The Strategist (2012): purpose only matters when it's something "people would miss" if the organisation disappeared, and when the leader treats being "the architect of organizational purpose" as a live, ongoing job, not a launch-day deliverable. The upshot for you: judge your statements by their use, not their prose. If no decision in the last quarter turned on them, they aren't strategy yet; they're branding.

flowchart TD
    P(["Purpose, why we exist (never changes)"]) --> M(["Mission, what we do now, for whom"])
    M --> V(["Vision, the future we're building (with a date)"])
    V --> SI(["Strategic intent, the specific win we're obsessed with"])
    SI --> A(["This quarter's moves, what we actually do"])
    A -. "decisions feed back, refine the mission" .-> M
The four terms as a ladder from the enduring to the immediate, each one should constrain the level below it. Leaders Loop

A worked example: a small B2B software firm

Take a fictional company, call it Ledgerly, a 40-person firm selling bookkeeping software to tradespeople. (Figures and statements below are illustrative.) Watch how the four words pull apart once you force the distinction.

Their first attempt was a single sentence: "To be the leading bookkeeping platform for trades, delivering world-class software our customers love." It fails every test. It can be finished ("leading", then what?), it has no date, and it would help nobody choose between two roadmap items on a Tuesday. Reworked into four jobs, it looks like this:

  • Purpose (never changes): "Give people who work with their hands their evenings back." Unfinishable, and it instantly explains why they obsess over a 90-second invoicing flow rather than a feature-count arms race.
  • Mission (what we do now): "Bookkeeping software that a sole-trader electrician can run from a van in under five minutes a day." Specific customer, specific job.
  • Vision (future, dated): "By 2032, the default financial tool for 250,000 UK trades businesses." A finish line you can measure against.
  • Strategic intent (the obsession): "Make every accountant's bolt-on irrelevant for a sole trader." Bigger than their current capability, which is the point. It tells engineering what to invent next.

Now the payoff. A partnership offer arrives: white-label the product for a payroll giant's enterprise clients. Good revenue. Against the old statement, you'd say yes, it's "leading" and "growth." Against the reworked set, you can see the cost: enterprise clients aren't sole traders, the integration work starves the van-in-five-minutes mission, and it moves them away from the 2032 vision. The distinction did real work, it let a leader decline attractive money for a defensible reason. That is the entire test.

flowchart LR
    O(["Tempting offer: enterprise white-label deal"]) --> Q{"Does it serve the purpose & vision?"}
    Q -- "No: not sole traders, starves the core" --> N(["Decline, with a reason the team understands"])
    Q -- "Yes: pulls toward the 2032 goal" --> Y(["Pursue, and resource it properly"])
A statement earns its keep the moment it helps you say a confident no. Leaders Loop

Frequently asked questions

What's the actual difference between a mission and a vision?

Tense and finish line. Mission is present-tense, what you do today, for whom. Vision is future-tense and dated, the state you're building toward. If your "vision" describes what you already do, it's a mission wearing the wrong label. If your "mission" has a 2032 deadline, it's drifted into vision territory.

Do we really need all four?

You need the distinctions more than the four labelled paragraphs. A small team can carry purpose and strategic intent in their heads and skip the formal vision document. The danger isn't having fewer statements, it's having one statement that quietly tries to be all four and so guides nothing. Keep what your people actually use.

Isn't "purpose" just marketing now?

Often, yes, which is the trap. The Desmidt meta-analysis is the evidence that a published purpose, on its own, does little. The test for a real one (from Montgomery) is subtraction: would customers or staff genuinely miss you if you vanished, for a reason other than the product itself? If the honest answer is no, write a smaller, truer purpose rather than a grander, emptier one.

How ambitious should a strategic intent be?

Beyond your current resources, but with a visible path. Hamel and Prahalad's examples deliberately outran the means available, but they were paired with near-term "corporate challenges" that built capability in stages. Collins' BHAG guidance lands in a similar place: aim for roughly a 50–70% chance of success. Certain is too small; impossible just demoralises.

How do we know if ours are working?

Audit decisions, not documents. Look back over the last quarter: which choices, a deal declined, a feature cut, a hire made, can you trace to one of these statements? If the answer is none, the statements aren't yet operational. That's a more useful signal than any wording workshop.

Related in the Toolkit

Vision and intent sit at the top of the strategy stack; everything below translates them into competitive choices. Start with where the choices get made, the levels of strategy, and how you read the terrain before setting intent, via the diagnostic frameworks.

Where to go next