The Year-End Question Most Leadership Teams Skip

Year-end reviews usually start with performance.

What did we accomplish? What did we miss? What did we learn? What should we do differently next year?

All useful questions. They're also questions about the work. There's another question underneath them, about the room the work happens in.

What did we learn not to say this year?

Every team learns this

No one writes these rules down. Teams learn them from experience.

They learn from what happened the last time someone disagreed in a meeting. From which concerns changed the plan and which ones were thanked and ignored. From whether a problem raised late was treated as useful information or as a failure of loyalty. From the conversation that happened after the meeting, because the real one couldn't happen in it.

By December, every room has a memory.

Research backs this up. James Detert and Amy Edmondson studied what they called implicit voice theories: taken-for-granted beliefs about when speaking up at work is risky or inappropriate. They found these beliefs led people to hold back even suggestions meant to help the organization, that they were widely held, and that they explained silence at work beyond the factors researchers already knew about.¹

Leaders rarely set out to teach these rules. Usually they're learned from small moments the leader didn't notice.

Signs your team has learned not to say something

Some silence is obvious. Most isn't. Watch for:

• The smooth room. Meetings end on time. No friction. No dissent. Sometimes that's a healthy team that has done the hard work. Sometimes it's a team that has learned agreement is safer than inspection. The surface looks identical.
• The meeting after the meeting. Decisions get relitigated in hallways and side chats, because the real objections didn't come up in the room.
• Polished problems. Issues arrive only once someone already has a solution, or not at all.
• Late surprises. Risks that "everyone knew about" show up only when it's too late to change course.

One test I use with smooth rooms: when was the last time someone said something that surprised you? If you can't remember, that's worth sitting with.

How to ask the question so you get honest answers

Asking "What did we learn not to say?" in a room that has learned not to say things takes care. A few practices help.

Go first. The leader names something they may have taught the room, without explaining it away. I think I've made it hard to raise concerns once I've shared my view. That one sentence does more than any promise of safety.

Ask about the room, not individuals. "What have we learned is risky to bring up here?" is easier to answer than "What haven't you told me?"

Give people a way in before the meeting. Short, anonymous prework lets people name patterns they won't name out loud the first time.

Listen without defending. Every explanation, even an accurate one, teaches the room the same lesson again.

Act on one answer, visibly. Don't promise to fix everything. Pick one thing the team named, change it, and say that you're changing it because of this conversation. That's how a team learns the question was real.

Bring it into your planning offsite

If your leadership team is meeting to plan next year, put this question on the agenda before the goals. Teams don't execute goals in the abstract. They execute them inside rooms with habits, histories, and permissions. Knowing what your room won't say is part of knowing what it can actually do.

It's also a natural opening for a speaker. A session on reading the room, early in the agenda, gives the team shared language for the harder conversations that follow.

Planning a leadership offsite? See how Jeremiah works with leadership offsites. The Read™ helps teams see what's really happening in the room before they decide what to do about it. Book a discovery call.

Go deeper: What Is Diagnostic Leadership?

Notes

1. James R. Detert and Amy C. Edmondson, "Implicit Voice Theories: Taken-for-Granted Rules of Self-Censorship at Work," Academy of Management Journal 54, no. 3 (2011): 461–88, https://doi.org/10.5465/AMJ.2011.61967925.