Why Your Team Needs to Hear the Vision More Than You Think

One line from Traction has stuck with me more than almost any other.

"People need to hear the vision seven times before they really hear it for the first time." — Gino Wickman

When I first read that, I thought it was a little generous. Seven times?

But after years of sitting in sessions with leadership teams and watching rollouts stall and restart, I stopped being surprised by it. I started expecting it.

The Communication Mistake Most Leaders Make

The leaders who struggle most with rollout are usually the ones who said it once, clearly and confidently, and then wondered why nothing changed. They communicated. They checked the box. And then they moved on.

It makes sense on the surface. If you said it well and people were in the room, they heard it. Right?

Not exactly. Hearing something in a meeting and actually internalizing it are two completely different things. People are distracted, skeptical, or just not ready to receive it the first time. Or the second. Sometimes even the fifth. The vision you've been living with for months is brand new information to most of your team, and new information takes repetition to become belief.

This is one of the most common reasons rollouts lose momentum. Leadership communicates the vision once, maybe twice, and then assumes the team is aligned. Meanwhile, the team is still processing, still skeptical, still waiting to see whether this is real or just another initiative that will fade in a few months.

Repetition Is a Discipline, Not a Weakness

There's a version of leadership that equates repeating yourself with a lack of confidence. If you said it clearly, people should have it. Moving on signals strength.

In practice, the opposite is true. The leaders who are most effective at rollout are the ones who understand that repetition is not a failure of communication. It's the strategy.

You repeat the vision at every All-Hands. You tie it into weekly meetings. You reference it when you make decisions. You find ways to make it show up in the day-to-day so it stops feeling like a presentation and starts feeling like reality. You connect it to what the team is working on right now, so it doesn't live in the abstract but in the actual work.

Every time you bring the vision back into the room, you are reinforcing that it's real, that it matters, and that the organization is genuinely moving toward it. That reinforcement is what turns a vision statement into a shared belief.

What This Looks Like in Practice

If you are running on EOS, you already have built-in opportunities to do this. The V/TO is not a document you create once and file away. It's a living reference that should be visible, discussed, and connected to decisions on a regular basis.

Your quarterly All-Hands is one place to do it. Your Level 10 Meetings are another. Even casual conversations where a leader connects a daily decision back to the company's long-term direction count. None of those moments feel dramatic. But they add up, and over time they are what make the vision feel real to the people who didn't build it.

Seven times is not an exaggeration. For some teams, it's a starting point.

If you're navigating a rollout and want support getting your team to actually hear it, visit bethfahey.com to learn more about working together.