The Last Question
Why this question works when others don’t
I gave an all-hands once where I thought I crushed it.
The slides were tight. People asked good questions. A few folks even came up after to say it landed. I walked back to my desk feeling sharp, the way you feel when you nail something hard.
A day later, my manager pulled me aside. “Nobody on the floor knows what they’re supposed to do.”
Wait, what?
I had spent forty minutes on that presentation. I had outlined the strategy, walked through the priorities, named the projects. I had done the work. And yet a hundred people walked out of that room, smiled politely on the way out, and went back to their desks with no real idea what was actually being asked of them.
That was the day I started asking the last question.
Does everyone know what we need to do?
That’s it. That’s the whole question.
I ask it before I walk out of any meeting where decisions are made or direction is set. Strategic planning, project kickoffs, after a hard pivot, after a reorg conversation, after anything where the team needs to leave with their feet pointed in a new direction. It is the simplest leadership tool I have.
Now read this slowly, because it took me too long to internalize.
If your team cannot quickly and easily answer that question after you’ve just spent forty minutes communicating with them, you actively made things worse. You stole their time, you stacked confusion on top of whatever they walked in with, and now they’re going to spend the next week guessing instead of executing.
That is a worse outcome than if the meeting had never happened in the first place.
Why this question works when others don’t
“Any questions?” is a useless question.
It tests whether anyone in the room is brave enough to admit confusion in front of their peers. Most people are not. The room goes quiet, you take the silence as understanding, and you walk out feeling effective.
“Does that make sense?” is worse.
It is a verbal tic disguised as a check-in, and most teams trained themselves a long time ago to nod through it. You’re essentially asking people to validate that you communicated well, which is a request they will almost always grant you because the alternative is awkward.
“Does everyone know what we need to do?” cuts a different angle.
It is not asking whether your delivery was clear. It is asking whether the listener can name an action. It puts the burden of proof on comprehension, not on diplomacy. A team can nod through “does that make sense” without breaking eye contact. They cannot nod through “tell me what you’re going to do tomorrow morning.”
When the answers come back fuzzy, you have just learned something extremely valuable for free. You did not actually communicate what you thought you communicated. Better to find that out in the room than two weeks later when the work goes sideways.
Adapting it to the size of the room
In a small group, ask the question directly. Go around the table if you need to. You want short, declarative answers. “I’m going to do X.” “My team is starting Y on Monday.” If anyone hedges or paraphrases the strategy back at you instead of naming an action, you’ve got your answer about whether you landed it.
In a large all-hands or town hall, the direct version does not scale. What I ask instead is a layered version. “If you walk out of here confused about what to do, talk to your manager. If your manager can’t get you clear, they should come to me, and we’ll get it sorted.” That sentence does two things at once. It signals that confusion is allowed and expected, which lowers the social cost of admitting it. It also creates an accountability chain that runs back up to you, which means you actually find out where the message broke down instead of letting it fester.
Either version requires you to be the kind of leader who can hear the answer. If you ask the question and someone tells you the message did not land, you cannot get defensive. You cannot explain why they should have understood you. You take the data, thank them, and reset.
The discipline behind the question
Most leaders do not ask this question because they do not want the answer. I get it. I have been there. You spent the time, you wrote the slides, you rehearsed the talk track, and the last thing you want to hear is that none of it landed.
But twenty-five years of leadership have taught me something I wish I had figured out earlier.
The teams that move fastest are not the ones with the smartest leaders. They are the ones whose leaders are willing to find out, in real time, whether the message landed.
That willingness is the actual job. The presentation was the easy part.
So ask the question. Make it the last thing you do before you leave the room. If the answer is fuzzy, stay another five minutes and clean it up. If the answer is clear, you have just earned yourself a week of execution instead of a week of thrash.
It is the simplest tool I have. It is also the one that has saved me the most times.
Stay courageous,
Josh Anderson
The Leadership Lighthouse
P.S. This came out of the latest episode of The Meta-Cast, where Bob Galen and I dig into manager speak, the buzzword bingo trap, and why softening your message creates the very anxiety you were trying to prevent. If this article resonated, that conversation is worth your time.
P.P.S. What is the question you’ve learned to ask before you walk out of a meeting? The one that has saved you too many times to count? Hit reply and tell me. I read every response.
Interesting article, thanks. During teacher training, I discovered concept-checking questions. You ask people to describe what they have understood, rather than giving them the option to just nod along.