Vision, Mission and Values: Examples and How to Write Them

What is the difference between vision, mission and values?

Vision is where you are going, mission is what you do to get there, and values are how you behave while doing it. They answer three different questions, operate on three different time horizons, and fail in three different ways.

The order matters less than the distinction. Some companies write the mission first because it is concrete, then derive the vision; others start with the vision because it sets the ambition. What breaks is writing one statement and dressing it up three ways.

Why do most vision and mission statements fail?

They fail because they are written for the website rather than for a decision. A statement that cannot settle an argument has no operational value, no matter how well it reads.

Three failures recur. The first is generality: “to be the leading provider of innovative solutions” could belong to any of ten thousand companies, and describes an outcome rather than a contribution. The second is aspiration without mechanism: a vision so large that nobody can name the first step, which makes it inspiring for a week and irrelevant by the second quarter. The third is values that cannot be violated, which means they cannot be enforced — and a value nobody can breach is not a value, it is a compliment.

The research here is more cautious than the consulting decks suggest. A 2018 systematic review of 53 studies in the *Journal of Management & Organization* concluded that mission statements are widely used in practice but thinly researched in theory. A 2024 study of 247 Philippine-listed firms found that having a mission statement, and naming customers in it, were positively associated with performance — while stuffing it with society and public-image language was negatively associated. Statements that name a specific stakeholder and a specific job outperform statements that try to please everyone.

Bain’s research adds the emotional half. In a survey of 2,500 employees, fewer than 15% said their job inspired them, and firms that did inspire people connected individual work to a mission people could feel. Bain also noted the lifecycle problem: purpose is strongest at founding and fades as the organisation ages, and a bold new mission statement that nobody takes seriously makes the fade worse.

How do you write a vision statement?

Write the vision as a description of the world you are trying to create, in the present tense, in one sentence a twelve-year-old could repeat. Then test it against three questions: is it bigger than the company, is it specific enough that a stranger could tell whether you are winning, and would a reasonable person disagree with it?

IKEA’s vision — “to create a better everyday life for the many people” — passes because it names a beneficiary (“the many people”) and a domain (“everyday life”), and because the alternative (better everyday life for the few who can afford it) is a real position held by other retailers. Patagonia’s “we’re in business to save our home planet” passes a harder test: it is uncomfortable, it implies the business could fail at it, and it constrains decisions about materials, ownership and dividends.

A useful drafting sequence:

1. Name the beneficiary. Who is better off if you succeed? Be specific: commuters, small clinics, first-time managers.
2. Name the change. What is different about their life? Not “empowered” — what can they now do that they could not before?
3. Set the horizon. Ten years, not three. A vision that will be achieved by next Christmas is a goal.
4. Cut every word that could appear in a competitor’s version. If the sentence survives the swap, it is not yours.
5. Read it aloud to someone outside the company. If they ask a follow-up question about what you mean, the statement is not finished.

> Common mistake: Writing the vision as a financial target. “To be a $100 million company by 2030” is a plan, not a vision. It tells employees what the founders want, not what the work is for — and it stops being motivating the moment the target is missed.

How do you write a mission statement?

A mission statement should say what you do, for whom, and why it matters, in a form that fits on a business card. The strongest ones read like a job description for the company, not a description of the market.

IKEA’s market position statement is a good model: “to offer a wide range of well-designed, functional home furnishing products at prices so low that as many people as possible will be able to afford them.” It contains a product, a quality claim, a price constraint and a beneficiary — four commitments, any of which could be broken. Microsoft’s “empower every person and every organisation on the planet to achieve more” is broader but still names a beneficiary and an outcome, which is why it survives being repeated by 200,000 employees.

Three practical rules:

• Start with a verb. “We help…”, “We build…”, “We make…”. Noun phrases drift into abstraction.
• Include the constraint. The price ceiling, the excluded customer, the thing you refuse to do. Constraints are what make a mission memorable and what make it useful in a sales meeting.
• Keep it under 25 words. Not because brevity is holy, but because a 60-word mission cannot be recalled under pressure, and a statement nobody can recall cannot guide anyone.

Distinguish the mission from the value proposition: the value proposition is for customers (“faster onboarding, half the cost”), while the mission is for everyone who decides what to build next. They can overlap, but the mission must survive a change in product line.

How do you write values people actually use?

Write values as behaviours that can be observed, rewarded and — crucially — violated. Each value needs a sentence describing what it looks like on a good day and a sentence describing what it forbids.

Patagonia’s core values, rewritten in 2022 on the eve of its 50th anniversary, are worth studying because each one contains a test. “Build the best product” is paired with a definition of what “best” means and an explicit statement that repair and durability matter more than novelty. “Examine our practices openly and honestly” commits the company to publishing what it finds. None of that is a poster; all of it constrains something.

A workable format for each value:

• Name it in the team’s own language. “Say the hard thing” beats “courage” because the first is an instruction.
• Write the behavioural test. “We raise a delivery risk in the same week we learn about it, even if the news is unwelcome.”
• Write the anti-behaviour. “We do not commit to a date we cannot defend, even to close a large deal.”
• Name the trade-off. Every real value costs something. A value with no cost is a preference.

