Leadership vision: how to create one your team can see and use

A leadership vision answers three questions for the people you lead: where are we going, what will it look like when we get there, and what follows from that today? For a team manager it is one or two sentences describing a visible end state, two or three choices it implies, and one thing the team will stop doing. Turning it into quarterly goals is where OKR software helps: each objective can point back to the vision, and each person can see how their work connects to it.

Most organizations leave a gap here. In Gallup research, only 22% of employees strongly agreed that their leaders have a clear direction for their organization. As of August 2025, only 16% of employees in the United States said their company's leadership made them enthusiastic about the future. A team manager cannot fix company strategy alone, but can make sure their own team knows where it is going and why.

People look to leaders for direction before anything else. In Gallup's research across 52 countries and territories, hope was the most common thing followers said they needed from leaders, followed by trust. A credible picture of the future is how a leader gives hope without empty promises.

Vision also has a measurable link to results. In a six-year study of 229 entrepreneur-CEOs, a communicated vision, together with goals and the leader's confidence, had direct effects on how fast the ventures grew. The key word is communicated: a vision in a leader's head does nothing.

At team level the cost of a missing vision is everyday confusion. Based on Gallup's work with companies worldwide, only about half of employees strongly agree that they know what is expected of them at work. Without a shared picture of where the team is going, people fill the gap with their own guesses, priorities collide, and every trade-off reaches the manager's desk.

These words get mixed up, and the confusion makes vision documents longer and weaker. Each answers a different question.

A useful rule of thumb: the vision should be the shortest item on the list, and the strategy the most specific. If your vision is longer than your list of choices, you have a values statement, not a vision.

The research on vision wording is unusually clear. In an archival study of 151 hospitals and an experiment with 62 groups of full-time employees, Carton, Murphy and Clark found that a large amount of vision imagery combined with a small number of values went with better performance. Their explanation is practical: imagery gives employees a shared sense of the ultimate goal, which improves coordination. The same research found the two habits most leaders have: communicating visions without imagery and overusing value-laden words.

Wharton's Andrew Carton calls the underlying problem the blurry vision bias: most people, leaders included, think abstractly about the distant future. The cost is not only inspiration. A vague vision stifles coordination, he explains, because different employees understand the goal differently. Two people can both agree with "deliver excellence for our customers" and pull in opposite directions.

Test every sentence with one question: could a new hire draw it? Then rewrite the abstract words into things someone could see.

Keep the values to three or fewer, and only those that change a real decision. A long list of values reads as balanced, but the hospital research suggests it dilutes the shared picture rather than strengthening it.

Most managers do not set company strategy, and a team vision that contradicts it creates friction. The job is translation: what does the company's direction mean for the work of this team?

1. Read the strategy for your team. List the two or three company priorities your team affects most. If they are not written down, ask your manager: "Which two outcomes matter most next year, and where does our team make the biggest difference to them?"
2. Find the visible end state. For each priority, describe what it will look like in your team's daily work when it is achieved. Who notices? What is different on an ordinary Tuesday?
3. Choose, and stop something. Strategy is choice. Michael Porter wrote that the essence of strategy is choosing what not to do. Name at least one activity, request type or project the team will stop or decline because of the vision. A vision with nothing on the stop list has not yet been tested against reality.
4. Check it upward and sideways. Show the draft to your manager and to the leads of the teams you depend on. A team vision should make their work easier to predict, not surprise them.

A short way to write the result is one sentence for the end state, one for the choices and one for the stop. For a support team: "By the end of next year, a customer gets a complete answer from the first person who reads their message. To get there we will cut handoffs and write down the answers to our most common questions, and we will stop adding new contact channels this year." If the decision about what to stop is hard, our guide to decision making in leadership shows how to sort it by stakes and reversibility.

A vision written alone and announced in a meeting tends to stay on the slide. A vision the team helped picture is one people can explain, and explaining it is the real test. Involvement also matters for motivation: Gallup reports that employees whose managers involve them in goal setting are 3.6 times as likely as other employees to be engaged.

Knowing that imagery works is not enough to produce it. Carton and Lucas found that simply telling leaders to use visual words did not make their visions vivid. What helped was a technique Carton calls mental time travel: stepping into the future in your imagination and describing what you see. The five steps in the figure below build that exercise into a 90-minute session.

