The Meeting That Should Have Gone Differently
There is a particular kind of meeting that most leaders recognise. Everyone is there. The agenda is clear. The people around the table are talented, experienced, and genuinely committed to the organisation’s success. And yet something is missing. The conversation stays on the surface. Decisions get made without the challenge they deserve because debate gives way to consensus. The most important questions – the ones that would require someone to name an uncomfortable truth – don’t get asked. And by the end, everyone leaves with a list of action items and a lingering, unspoken awareness that something real just didn’t happen.
This is not a talent problem. It is not a motivation problem. It is a fear problem.
And the reason most leaders don’t name it as such is that fear in high-performing teams looks almost nothing like the word suggests.
The Most Expensive Problem Isn’t on Any Dashboard
The most expensive performance problem in your organisation isn’t on any dashboard. It’s the idea that went unspoken in yesterday’s meeting – and the one that won’t be raised tomorrow either.
Think about what that actually means. The insight that would have reframed the strategy. The concern that would have caught the risk before it became a crisis. The challenge that would have made the decision sharper, the plan stronger, the outcome better. None of it missing because the people in the room lacked the intelligence or the commitment to surface it. All of it missing because the environment – in ways nobody designed and nobody explicitly chose – made saying it feel like a risk not worth taking.
This is the hidden architecture of underperformance. Not capability gaps. Not disengagement. Not poor process. A culture in which the cost of honesty, however subtle and unspoken, is experienced as higher than the cost of silence.
What Fear Actually Looks Like in High-Performing Teams
Fear in organisational life is rarely dramatic. It does not announce itself. It is not the paralysis of someone who cannot function; it is the subtle, sophisticated self-management of someone who has learned, through accumulated experience, that speaking honestly in this environment carries a cost. It hides behind language that sounds entirely reasonable: accountability, urgency, performance pressure, getting back to basics. And it shows up not as avoidance but as a certain kind of precision – saying exactly enough, and not one word more than is safe.
And it operates through three specific patterns I have seen in organisations across every sector and scale.
The first is habitual thinking. When the environment feels unsafe, people fall back on what they know. Familiar mental models. Tried approaches. The default way this team has always handled this kind of challenge. This is not laziness or conservatism – it is a survival response. In uncertain environments, the known path feels safer than the experimental one. But in a world defined by rapid change, defaulting to what has always worked is exactly how capable teams become irrelevant. Habitual thinking is fear wearing the costume of experience.
The second is siloing. When trust between functions is fragile, people protect what they control. Information that might be useful to another team stays in the department where it was generated. Concerns about a cross-functional project get raised in the wrong room – or not at all. Interdependencies that should be managed through honest dialogue get managed through formal processes and escalation chains. Siloing is not primarily an organisational design problem. It is a relational one. It is what happens when the cost of genuine collaboration – the vulnerability it requires, the conflict it potentially surfaces – feels too high and too risky.
The third is control-seeking. When leaders feel anxious about outcomes, they tighten. More oversight. More reporting. More approval steps. More metrics. These responses feel productive because they are visible and they create the comforting sensation of grip. But what they actually do is communicate, loudly and unmistakably, that mistakes are not welcome here. And when mistakes are not welcome, neither is the experimentation, the candour, or the genuine learning that would actually improve performance. Control-seeking is fear masquerading as discipline.
Underperformance and Fear: Learning to Tell Them Apart
This is the distinction that matters most, and the one most leaders are never given language to make: the difference between a team that is underperforming and a team that is afraid.
An underperforming team lacks capability, clarity, or resources. The solution is skill-building, goal-setting, or resourcing. These are knowable problems with identifiable fixes.
An afraid team is something else entirely. The capability is present. The clarity may even be there. But the conditions in which that capability is deployed have made honest contribution feel dangerous. And so talent is directed not toward the problem in front of the team, but toward managing the professional and social risk of being in the room.
The signs are specific, once you know how to read them. Contributions that are heavily qualified before they are made. Agreement that comes too easily and too early. Questions that are asked as statements, so they carry less exposure if they land badly. Post-meeting conversations that are more honest than the meeting itself. A consistent pattern of the same voices speaking, and the same voices staying quiet.
These are not performance failures. They are fear signals. And when leaders treat them as performance failures – responding with more oversight, more process, more pressure – they intensify the very conditions that produced the signals in the first place.
The diagnostic question is worth sitting with deliberately: when performance stalls in your team, do you reach first for a capability explanation or a cultural one? Because if the answer is almost always capability, you may be solving for the wrong thing.
The Self-Reinforcing Loop – and How to Break It
None of the three patterns above – habitual thinking, siloing, control-seeking – are conscious choices. They are survival responses. And they are self-reinforcing. Fear produces these behaviours, these behaviours deepen the conditions that produce fear, which intensifies the patterns further. Without intervention, the loop runs itself – persistently and unobtrusively, and at considerable cost to performance.
The intervention begins with something deceptively simple: naming what is happening.
Fear loses much of its power when it is made discussable. When a leader can say “I notice we are playing it very safe in this conversation; what would we say if we were being fully honest?” or “I’m aware there is something we are not quite getting to – can we name it?”, they change the permission structure of the room. Not by eliminating fear, but by making its presence part of the conversation rather than the invisible force shaping it from below.
This is precisely what Adaptive Safety provides: the shared capability to create conditions in which fear can be named, examined, and transformed from a constraint into a signal. Because when a team learns to notice fear – to see it in the micro-moments of daily interaction rather than waiting for it to produce a visible crisis – it gains access to some of the most important information available about the health of its culture.
Fear Named Is Data. Fear Unnamed Is Destiny.
The question worth sitting with is this: in the last week of your work, how many of the most important things that needed to be said were not said? Not because people didn’t know them. But because the environment, in ways that nobody designed and nobody explicitly chose, made saying them feel like a risk not worth taking.
That is where the work begins. Not with a new process or a new initiative. With the courage to see, and then name, what is already there.
Next week, we will turn to the specific, observable moments that either build or undermine safety – what I call micro-behaviours. And why a leader’s ability to notice these moments, and deliberately reinforce or challenge them, is central to creating Adaptive Safety and building teams that perform under pressure.
From Fear to Flow: The Adaptive Safety Revolution by Errol Amerasekera is available now wherever books are sold. Each blog in this series draws on research and frameworks from the book – which goes substantially deeper on every concept introduced here.