Then audit. Take the last twenty decisions your team made — a hire, a discount, a scope cut, a vendor choice — and ask which value informed each one. If the answer is “none” for most of them, the values are not operating. That is not a moral failure; it is a design failure, and it is fixable by rewriting the values around decisions you actually face.

What do strong examples have in common?

Strong statements are specific, falsifiable, and visibly expensive. Weak ones are interchangeable. The table below compares statements that work with the pattern they avoid.

Notice what is missing from every row: the words “passion”, “excellence”, “innovation” and “synergy”. Those words describe aspirations everyone holds, which means they discriminate nothing.

What does this look like for a 40-person company?

A hypothetical but fully reproducible example. A 40-person software company has six values on its website, written by the founders in 2019. Leadership suspects nobody uses them, so it runs an audit.

Step 1: measure the current state. A 90-minute workshop with the eight people leads to 62 candidate behaviours. Nobody can recall more than two of the six existing values. A review of the last 20 documented decisions finds zero references to any value.

Step 2: cost the exercise. Eight people × 90 minutes × three sessions = 36 person-hours. At a fully loaded $65 an hour, that is $2,340. Compare that with the cost of one bad senior hire — roughly $40,000 in salary, onboarding and replacement — to see why a half-day of alignment is cheap.

Step 3: cut to four. The 62 behaviours cluster into four themes: shipping small and often, saying the hard thing early, refusing to promise dates the team cannot defend, and writing things down so the next person does not have to ask. Each is a behaviour, not a virtue. Each can be violated in a meeting.

Step 4: attach them to mechanisms. The “no undefendable dates” value becomes a rule in the sales-to-delivery handover. The “write it down” value becomes a definition-of-done item. The “say the hard thing” value becomes a standing agenda item in the weekly review.

Step 5: use them in a real decision. A $180,000 enterprise deal — about 18% of quarterly revenue — requires a committed delivery date the engineering lead believes is 30% likely. Without a value, the discussion escalates for three weeks and ends in a compromise nobody owns. With the value, the decision takes 20 minutes: offer a discovery phase with a fixed date and no delivery commitment. The deal may be lost; the cost of a missed date would have been a 10% service credit ($18,000) and roughly six engineer-weeks of unplanned work.

That is the only real test of a values statement: it made an expensive decision faster and more consistent.

How do you turn the statements into operating rules?

Connect each statement to a mechanism — a hiring scorecard, a promotion criterion, a decision log, a meeting ritual — or it will not survive the first busy quarter. Statements change behaviour through process, not through repetition.

Four mechanisms do most of the work:

• Hiring. Score values-based evidence in the interview, weight it explicitly (for example 40% values, 60% craft), and write down the evidence. A candidate who is brilliant and behaves against a stated value is a future escalation.
• Promotion. If the values appear in the promotion rubric, they are real. If only delivery metrics do, the values are decorative — and everyone learns that within one cycle.
• Decision records. Log the decision, the options, and which value or principle was decisive. This is the cheapest way to make values observable, and it gives new managers a library of precedents.

This is where a workspace earns its keep. If goals, projects, tasks and decision notes live in different tools, the values never appear next to the work they are supposed to govern. Doitify is our product, and the relevant part here is narrow: goals, projects, tasks and written decisions in one place, so a decision note can reference the value it applied and a new hire can read the precedent.

How often should you revisit them?

Revisit the mission and values every 12–24 months, and the vision every 3–5 years — or immediately after a change in ownership, business model or market. Frequent rewrites signal that the statements were never serious; no revision ever signals that the company has stopped listening.

A practical cadence: review the values in the annual planning cycle, ask in the engagement survey whether people can name two of them, and check whether the last quarter’s decisions can be traced to them. Keep the document under version control with dates and a one-line note on what changed and why. The history is often more useful than the current text, because it shows whether the organisation is drifting or deliberately evolving.

What are the common mistakes?

• Writing them by committee and publishing by consensus. A statement with seven authors and no editor reads like a policy document.
• Confusing values with competencies. “Strong analytical skills” is a hiring requirement, not a value.
• Choosing virtues that cannot be observed. Honesty and respect are outcomes of specific behaviours; name the behaviours.
• Announcing values before changing a single process. The announcement creates cynicism that takes years to undo.
• Letting leaders opt out. One executive exempted from a value teaches the organisation that the values apply to juniors.
• Rewriting when the problem is enforcement. If nobody follows the current values, a new set will not fix it; the mechanism will.

Conclusion

Vision, mission and values are three different instruments, and the most common failure is treating them as one. The vision sets the destination, the mission defines the work, and the values decide what you refuse to do on the way.

Write them specifically, keep them short enough to remember, and attach each one to a mechanism that can reward or punish behaviour. Then test them the only way that counts: find a decision from last quarter that they changed. If you cannot find one, you have written a website page, not a strategy.

If this post on vision, mission and values was helpful, you might also enjoy Project Management Software With CRM and Time Tracking: Best Options and What Are Task Dependencies in Project Management?.