You can usually tell whether a vision has landed by asking the wrong person. Not the executive who wrote it, ask the team lead two or three rungs below them what the company is trying to become, and listen for whether the answer is confident, specific, and roughly the same as the one at the top. Most of the time it isn't. The picture was painted clearly enough in the boardroom; it just never made it down the corridor.

The quick version

  • Articulating a vision is putting into words a vivid, durable picture of where you're going and why it matters, clear enough that someone can repeat it without the slide deck in front of them.
  • Cascading is the harder half: getting that picture to travel down and across the organisation so a frontline team's daily choices line up with it, not just the words, but the meaning.
  • The most common failure isn't a bad vision; it's a good one that's badly under-communicated. The research on strategic alignment shows understanding falls off a cliff just below the top team.
  • The fix is repetition and translation, not a launch. Say it far more often than feels necessary, and help each layer answer "so what does this mean for my work?"

The idea in depth: a good vision has two halves

Start with what you're actually articulating, because "vision" gets used loosely. The most durable framing comes from James Collins and Jerry Porras in "Building Your Company's Vision" (Harvard Business Review, 1996). They split a well-formed vision into two parts: a core ideology, the values and the reason the organisation exists, which barely changes, and an envisioned future, the ambitious thing you're trying to become, which they made vivid with the idea of a BHAG (a Big, Hairy, Audacious Goal) and a "vivid description" of what reaching it looks like.

So write both halves, and stop pretending they're the same sentence. The "why we exist" part anchors people when the plan changes; the "where we're going" part tells them what winning looks like. A vision that's all purpose floats; one that's all target feels arbitrary. When you can say why this matters and what specifically we're chasing in two breaths, you've got something a person can carry. The honest limitation: Collins and Porras built this from studying companies that were already successful, so there's a survivorship question baked in, it describes what enduring companies had, not a proven recipe that produces them. Use it as a structure for clear thinking, not a guarantee.

Why "start with why" beats "start with what"

How you order the articulation matters as much as its content. Simon Sinek's well-travelled framing, the "golden circle" from his 2009 talk "How Great Leaders Inspire Action" and the book Start With Why, argues that the leaders who move people open with why they do what they do, then how, then what, rather than the reverse. It's a communication ordering more than a tested theory, and it's fair to treat it as a memorable heuristic rather than peer-reviewed evidence, but the underlying instinct lines up with the Collins–Porras point: purpose first, specifics second.

The practical test is to audit your own vision statement for what it leads with. If the first thing out of your mouth is the target, "we'll hit X by Y", try leading instead with the reason that target is worth anyone's Monday. People rarely rally to a number; they rally to what the number is for. The same goal lands differently when "why" carries it.

People rarely rally to a number. They rally to what the number is for.

The cascade problem: where the picture goes to die

Here's the part most leaders underestimate. You can write a genuinely good vision and still watch it evaporate, because communicating it once, or even a dozen times, isn't nearly enough. John Kotter, in "Leading Change: Why Transformation Efforts Fail" (Harvard Business Review, 1995) and the book that followed, named this directly: leaders routinely under-communicate the vision by a factor of ten (or a hundred, or a thousand). They hold one all-hands, send one email, give a few speeches, and assume the message is now common knowledge. It isn't. He estimated that vision typically captures a fraction of a percent of the total communication an organisation produces in a year, then leaders wonder why hearts and minds never followed.

The evidence for the gap is sobering. In "No One Knows Your Strategy, Not Even Your Top Leaders" (MIT Sloan Management Review, 2018), Donald Sull, Charles Sull and James Yoder surveyed managers across more than 120 organisations and found that, on average, only 28% of executives and middle managers could list three of their company's five strategic priorities. Worse for anyone thinking about cascade: among top teams, 51% could name three priorities, but among their direct reports, that fell to 22%. The sharpest drop wasn't gradual down the hierarchy; it happened in a single step, from the C-suite to the layer just below. The picture isn't slowly fading as it travels, it's falling through the first floorboard.

