Say It Again
Updated: 23 hours ago
Hearing a vision is not the same as having a vision you can use.

As the prototype team, we heard the vision once. It was explained, then filed away. Never posted. Never restated.
And that's the problem with a vision that's only announced. People shouldn't have to rely on their memory of a meeting to know how they're expected to work. A vision needs to be something they can see, hear, and act on every day.
Declan* had heard the vision too. That’s the part I didn’t say clearly in my Seeing the Gap post. Declan, our grade-level learning support teacher, understood what was being asked of him, but kept working the way he always had. He pulled a handful of “his” students out each day, one-on-one, into “his” quiet space. By pulling them out of the community, he was undermining the model. Teachers on our team kept saying so, but nobody with the authority to address it did. It wasn’t malice; hard conversations are easy to put off. So things were left alone, unspoken, until it became too difficult for us to operate as a community.
Outside leadership stepped in just before Declan walked into that math class in “Seeing the Gap,” the moment that cracked something open in him. He saw that he wasn’t the only adult who could reach a student.
But if someone had reinforced the model earlier, or if we’d posted the vision in our learning spaces, things could have been different from the beginning. Declan would have seen Isla* moving and grooving with other learners long before that day. Our team, our students, and Declan would have saved so much time and stress.
Said Once Isn’t Enough
Looking back, the problem wasn't simply that Declan hadn't changed his practice. It was that we'd treated the vision as something communicated rather than something continually reinforced.
A vision isn't something people should have to remember from a meeting. It's something they should be able to see, hear, and act on every day. Said once, it’s an announcement.
So what does that actually take? To work, it has to be three things: defined, visible, and repeated.
Defined. A vision that is not specific feels more like a proclamation or wishful thinking. Define the parameters of the vision. Ours took shape as four lines that were easily understood by everyone and easily said in one breath:
In our learning community:
We co-plan, co-teach, and co-assess.
We share the students.
We are responsible for all of them.
We don’t carry the work alone.
A newcomer could act on that vision on the first day of school. What they can’t act on is a vision statement like: “a culture of collaboration.”
Visible. A vision typed up in a Google Doc somewhere isn’t a lived vision. Write it down. Post it where people will see it. Share it with everyone who works with your students, including specialists, assistants, and new hires… that’s visibility. And that visibility invites accountability.
Repeated. You can’t just say it once; any parent or teacher knows this. But for some reason, we expect teachers to need it only once. Said more than once, by more than one voice, especially leaders, it creates a ripple effect of expectation. People need to hear the vision when it’s inconvenient, not just at the launch.
What I Wish Someone Had Asked
Early on, I wish a leader had made time to check in with everyone on the team, especially Declan. Not to reprimand, but to make sure the vision was understood, the commitment was there, and the support was available.
Three questions would have been a good place to start:
Do you understand what we’re asking of you?
Are you willing to do it?
If yes, what help can we offer you?
Then I would have appreciated the check-in later. Again, not just with Declan, but with all of us. Asking, “Do you understand what we’re asking of you?” again and again throughout the year means that when we start to fall back on old ways of solo teaching, the north star of community can be realigned to the school’s vision and expectations.
If the answer to, “Are you willing to do it?” is no, that’s an honest conversation, and having it early is kinder than having it late. If behaviors change, or silo behaviors resurface throughout the year, ask the same questions again. Sometimes it’s overwhelm, which needs support. Sometimes it’s a change of heart, which needs an honest conversation.
These questions don’t accuse. They ask. They invite conversation and create opportunities for support.
If you’re the team lead and a “Declan” appears on your team, start by coaching. This may include modeling as a resource or a refresher “boot camp” like I shared last week. When you’ve done all that you can and your “Declan” doesn’t move, take it to leadership. At that point it’s no longer a team problem. It’s a personnel one, and it needs someone with the authority to step in.
Where This Sits in the Knoster Model
In the Lippitt-Knoster model (which I wrote about in The 8 Principles post), vision is the first element. When vision is missing or unclear, you get confusion.
The same is true when a vision exists but isn't defined, visible, or repeated enough for people to act on it. Having a vision isn't the same as having a shared understanding of what that vision looks like in practice.
And when expectations aren't clear and reinforced, a teammate's inability to work as a member of the community becomes more understandable. That doesn't mean the behaviour should go unaddressed. It means we need to look at the conditions that allowed it to continue.
For Administrators
Your school’s vision (probably) already says what you mean. Translate it into verbs. Then, post it. Then say it again, as often as possible. I do it at the end of the videos I post by saying, “We were never meant to do this alone.” Find a mantra that articulates your vision succinctly, and then profess it. And if/when someone’s practice drifts, a small, early, kind conversation is much easier on everyone than a late, hard one. Ask the three questions above.
Try This
You don’t need the whole team to start. Pick the level that fits your capacity right now and try one of these learning community shifts this week.
Solo Actions: Say It in Verbs. Write your team’s vision as three things someone could watch you do on Monday morning. If you can’t write it… you’ve found your gap.
Pair Actions: Say It Back. Ask a colleague to explain your team’s vision in their own words, then compare. Where it differs is where it needs defining.
Team Actions: Say It Twice. Post the vision where everyone sees it, and restate it out loud during your next meetings. Ask leadership to do the same.

The goal isn't simply to make sure people have heard the vision. It's to make sure they can live it.
Say it once, and it’s an announcement. Say it again, and it becomes the way you work.

* Names have been changed, and characters are composites, to protect anonymity.
Note: This post was edited with AI as an assistant to refine structure and readability. My ideas, voice, and words remain intact.



Comments