1. Share the strategy (10 minutes). Present the two or three company priorities you identified, in plain words, and what you know and do not know.
2. Travel forward (20 minutes). Ask each person to write, alone, a description of an ordinary working day two years from now when the team has succeeded. Prompt with concrete questions: "Who is happier, and what are they doing? What no longer happens? What would a customer, a colleague in another team or a new hire notice?"
3. Find the common picture (25 minutes). Read the descriptions aloud. Underline the images that appear more than once. Those shared images are the raw material of the vision.
4. Draft and choose (25 minutes). Write one or two sentences from the shared images. Then agree on two or three choices and one stop. Keep the values to those the team actually argued for.
5. Agree how to check it (10 minutes). Decide how you will know in three months whether the vision is guiding work (see the checks below), and when you will revisit it.

Write the vision yourself after the session if needed, but keep the team's images. People recognize their own words, and the recognition is what makes them repeat it.

A new vision usually asks people to change something they value. Resistance often comes less from the goal than from the fear of losing what makes the team the team. Research by Venus, Stam and van Knippenberg found that leaders can reduce that resistance by assuring people that the essence of the group's identity will remain unchanged, so the vision of change is also a vision of continuity.

In practice, say explicitly what will not change: "We will still be the team that owns the customer until the problem is solved. What changes is how we get there." Then name what people can keep: their expertise, their relationships, the standards they are proud of. Our guide on how to lead change covers the rest of the change process, from building a case to sustaining new habits.

A vision is remembered through use. Posters and screensavers rarely change what people do; decisions do. Three habits keep a vision alive:

• Link every significant decision to it. When you approve, decline or reprioritize something, say which part of the vision it serves: "We're saying no to the new chat channel because it adds a handoff, and our vision is fewer handoffs."
• Tell progress stories in its language. In team meetings, share a short, concrete example of the vision happening: a customer who got a complete answer the first time, a handoff that disappeared.
• Make the goals point back to it. Each quarterly objective should name the part of the vision it moves. If a goal cannot be linked, question the goal. If your team works to OKRs, the objective is the natural place for that link.

Repetition feels excessive to the person who wrote the vision long before anyone else heard it. Expect to repeat it far more often than feels necessary, in different words and examples, until people start using it without you. Clear, regular communication is the base of all of this; how to improve team communication covers the habits that make the message land.

A vision works if it changes what people do when you are not in the room. Three checks, once a quarter:

1. The explain-back test. Ask three people at random, one at a time: "Where is our team going, and what does that mean for your work this month?" If the answers describe the same picture in different words, the vision has landed. If they repeat the slogan word for word, or describe different pictures, it has not.
2. The decision test. Review five recent decisions. Could you point to the part of the vision each one served? Count how many requests the team declined because of the stop list.
3. The pulse question. Add one item to your regular survey: "I know where our team is heading and how my work contributes." Track the share who strongly agree, by team, quarter over quarter.

When the checks disagree with your sense of how things are going, trust the checks. Revise the vision when the strategy changes, when the team has achieved most of it, or when the explain-back test fails twice in a row.

The examples use the support-team vision from this guide; swap in your own picture.

• Introducing it: "Here's the picture we agreed on. Two years from now, a customer gets a complete answer from the first person who reads their message. That means we'll focus on fewer handoffs and written answers, and we'll stop opening new channels. Tell me what's unclear."
• Linking a decision: "I'm saying yes to the knowledge-base project because it gets us closer to first-time answers. I'm saying no to the chat pilot because it adds a handoff, and our picture has fewer of them."
• When someone asks why it matters: "Because today customers repeat their story to two or three people, and in our picture they don't. For you, it means fewer escalations landing on your queue."
• Saying what stays: "We'll still be the team that owns a customer until the problem is solved. What changes is how we hand work over, and how much of it we write down."
• Revising it: "The company moved its priorities this spring, so part of our picture no longer fits. Let's keep the first-time answer and redraw the part about channels together."

• Writing values instead of a picture. "Integrity, excellence, teamwork" tells people how to behave, not where they are going.
• Copying the company vision. Repeating the corporate statement adds nothing; translate it into what this team will see and do.
• No stop list. If nothing gets dropped, the vision is a wish added to existing work.
• Announcing instead of building. A finished vision presented on a slide skips the step where people make it their own.
• Measuring the slogan. Being able to recite the vision is not the goal; being able to explain what it means for one's own work is.
• Never revisiting it. A vision that outlived its strategy becomes background noise and weakens the next one.

Software cannot create a vision or make anyone care about it. It can make the vision visible in daily work. OKR tools connect quarterly objectives to the vision and show each person how their goals contribute. Internal communications tools keep the vision, the decisions it led to and progress updates in one searchable place, so people who join later can read the reasoning. Survey tools run the pulse question and show by team where the vision is clear and where it has not landed.

Treat the software as the record and the reminder. The picture, the choices and the conversation that make people believe it remain the manager's job. If the gap between the vision and the team's behavior is about motivation rather than clarity, how to motivate employees covers what to do next.