There is a conversation that happens in almost every scaling organisation, and it usually happens after something has gone sideways. The founder is frustrated. “I told them this three weeks ago,” she says. “We discussed it at the offsite. Everyone was in the room.”
They were. The message was delivered. And yet three weeks later the product team is building for one customer segment, sales is targeting another, and the operations lead is making capacity calls on a strategy that shifted six weeks ago. Nobody flagged it. Nobody asked. Everyone assumed that because the conversation had happened, alignment had happened too. It had not. The distance between those two things, the moment a leader speaks and the moment an organisation actually understands, is what I call the context gap. It rarely shows up on a balance sheet. It shows up in meetings that rehash decisions already made, and in teams working hard, in different directions, with total sincerity.
The structure of the problem
The context gap is structural. When a leader makes a strategic decision she has usually been turning it over for weeks, running the scenarios, sitting with the discomfort, processing the implications, so by the time she says it out loud the reasoning feels obvious, because she has already done all the work. What she shares is a conclusion. What her team needed was the reasoning that got her there. “We’re shifting focus to SMB” lands differently once you know why the enterprise pipeline stalled, what the unit economics look like at smaller deal sizes, and what success looks like in six months. Without that scaffolding the same sentence produces six readings across six functions, all of them sincere, none of them triangulated. Meetings do not fix it, because meetings are built for decisions and not for the distribution of understanding; the update gets heard, noted, and buried under the fifteen other things on people’s plates. Nobody knows they misheard, so nobody asks, and the gap compounds until it surfaces downstream as something more expensive.
Why this is the Chief of Staff’s job
This is the operating system’s fault, and the Chief of Staff, more than anyone, is placed to fix it by building a deliberate, repeatable practice of context auditing: checking whether what the leader meant to communicate has actually travelled through the organisation in a way people can act on. The leader is the source and the organisation is the network; the Chief of Staff is the signal check, making sure what left the source is what the network received. A January 2026 Leadership IQ survey of 1,204 employees found the gap between how leaders rate their own behaviour and how their reports describe it is the single strongest predictor of disengagement, ahead of pay, workload, or where people sit.1 It is some of the highest-leverage work a Chief of Staff does, and while nobody hands out awards for it, it decides whether a company runs as one coherent system or a set of departments each operating on its own version of reality.
The three-question context audit
After any significant decision, pivot, or priority change, run three questions before the next milestone:
- What did they mean to say? Go back to the leader, not to recap but to hear it fresh. Thirty minutes, no agenda: if you were telling someone who joined tomorrow, what would you say, and what are the two or three things you most need people to understand? Listen for what she leaves out the first time and includes the second. That gap is where the real context lives.
- What did the team receive? Walk the floor as a curious colleague, not an auditor. Ask what people are working toward and what the top priorities are this quarter. You are listening for the version of reality actually running in the building, and where it diverges from what the leader intended.
- What needs to be bridged? Now you have the gap. Close it with something brief and plain, two paragraphs or three bullets, naming what the decision means, why it was made, and what it asks of people. Send it through whatever channel reaches the team. Follow up once. Then follow up again.
What to do this week
Pick one strategic decision or priority shift from the past three weeks that never had a formal follow-up. Find three people outside the leadership team who should understand it, and ask each of them, separately and casually, what they think the current priorities are. Compare their answers to what the leader intended. The distance you find is your brief for the next fortnight. You do not need a new process. You need a habit of checking.
Context does not distribute itself. It sits in the minds of the people who made the decision, growing richer by the week, while everyone else moves on an earlier, thinner picture. Teams are busy, not careless; leaders are fast, not secretive. The misalignment just arrives wearing the costume of execution problems, friction between functions, decisions that get relitigated, a low hum that everyone is working hard and not quite toward the same thing. The Chief of Staff who builds a steady practice around this never gets the credit for preventing it, and that is fine. The company simply runs better. Decisions stay decided. The leader trusts the team a little more, and the team trusts the leader a little more, and that trust is built in the gap, in the unshowy work of making sure that what was said and what was understood are the same thing.
Sources:- Leadership IQ, survey of 1,204 employees, January 2026[↩]
