Vision expires. Mission does not.

Vision and mission get written on the same slide.

Two days off-site, paper on the wall, and the same session produces both a vision sentence and a mission sentence. Both are written in the future tense, both sound ambitious, both sit on the same page of the deck. By the time the meeting ends, nobody in the room can say what actually separates them, and nobody minds, because both got written.

That is not surprising. Both sentences try to answer the same question — who are we — and side by side on a slide they read alike. Nobody objects, because both sound right, and objecting to a sentence that sounds right costs more in the room than letting it pass unexamined.

The difference is being looked for in the wrong place

Teams usually reach for a dictionary, trying to decide which sentence belongs under which heading. That is not a definitions problem. It is a time problem — and until the time question gets asked, the two sentences stay interchangeable.

Treated as a definitions problem, the argument runs in circles: one person says vision is the broader of the two, another says mission is the one that describes the daily work, and both are right about a true but incomplete definition. The meeting ends an hour later with a compromise sentence, and the compromise carries the same confusion forward.

A mission is a commitment that never ends. A vision carries a date.

A mission states who a company serves and why, and it lives in the present tense. It is not meant to finish; it holds for as long as the company exists, the way a decision's responsibility outlasts the meeting that made it. A vision is a different kind of sentence: a claim about something that is not true today and is meant to become true by a stated point.

Vision is the one that can be tested

The working test is simple: could this sentence turn out true or false on a specific date? If yes, it is a vision. If the sentence stays true forever and never resolves into a yes or a no, it is a mission, whatever heading it was filed under.

"Be the most trusted partner in our category" is an unending commitment; it asks for the same answer whatever year it is checked. "Lead our region by 2029" is testable; when 2029 arrives, it is either true or it is not. Both are legitimate sentences. Put them in the same box and one starts doing the other's job.

The harder part of the test is catching sentences that sound like a vision but are actually a mission in disguise. "Always give our customers the best" reads like a vision because it is large and ambitious, but it can never be checked against a date, because "the best" can always be redefined. Filed as a vision, a sentence like this leaves the company living against a target it never reaches and never fails to reach either.

Mixing the two costs the vision its testability first.

When a mission's permanence leaks into a vision, the vision turns into a claim that never resolves either. A sentence written eight years ago still sits in the deck, and nobody thinks to read it against a date, because it was never attached to one.

A vision that never ends is not really a vision

At that point the company has either quietly reached the target and not noticed, or missed it and not noticed. From outside, the two look identical: a sentence on the wall that nobody is being held to.

A vision that never ends is a vision nobody is accountable for.

The cost to the team is quiet and it compounds. Someone who joins two years in hears the same vision sentence, notices that nobody is tracking progress against it, and stops taking it seriously. The company does not notice this happening, because nobody was really looking at the sentence anymore; sitting on the slide was treated as enough.

This is a narrower version of the observation that setting direction is not a document exercise: there the problem was a document that ruled nothing out. Here the problem is a document that was never tied to a date. Both come from the same place — a sentence written as though it would never have to be checked.

When a mission takes on a deadline, the commitment turns temporary.

The reverse case is harder to spot. Once a mission is given a date — "we will deliver X to customers by 2027" — it starts reading as a line in the strategy rather than as a promise. When the strategy changes, that line quietly drops with it, even though the promise underneath it was supposed to outlast any one strategy.

A commitment should not move when the strategy does

This shows up most often at the planning cycle. A new plan gets written, the old mission sentence gets reviewed alongside it, someone says it no longer applies, and a new one replaces it. But what changed was the strategy — how the company serves customers — not who it serves or why, and the mission itself never needed to move with the plan.

The practical way to keep the two apart is to ask what happens to each sentence when the strategy changes.

• Mission: who we serve and why. It should read the same after the strategy changes.
• Vision: what will be true by which year. It may need rewriting when the strategy does.

A sentence that survives a strategy change unchanged is a mission; one that needs rewriting is a vision — and a sentence written without knowing which box it belongs in gets lost the first time a strategy meeting tests it against the wrong rule.

From the field.

When we sit with companies that have blurred vision and mission, the gap is rarely a lack of definitions. It is a reluctance. Putting a date on a vision means agreeing, in advance, to be checked against it on that date, and most leaders are not ready to sign up for that reckoning yet — so the sentence gets written to never end.

Setting a date is a decision to be accountable

The reluctance is personal, not organizational. A founder or a general manager does not want to sit in a room five years from now and say it did not happen; so the sentence gets written in a way that the question can never be asked. What looks like a missing definition is usually a deferred decision about being held to account.

What we actually do is not sort one sentence from the other. It is build a room where a leader can say out loud which sentence they will be checked against, and when. Once that date exists, a vision stops being a wish on the wall and becomes a claim read again on a set interval. How we work follows the same order: name what gets tested and when, then write the document.

The observation from the field is this: a vision that never changes is usually not resolute. It is protected. As long as a sentence is never tested, nobody is proven wrong — and nobody is proven right either.