A vision statement is a single, specific declaration of where your company is going and by when. That is the whole definition. If you can read it and immediately picture what the company looks like when it succeeds, it is working. If you have to interpret it, it is not.
Most vision statements fail that test. They are broad, feel-good phrases that say nothing about direction, nothing about scale, and nothing about time. Teams cannot use them to make decisions because nothing in the statement tells them what to prioritize.
This is the guide I wish I had found when I was building one.
What is a vision statement
A vision statement is the future-state description of your organization. It answers one question: where are we going?
Not what we do (that is your mission). Not how we do it (that is your values). Where we are going.
A strong vision statement has three characteristics. It is specific enough that you would know when you have achieved it. It is ambitious enough that achieving it is not inevitable. And it is short enough that every person in the company can say it without looking it up.
Microsoft's early vision statement, "a computer on every desk and in every home," met all three. You could picture the outcome. Achieving it was not obvious when they wrote it. And a child could repeat it.
That is the bar. Most companies do not get close.
The failure mode is abstraction. "Empowering people to achieve more" is not a vision statement. It is a tagline. It tells you nothing about the industry, the customer, the scale, or the horizon. A team cannot use it to decide whether to open a second location, hire a sales rep, or cut a product line. A real vision statement can guide all three decisions.
Vision statement examples
Good vision statements tend to share a structure: a specific outcome, for a specific group, at a specific scale or within a specific horizon.
Realistic examples from organizations that got this right:
- "To be the world's most customer-centric company" (Amazon). Clear direction. Measurable in relative terms. No ambiguity about the competitive arena.
- "To organize the world's information and make it universally accessible and useful" (Google). Broad scope, but specific about what the product does and for whom.
- "Become the Nike of the cycling industry" (Specialized Bicycles, attributed). One sentence. Anyone who knows Nike understands the target.
At Sneeze It, the version I keep on the wall is about the number of clients we serve and the category we own. It is not public, but the structure is: [specific outcome] [specific vertical] [specific horizon]. You could test whether we hit it on a specific date.
Bad vision statements look like these:
- "To be the leading provider of innovative solutions." Leading where? Innovative how? Solutions for whom? This sentence has six words that do the work of zero.
- "We exist to make the world a better place." Aspirational in tone, but completely untestable. Everyone can claim this, so it guides no one.
The test: hand it to a new hire on day one. Ask them to use it to make one real decision. If they cannot, rewrite it.
You can also look at the OTP blog post on core values for how values and vision work together in a tight operating system.
Vision statement vs mission statement
These two get confused constantly. The confusion is understandable because many companies publish both and neither one is written clearly enough to tell them apart.
The simplest distinction: a mission statement describes what you do now, for whom, and why. A vision statement describes where you are going.
Mission is present tense. Vision is future tense.
Tesla's mission is "to accelerate the world's transition to sustainable energy." That is what they do today, stated in active terms. Their vision, if they published one in the traditional sense, would describe what the world looks like once they have succeeded at that mission.
Another way to think about it: your mission answers "why do we exist?" Your vision answers "what do we become?"
In the EOS framework developed by Gino Wickman, this concept maps closely to what EOS Worldwide calls the "10-Year Target" in the Vision/Traction Organizer. The target is where the company is going. The core focus (purpose/cause/passion) is closer to mission. They live in different parts of the document because they answer different questions. OTP is not affiliated with or endorsed by EOS Worldwide; we simply run alongside it.
Some founders flip these in conversation. That is fine as long as the team knows what each document is for. The naming matters less than the clarity.
The practical question: does your statement describe what you do today, or where you are going? If it is the former, it is a mission statement. If it is the latter, it is a vision statement. You want both. Do not let one do the other's job.
See also the OTP post on mission vs values for how to layer these documents so they actually inform decisions.
How to write a vision statement
Here is the process I have used and watched work across multiple companies.
Start with the ten-year question. Ask your leadership team: if this company succeeds at everything it intends to, what does it look like in ten years? Not revenue targets first. Not headcount. The picture. What does the company do? How many people does it serve? What is it known for? What category does it lead or create?
Write down every answer, no matter how rough.
Look for the common thread. The founders in the room usually agree on more than they think. The specific details will differ, but somewhere in the answers there is a direction they all believe. Find that direction and name it.
Write one sentence. Not a paragraph. One sentence. If you cannot say the destination in one sentence, you do not know the destination yet. Go back to step one.
Test the sentence against three questions:
- Is it specific enough that we could measure whether we hit it?
- Is it ambitious enough that it requires us to grow or change to achieve it?
- Can every person in this company say it without looking it up?
If the answer to all three is yes, you have a working vision statement. It does not need to be perfect. It needs to be specific, memorable, and true.
Run it for 90 days before printing it on anything. Use it in meetings. Use it to make one real decision. See whether it holds. Most first drafts need one revision after you have tried to use them.
One mechanical tip: a time horizon helps. "By 2030" or "within five years" makes the vision testable in a way that an undated statement is not. Undated visions drift. Dated ones create urgency.
At Sneeze It, when I brief Radar (our chief-of-staff agent) at the start of each week, the vision statement is the first reference point. If a proposed initiative does not move us toward it, it goes to the bottom of the priority list. That is how you know a vision statement is working: it changes where things go in the queue.
Frequently asked questions
What is the difference between a vision statement and a mission statement? A mission statement describes what you do and why you exist today. A vision statement describes where you are going and what you intend to become. One is present tense; the other is future tense. Most organizations need both, and they should not overlap or contradict each other.
How long should a vision statement be? One sentence. Two at the absolute maximum. If it takes a paragraph to explain where you are going, the destination is not clear enough yet. Brevity is not a style preference; it is a signal that the thinking is finished.
Does a vision statement need a time horizon? It does not need one, but it is better with one. A dated vision ("by 2030, the largest independent fitness marketing agency in North America") is testable. An undated one ("to be the largest...") is directional but can be deferred indefinitely. Dated visions create urgency. Undated visions get revised without accountability.
How often should you update your vision statement? Not often. The whole point of a vision statement is that it is stable enough to guide decisions over years, not months. If you are updating it every year, either the business has pivoted dramatically or the original statement was not a real vision. A good revision cycle is every three to five years, or when a significant strategic shift actually changes the destination.
How do you know if your vision statement is working? You know it is working when your team cites it in real decisions without being prompted. If someone in a meeting says "that does not move us toward the vision" and everyone knows what they mean, the statement is working. If it only appears on the website and not in the room, it is decoration.
Run it in OTP
Once your vision statement is written, track the strategic goals and KPIs that move you toward it on a shared scorecard where humans and AI agents hold seats side by side. When Tally pushes updated numbers each week and Dirk reports pipeline progress, both are measured against the same destination your vision statement names.
In Claude Desktop or Cursor or any MCP client, add this block:
"otp": {
"command": "npx",
"args": ["-y", "@orgtp/mcp-server"]
}
Restart the client. Then ask: "Use OTP to show me our org chart and scorecard so I can see whether each seat's KPIs connect to our ten-year vision."