flowchart TD
  A(["Top team
51% can name 3 priorities"]) -->|"the cliff edge"| B(["Their direct reports
22% can name 3"])
  B --> C(["Middle managers
~28% across the org"])
  C --> D(["Frontline teams
often the vision in name only"])
Where alignment collapses, the steepest fall is the first handoff, top team to their reports (figures: Sull, Sull & Yoder, MIT SMR 2018). Leaders Loop

Treat cascade as translation, then, not relay. A relay just passes the same words along; a cascade asks each leader to restate the vision in terms of their own team's work before passing it down. The question that has to get answered at every layer is "so what does this mean for what we do?", and the only people who can answer it credibly are that team's own managers, which is exactly why leading through other leaders is the skill cascade depends on. Your job up top is to repeat the vision far past the point of boredom; your managers' job is to convert it into priorities their people recognise as their own.

An honest limitation. Repetition can curdle into slogan. Say the same words often enough without ever connecting them to a real decision and you breed the eye-roll, the poster nobody believes. Frequency is necessary but not sufficient; the vision also has to visibly drive what gets funded, hired, promoted and killed. If people see it contradicted by where the money and attention actually go, more communication just advertises the gap. Cascade works when the words and the decisions tell the same story.

A worked example

Take a mid-sized logistics firm, call it Meridian. (Illustrative throughout; this is a teaching example, not a real company.) The leadership team spends a quarter crafting a vision: "To be the most trusted same-day delivery partner in the region by 2029." They launch it at a conference, put it on the wall, and move on. Six months later, a depot supervisor asked what the company is aiming for shrugs: "More deliveries, faster, I think?"

The articulation wasn't bad, but it was a target with no why attached, and it was communicated as an event rather than a habit. The relaunch fixes both. First, they rebuild the statement Collins–Porras style: the core purpose ("we get people the things they're waiting on, when it matters") sits in front of the BHAG, so the number has a reason. Then they tackle the cascade. Instead of one all-hands, every people-leader runs the translation themselves: the depot supervisor's version becomes "trusted means zero missed promises on my shift," with a weekly count of on-time promises kept; the regional manager's is about which depots to invest in to hit that. Same vision, honest translations, repeated in huddles for months rather than announced once.

flowchart LR
  V(["Vision: most trusted
same-day partner by 2029"]) --> P(["Purpose first:
'things you're waiting on,
when it matters'"])
  P --> R(["Regional mgr:
which depots to invest in"])
  R --> S(["Depot supervisor:
'zero missed promises
on my shift'"])
  S --> M(["Frontline metric:
on-time promises kept,
counted weekly"])
One vision, translated layer by layer until it becomes a number a frontline team owns. Leaders Loop

The test isn't whether the slide looks good. It's whether the supervisor, asked again a quarter later, can say what the company is becoming and what their shift has to do with it, in their own words. When that's true, the vision has stopped being a statement and started being a steering wheel.

Frequently asked questions

What's the difference between a vision, a mission and values?

In the Collins–Porras framing the lines blur usefully: values and core purpose ("why we exist") together form the enduring core ideology, while the vision proper is the envisioned future, the ambitious, time-bound thing you're chasing. Mission is often used for either, so don't get trapped in vocabulary. What matters is that you've articulated both an unchanging "why" and a vivid "where we're going," whatever you label them.

How often should I actually communicate the vision?

Far more than feels comfortable. Kotter's point is that leaders under-communicate by a factor of ten or more, so the safe assumption is that the moment you're sick of saying it is roughly when people are first hearing it. Build it into recurring forums, team meetings, reviews, decisions you can explicitly tie back to it, rather than treating it as a one-off launch. Frequency plus connection to real decisions is what makes it stick.

My team is small. Do I really need a formal vision?

You need the clarity, not the ceremony. A five-person team doesn't need a laminated statement, but it does need everyone able to say what "good" looks like a year out and why it matters, otherwise people optimise for different things. Articulate it plainly, even verbally; the cascade problem is smaller in a small team, but the articulation problem is the same.

How do I stop the vision sounding like empty corporate slogans?

Tie it to a decision people can see. The cynicism comes from words that never touch reality, a "customer-first" vision in a company that visibly chases short-term margin. Make the vision earn its keep by pointing to something you funded, hired for, or said no to because of it. A vision that explains a real trade-off is believable; one that explains nothing is wallpaper.

Whose job is it to cascade, mine, or my managers'?

Both, in different modes. You own articulating it clearly and repeating it relentlessly; your managers own translating it into what their specific team does. Cascade fails when leaders treat it as a relay, passing identical words downward, instead of asking each layer to restate the vision in their own team's terms. That translation work is a core part of day-to-day people management, not a once-a-year offsite.

Related in the Toolkit

Articulating a vision is one thing your leadership style shapes, a transformational leader sells a future, an adaptive one frames a hard problem, and cascading it well is largely about leading through other leaders rather than broadcasting from the top.

Where to go next