Something about it feels wrong to several of them. Not necessarily wrong enough to oppose it, and perhaps not even clear enough to explain. Four can put some language around their concern. Two decide it is important enough to raise. One actually does.

The concern is discussed. The decision doesn’t change.

A week later, the meeting appears in an update as evidence that the team is aligned.

Nobody lied.

Nobody was necessarily afraid to speak. The meeting may have been well run, the disagreement taken seriously and the eventual decision entirely reasonable. Yet the organisation began with several people experiencing some form of uncertainty and ended with evidence of alignment.

What happened in between is usually treated as a communication problem. I think it is more complicated than that.

David Ogilvy is often credited with the observation that people don’t think what they feel, don’t say what they think, and don’t do what they say. It is a neat description of a familiar human problem, but it also implies a sequence: feel, think, say, do.

Organisations add another stage.

They see.

And then they explain what they saw.

This matters because each transition is not simply the transmission of information. It is an act of interpretation.

A vague feeling has to become a thought before somebody can explain it. A thought has to become language before somebody else can hear it. Language becomes an intention or commitment, which eventually becomes behaviour. Then somebody observes that behaviour and decides what it means.

We behave as though meaning travels through this process intact.

It doesn’t.

The pressure to make things legible

Organisations cannot operate indefinitely in ambiguity. Decisions have to be made, resources allocated, projects approved and risks managed. Senior leaders cannot absorb every conversation, hesitation and half-formed concern occurring across a company.

So information gets compressed.

Usually for perfectly sensible reasons.

Someone notices that a project doesn’t feel quite right but cannot explain why. Their manager asks them to make the concern more specific. The concern becomes an assessment.

The assessment moves upwards and somebody asks what should be done about it. It becomes a recommendation.

The recommendation enters a steering committee and needs a status.

The status enters an executive dashboard and needs a colour.

Uncertainty becomes an assessment.

The assessment becomes a recommendation.

The recommendation becomes a status.

The status becomes green…

Nobody has behaved irrationally. In fact, everybody may have improved the information according to the requirements of their role. The problem is that green can acquire a certainty the original information never contained and, six weeks later, the project turns red and everyone wants to know what changed so quickly.

Perhaps reality didn’t change quickly at all, but perhaps the reporting did.

Every boundary in an organisation is a filter, not a wire. Information is translated as it moves, and hierarchy creates an implicit assumption that uncertainty arriving from below has already been dealt with. If something reaches an executive as a recommendation, it is reasonable to assume somebody has tested the assumptions underneath it.

The person below may have made exactly the same assumption. Eventually leading to everyone finding themselves acting on certainty that nobody actually possessed.

Then the journey reverses

The more interesting problem starts when leaders try to reconstruct what happened upstream from what they can observe downstream.

People attended the training, so they must understand the change.

They followed the new process, so they must support it.

Nobody challenged the decision, so they must agree with it.

The meeting went smoothly, so the team must be aligned.

Behaviour is evidence. So are survey responses, meeting contributions and adoption rates. The mistake is not measuring them. The mistake is assuming they tell us more than they do.

We lose uncertainty moving forward, then manufacture certainty moving backwards.

A person can comply without agreeing. They can agree without understanding. They can intend to change and encounter an environment that makes the new behaviour difficult. They can feel something important without yet knowing what they think about it.

This is why psychological safety only explains part of the problem.

A psychologically safe environment may make it easier for somebody to say what they think. It cannot guarantee that they yet know what they think, that what they say will influence the decision, or that what they intend will survive contact with the system around them.

Information can be present, expressed, heard and still have almost no causal power.

The explanation doesn’t stay at the top

Imagine that leadership introduces a new way of working.

People agree to it, but adoption is inconsistent.

Leadership observes the behaviour and needs an explanation.

“The team is resistant.”

That explanation might be wrong. More importantly, it doesn’t remain an explanation.

It changes what happens next.

Managers are told to drive accountability. One starts checking adoption more closely in team meetings and asking people to explain when they have not followed the new process. An employee who had been uncertain about one part of the change raises the concern again, but this time the question lands differently. What previously sounded like useful hesitation now sounds, in the context of resistance, like another reason not to change.

The manager pushes harder.

The employee learns that continuing to raise the concern is unlikely to change the decision, so stops raising it and does what is required instead. The behaviour becomes more compliant, but the conversation becomes less candid. When problems with the new process continue, they surface later and with less context.

Leadership now sees a team that needs repeated prompting, raises fewer concerns openly and appears reluctant to engage with the change.

More resistance.

The original explanation has acquired new evidence.

This is where the problem stops being a simple failure of communication or measurement. Leadership can eventually help produce the evidence that confirms its original inference.

More data does not necessarily correct the mistake because the system producing the new data has changed. Each new observation is being generated inside an environment already shaped by the previous explanation.

The organisation is no longer merely interpreting reality.

Its interpretation has become part of the conditions producing the reality it will interpret next.

What happens to the things we don’t understand yet?

There is another problem hiding near the beginning of this process….not every vague concern is useful.

People misread situations. We carry biases, anxieties, preferences and self-interest into work. Seven people feeling uneasy about a decision does not make the decision wrong, and an organisation that treats every intuition as meaningful will struggle to make decisions at all.

The difficulty is that we often cannot distinguish useful weak information from noise at the moment it first appears.

Sometimes expertise begins with noticing that something is unusual before knowing why.

This creates an awkward category for organisations:

Something happened.

Someone noticed it.

Nobody knows what it means…yet.

Most management systems are not particularly comfortable with that category.

We ask for the issue, severity, owner, recommendation and action. Even mechanisms intended to surface concerns can demand that the person reporting something classify it before the organisation agrees to retain it.

Some safety-critical environments offer a useful contrast. Near misses and anomalies can be captured before their full significance is understood. The initial task is not necessarily to prove what something means, but to preserve the observation so it can later be compared with other observations, investigated or recognised as part of a pattern.

The distinction is subtle but important.

Capture and classification are not the same thing.

An issue log still forces premature certainty if the price of putting something on it is knowing what category it belongs to, how serious it is and who owns it. Perhaps organisations need somewhere for an observation to exist before somebody has to defend an explanation for it.

Not because every observation deserves action.

Because sometimes meaning only emerges when several apparently insignificant observations begin to cluster.

Why this persists

None of this requires bad leadership, and that may be why it is difficult to correct.

The employee doesn’t want to overstate a vague intuition.

The manager tries to make it actionable.

The director makes it concise.

The executive makes it decisive.

The board needs enough clarity to act.

At every stage, somebody behaves reasonably.

Nobody has much incentive to reopen uncertainty that appears to have been resolved one level below them. The accumulated distortion belongs to nobody, because every individual translation made sense locally. Then the organisation acts on the resulting explanation, changes the environment and begins generating new evidence. Eventually, the explanation starts to look less like an interpretation and more like a fact.

“The team is resistant.”

“The culture isn’t ready.”

“People don’t want the change.”

“We were aligned when we made the decision.”

Perhaps some of those statements are true, but the problem is knowing whether we discovered them or helped create them. Leaders often ask why nobody told them.

Perhaps the more useful question is what the organisation required the information to become before it was willing to hear it.

Definitions, frameworks, models, research summaries, podcasts, newsletters and explainers are everywhere. If I want to understand psychological safety, organisational culture, strength training, artificial intelligence or almost anything else, I can know considerably more about it by lunchtime than I did at breakfast. That is mostly a good thing, but the problem begins when access to knowledge starts to look like evidence of competence.

There is an old distinction in cognitive psychology between declarative and procedural knowledge. Declarative knowledge is knowing what, while procedural knowledge is knowing how. I can understand the principles of negotiation without ever having sat across from somebody who is prepared to walk away, explain how progressive overload works without having coached another human being, or know the accepted principles of leadership without ever having been responsible for a difficult decision when the information is incomplete and somebody is going to be unhappy whatever I choose.

The first kind of knowledge has become almost frictionless, while the second hasn’t. Procedural knowledge still requires doing something, usually repeatedly, with enough feedback, mistakes and adjustment to discover which parts of what you thought you understood survive contact with reality and which don’t.

Somewhere in that process another form of knowledge begins to develop: judgement. It is one thing to know what and another to know how, but experience gradually teaches you when. You begin to recognise when the framework applies and when it doesn’t, when something doesn’t quite fit, when you have enough information to act and when you don’t yet understand the problem well enough to give an answer.

This is why genuine expertise can sometimes sound surprisingly uncertain. The person who has seen something work ten times has probably also seen it fail twice, so they know the exceptions and have encountered the awkward cases that didn’t behave as the model predicted. Over time, they learn which variables matter, which ones sometimes matter, and which ones mostly make for good presentations. Ask someone with enough experience a difficult question and you will often hear some version of, “It depends”, not because they know less, but because they know what the answer depends on.

Yet we have built an information environment that often rewards precisely the opposite. Certainty is easier to distribute than conditionality, and a clear explanation can be compressed into a post, a carousel or a podcast clip in ways that context cannot. “Five things great leaders do” is easy to distribute, while “it depends on the team, the task, the incentives, the history, the environment and what happened last Tuesday” is less cooperative.

So context gets stripped away, leaving behind what is often perfectly accurate declarative knowledge, detached from many of the conditions that determine whether it is useful. The person consuming it can become genuinely more knowledgeable, learning the terminology, understanding the model and becoming capable of explaining the concepts convincingly. They have all the right words but none of the right scars.

This isn’t necessarily dishonesty, because most people aren’t pretending to know things they don’t. The problem is that fluency feels remarkably similar to understanding from the inside and, increasingly, it looks similar from the outside too.

That creates a problem for organisations because a fluent person can perform extremely well while conditions remain familiar. They can reproduce the framework, prepare the strategy, explain the methodology and use all the right language, right up until something happens that isn’t in the model. The market changes, the client behaves strangely, the team doesn’t respond as expected, two apparently sensible principles contradict each other, or the information is incomplete and a decision still has to be made.

This is where the distinction becomes visible, because the framework tells you what normally happens, while experience helps you notice what is happening now.

For a long time, some of the signals we used to identify expertise were reasonably expensive to produce. Being able to synthesise a complex subject, produce a sophisticated analysis or explain an idea clearly usually told us something about the work someone had done to get there. Those signals are becoming cheaper, and AI accelerates that considerably.

It can explain, structure, summarise and synthesise at a level that would have required considerable effort not very long ago. It can produce a plausible strategy, critique an argument, explain a technical concept or generate the language of almost any profession within seconds. Much of this is useful, and I use it constantly, but AI changes the relationship between the appearance of expertise and the experience traditionally required to produce it.

It can give me the vocabulary and the framework, and it can even tell me what an experienced practitioner might consider, but it cannot give me the scars. The judgement that comes from acting, getting something wrong, noticing why, changing course and carrying the consequences still has to be earned.

This may create a strange problem over the next few years, as we become surrounded by increasingly sophisticated outputs while finding it harder to determine who actually knows what they are doing. A polished strategy will tell us less about the strategist, an articulate explanation will tell us less about the speaker, and knowing the literature will tell us less about whether somebody can apply it. The traditional signals of expertise won’t disappear, but their value as evidence may decline.

I’ve noticed this most clearly when interviewing experienced people. Almost everyone at that level can explain what good practice looks like, but the more revealing question is usually much narrower: tell me about a time you did this and it didn’t work. The answer changes because people who have actually been there tend to give you the inconvenient details, what they missed, what surprised them, what they tried first, why it failed and what they would do differently now. The answer becomes less polished and more useful.

Perhaps that is the real infodemic, not too much information, but an abundance of the signals we once used to identify expertise. In a world where almost everyone can sound like they know, knowing who actually does may become one of the most important judgements we make.

It isn’t because the day disappeared into pointless meetings or work that didn’t matter. Usually the opposite. A client needed something. Someone wanted an opinion on a proposal. A meeting ran fifteen minutes over because the conversation was useful. A message came in that was easier to answer immediately than leave sitting there. Then another meeting started, somebody called afterwards, and somewhere between all of that I opened the document I had actually intended to work on that morning.

By late afternoon, I might have touched ten different problems. I’m just not sure I properly thought about any of them.

I used to see days like this mostly as a time-management problem. Perhaps I needed to protect the diary better, decline more meetings or become more disciplined about when I answered messages. There is probably some truth in all three, but I’ve become more interested in something slightly different.

The problem isn’t always that we have too much work. Sometimes it is that we rarely get to finish thinking about one thing before we have to start thinking about another.

Sophie Leroy’s research on what she calls “attention residue” helps explain why this matters. When we move from one task to another, particularly when the first task is unfinished, our attention does not necessarily move cleanly with us. Part of it remains attached to what we have just left.

Anyone who has spent time moving between meetings will recognise the feeling. You are listening to the conversation in front of you while still processing something from the previous one. Perhaps there was a decision you weren’t entirely comfortable with, a question you didn’t answer particularly well, or something somebody said that only started to seem important once the meeting had ended.

You have moved on. Your attention hasn’t, at least not completely.

That would matter in almost any kind of work, but I think it creates a particular problem for leaders because so much of senior work depends less on producing things than on judging them.

A good decision often requires you to sit with ambiguity for longer than is comfortable. You have to notice what doesn’t quite fit, hold competing explanations in your head, question the obvious interpretation and think beyond the immediate consequence. Sometimes the most useful thing you can do is resist answering until you understand the problem well enough to know whether you are even being asked the right question.

Those are difficult things to do in the gaps between meetings.

There is a strange contradiction here. As people become more senior, organisations place greater value on their judgement while simultaneously creating more opportunities to fragment the attention required to exercise it.

More people want access to them. More decisions arrive for approval. More meetings require their presence. Problems move upwards because asking somebody senior is often quicker than resolving uncertainty lower down. Eventually, a significant part of the working day becomes a series of small transitions between other people’s priorities.

The difficulty is that none of this necessarily feels dysfunctional. A day of meetings, messages, approvals and quick decisions produces a lot of visible evidence that something happened. Problems move forward, people get answers and decisions are made. There is a satisfying administrative archaeology at the end of the day showing exactly where the hours went.

Thinking leaves much less evidence. You can spend ninety minutes wrestling with a difficult problem and have very little to show for it. Perhaps you changed your mind, noticed an assumption that everyone else had accepted, or realised that the question you started with wasn’t particularly useful. Reactive work gives us constant signals of contribution. The slower work of judgement can look suspiciously like doing nothing.

Modern work has also made it extraordinarily easy for something else to claim our attention. The problem is that most of those claims are perfectly reasonable.

Reply to the message because somebody is waiting. Join the meeting because your perspective matters. Review the document because a decision needs to be made. Help somebody who is stuck because leaving them stuck for half a day seems absurd.

No single interruption needs to be particularly damaging for the cumulative effect to become expensive.

The obvious response is to protect time. Block two hours for deep work, turn notifications off, create meeting-free mornings, delegate more aggressively, perhaps use AI to summarise the material you didn’t have time to read. All of those can be useful, but they also risk treating an organisational problem as an individual one.

If every meaningful decision eventually travels upwards, the leader’s calendar isn’t the only problem. If people cannot progress without getting an immediate answer from someone senior, turning off notifications does not remove the dependency. And if a team struggles whenever its leader becomes unavailable for a few hours, a protected block of focus time may reveal more about how the organisation has been designed than about the leader’s productivity habits.

Organisations already understand this principle when allocating other scarce resources. Money requires approval, headcount is debated and travel budgets are scrutinised because putting resources in one place means they are unavailable somewhere else. Senior people themselves are often kept away from lower-value activity for exactly the same reason.

Yet access to their attention tends to accumulate with far less scrutiny. A thirty-minute meeting looks like it costs thirty minutes, a two-minute question looks like it costs two minutes, and a message appears to cost roughly as long as it takes to type the reply. Looked at individually, none seems particularly expensive, which is probably why they accumulate so easily.

What that calculation misses is the cognitive tail attached to each one. The previous problem does not necessarily disappear because the next one has arrived, and the next one does not wait politely while we finish thinking about the last.

The real cost is therefore difficult to see. It might be the connection you nearly made before your attention moved elsewhere, the assumption you would have questioned if you had stayed with the problem for another ten minutes, or the decision that was perfectly reasonable given the information available but would have looked different after another half-hour of thought.

Meetings, messages and working hours leave records behind, so we can usually reconstruct where a day went with reasonable accuracy. There is no equivalent record of what somebody might have noticed, questioned or understood if their attention had remained in one place for slightly longer.

That makes fragmentation unusually easy to tolerate because its costs mostly appear as absences.

Perhaps that changes the question. Instead of asking only where our time is going, it may be more useful to ask what has permission to interrupt our thinking, and why.

Because the most expensive part of a fragmented day may not be the hours we lose.

It may be what we almost had time to understand.

A technology, a supplement, a framework or a molecule that promises to make us faster, smarter and more productive than ever before.

Today, in business, it’s AI.

In health, it’s peptides.

At first glance they have almost nothing in common. One promises to change the way we work. The other promises to change the way we recover, age and perform. Yet the conversations around both sound remarkably similar.

“This changes everything.”

“You’ll be left behind if you don’t use it.”

“It’s a force multiplier.”

The interesting thing is that those claims may all be true. They simply leave out the most important sentence.

A force multiplier only multiplies what’s already there.

Spend five minutes on social media and you’d think peptides are responsible for every impressive physique over the age of forty. It’s an attractive story because the intervention is obvious. Years of consistent training, adequate sleep, sensible nutrition and patience aren’t. We have a habit of attributing outcomes to the most visible thing in the room, while quietly overlooking the system that made those outcomes possible in the first place.

That’s why the peptide debate often feels detached from reality. Someone sleeping five hours a night, living on ultra-processed food and never exercising is unlikely to transform their health because they added peptides. The intervention isn’t ineffective. It’s simply arriving in a system that can’t make much use of it. Put the same intervention into a body built on years of good habits and the outcome may look entirely different.

Watching the debate around AI, I’m struck by how quickly it becomes a conversation about the technology itself. Will it replace jobs? Is it overhyped? Which model is best? I find myself wondering whether we’re looking in the wrong place.

AI can only respond to the thinking that produced the question in the first place. If your brief is confused, AI produces beautifully written confusion. If your assumptions are flawed, it explores those flaws at remarkable speed. If your organisation can’t distinguish signal from noise, AI simply creates more noise, faster.

A few weeks ago I sat in a call reviewing an AI-generated strategy paper. The first discussion wasn’t about whether the argument held together. It was whether the executive summary should come first, whether one section flowed better before another and whether a few paragraphs could be tightened. For ten minutes we improved the document without ever asking whether the underlying thinking was sound.

I’ve felt that pull myself. A polished answer invites agreement long before it earns it.

None of that is AI’s fault. It’s simply doing what it was asked to do.

An organisation with capable people, clear judgement and disciplined decision-making will probably get far more from AI than one built on muddled thinking and poor decisions.

The same pattern appears elsewhere. Give great coaches better data and performance often improves. Give poor coaches the same data and they often become more confident in bad decisions.

We notice the thing that arrived last because it’s visible. We overlook the years of capability, judgement and habit because they aren’t.

Perhaps that’s why every generation eventually feels disappointed by its miracle technology. We expect it to create capability. More often, it exposes the capability that was already there.

Maybe the next few years won’t tell us as much about artificial intelligence as they will about ourselves.

Two organisations can look remarkably similar from the outside. They deliver on time. Their customers are happy. Their people seem engaged. The numbers look healthy. If you were asked to choose between them, you’d probably struggle.

Then one experienced person leaves.

Six months later, one organisation barely notices.

The other begins to unravel.

I’ve seen versions of this often enough that I no longer think it’s coincidence, but I don’t think I’ve ever really understood why.

My first instinct was to blame leadership. Or culture. Or poor succession planning. All of those probably matter.

I’m no longer convinced they’re the whole story.

I spent much of my career in high level sport, where people are obsessed with performance. We measure almost everything. Training load. Sleep. Strength. Power. Recovery. Injuries. We look for patterns because small differences accumulate over time.

One thing always bothered me.

I remember working with an outstanding medical department. Rehabilitation was meticulous. Return-to-play decisions were thoughtful. Athletes trusted the staff completely. If you judged the department by the quality of its work, it would have been difficult to find fault.

Every Monday another athlete walked through the door with a hamstring injury.

That image stayed with me far longer than I expected. Not because the medical team was doing anything wrong. They weren’t. They were exceptionally good at what they did.

What bothered me was something else.

The better they became at rehabilitation, the easier it became for everyone else to stop asking why rehabilitation was needed so often in the first place.

At the time, I assumed those were unrelated questions.

Now I’m not so sure.

Since then, I’ve started noticing the same pattern in places that have nothing to do with sport.

The customer service team that somehow recovers every poor client experience, so gracefully that nobody upstream ever hears about it.

The executive assistant who quietly prevents a leadership team from descending into chaos, rearranging, reminding and smoothing until the leadership team believes it is simply well organised.

The finance manager with twenty spreadsheets nobody else understands, who has become, without anyone consciously deciding it should be this way, the real system of record.

The operations director who knows every workaround because the documented process stopped matching reality years ago.

We admire these people.

So we should.

The more I’ve thought about it, the more I’ve wondered whether they also change the way we judge organisations.

From a distance, what do we actually see?

Projects are delivered.

Customers stay.

Targets are met.

We don’t see the conversation that prevented a resignation. We don’t see the spreadsheet rebuilt by hand because the system failed again. We don’t see the phone call made after hours to repair a relationship that should never have been damaged in the first place.

We see the outcome.

We almost never see the work that made the outcome possible.

Remove the finance manager and watch how long it takes before someone asks where the real numbers actually live.

Lose the operations director and discover that the documented process was never really the process.

Replace the experienced coach and realise that what looked like a robust performance programme depended on one person noticing what everyone else missed.

Institutional knowledge is usually how we describe what happens next.

I’m not sure that’s quite right.

Institutional knowledge suggests something the organisation once possessed and has now misplaced.

What I’m describing feels closer to debt.

Capability quietly borrowed from individuals, year after year, without ever appearing on any balance sheet.

Eventually the debt falls due.

People talk about the departure as though it caused the decline.

Perhaps it merely exposed it.

I keep returning to the same question, and I don’t think I have a comfortable answer.

How would you know, right now, whether the parts of your organisation that are working are working because of what you’ve built, or because of who happens to still be there?

He would almost certainly never see the building finished.

Many of Europe’s great cathedrals took longer than a human lifetime to complete. The mason carving a column at twenty-five knew there was every chance somebody else’s grandchildren would place the roof above it. The quarry worker cutting stone understood that he would never know whether his own work became part of something that endured for centuries, or whether it disappeared beneath later changes, repairs and rebuilding.

Yet the stone was still cut with extraordinary care.

I’ve been thinking about that recently.

Not because I have any particular fascination with medieval architecture, but because more and more of the work that matters to me seems to operate on timescales that exceed my ability to judge whether I’m getting it right.

There’s an old saying, often referred to as the Quarry Worker’s Creed.

“We who cut mere stones must always be envisioning cathedrals.”

It’s usually presented as a lesson in purpose.

I’m no longer convinced that’s what it’s asking.

Over the past year we’ve been redesigning an assessment used with senior leaders and executives.

From the outside it looked like a routine product update. Better questions. Better reports. Better design.

From the inside, it rarely felt like progress.

We spent hours arguing over the wording of a single question because changing one verb subtly changed the behaviour we were trying to understand. We redesigned the scoring before rewriting the questionnaire because we wanted every score to point towards a better coaching conversation, not simply another number. Entire sections were abandoned because they solved today’s problem while quietly creating tomorrow’s.

There were days when it felt as though nothing had happened.

No report to show.

No feature to demonstrate.

No obvious sign that we’d moved forward.

Looking back, I doubt anyone who completes the assessment will ever notice those decisions. They’ll simply experience the result.

That’s the strange thing about well-designed systems.

The work disappears into what it makes possible.

I wonder if the same is true of culture.

When I think back to the organisations I’ve admired, I don’t remember many strategy presentations.

I remember the promotion that made perfect sense.

The conversation nobody wanted to have but someone did anyway.

The afternoon when commercial pressure collided with a stated value, and everyone quietly waited to see which one would give way.

None of those moments announced themselves.

Looking back, they seem to explain far more than the presentations ever did.

The same thought has followed me outside work.

Parents have conversations they won’t understand the significance of until years later, if ever.

Teachers explain an idea that disappears into the background of someone else’s thinking.

Coaches repeat fundamentals that eventually become instinct.

Even writing has started to feel like this.

For the past eighteen months I’ve published an essay almost every week. Most disappear quietly into the internet. Some resurface months later in conversations I never expected. Every now and then someone mentions a paragraph I’d completely forgotten writing.

If I’m honest, I don’t know what to do with that.

It makes me wonder how much of life is like this.

How many decisions only reveal themselves years after they’re made.

How many careful choices become so absorbed into the people or systems they shape that nobody notices they were ever choices at all.

Perhaps that’s why the image of the quarry worker has stayed with me.

Not because he was building a cathedral.

Because every morning he had to decide what kind of care today’s stone deserved without knowing whether he’d ever understand its place in the finished building.

I find that harder than I used to.

It’s one thing to work towards a goal you can measure.

It’s another to keep investing in something when the evidence always seems to arrive somewhere beyond the horizon.

The question I’ve been left with isn’t whether I can see the cathedral.

It’s whether I’d still be willing to cut the stone if I couldn’t.

I haven’t taken a real break since February 2025.

Back then, we were still in Saudi.

AlUla had that effect certain places have…t stays with you longer than you stay with it.

Around that time, I published the first piece on this Substack…and every week since, another one followed.

No gaps. No misses.

In that same stretch, we moved countries. I stepped into a new role. Then another, during a company transformation. Completed a PGDip in Organisational Psychology. Continued coaching. Continued travelling. Continued being a husband and father.

From the outside, it looks like a productive eighteen months…and it has been.

But productivity is a poor witness.

It tells you what got done. It says nothing about the cost of getting it done.

What recovery was skipped. What signals were ignored.

How often your system asked for space and got given structure instead.

Nothing failed…and that’s what makes it dangerous.

Capability held. Responsibility held. Achievement held.

What narrowed was harder to measure.

Curiosity had less room. Creativity needed permission. Aliveness became something postponed…and the ADHD patterns I’ve managed most of my life got louder.

There is a limit to how long any system can carry weight before it insists on being noticed. Consistency is celebrated until it becomes identity. And once that happens, stopping doesn’t feel like rest…it feels like loss.

Not that the habit is unhealthy….more like because it no longer feels like a choice.

We’ve become suspicious of seasons.

Fields lie fallow. Forests rest. Athletes deload…even the Sabbath was never intended as an optimisation strategy…merely an interruption.

Perhaps that’s why stopping feels uncomfortable…we fear what remains when the noise subsides.

If I stop producing, what remains?

If momentum fades, what was carrying it?

What only becomes visible when nothing is being harvested?

AlUla marked the beginning of this season. Eighteen months later, it’s ending.

Just a summer…no grand plans…family, friends, experiences…

And a better question than the one I started with.

Who am I when I no longer have to produce something every week?

I’m about to find out.

See you in August.

Most organisations are remarkably good at managing things that exist.

Revenue exists. Costs exist. Customers exist. Projects exist. Risks exist. Entire departments, dashboards and reporting structures have been built around making these things visible and assigning somebody responsibility for them.

Which raises an interesting question.

Who is responsible for what isn’t there?

Not in some philosophical sense, but in the very practical sense that many organisational failures have surprisingly little to do with things people can see. They emerge from things nobody notices. The customer whose needs are changing quietly. The assumption everyone shares without realising it. The competitor that doesn’t yet look like a competitor. The question nobody thinks to ask because nobody has thought to ask it before.

Absence presents a peculiar problem. Presence announces itself. Absence doesn’t.

That may be one reason hindsight always feels so cruel. Looking backwards, the signs often appear obvious. We comfort ourselves with the thought that somebody should have known. Usually somebody did.

Perhaps this is why expertise itself often involves developing sensitivity to absence.

Sherlock Holmes famously solved one mystery not because of what happened, but because of what failed to happen. The dog didn’t bark. Physicians frequently diagnose illness through what ought to be present but isn’t. Astronomers infer the existence of invisible matter because galaxies behave as though something missing is exerting force. In each case, the signal lies not in what can be observed directly, but in the shape left behind by something absent.

Organisations, unfortunately, tend to be less comfortable with this kind of reasoning. They are drawn towards the visible. Metrics attract attention. Problems with names attract attention. Customers who complain attract attention. It is far harder to mobilise around things that have no voice and no obvious presence.

This perhaps explains why the idea of the Devil’s Advocate has survived for so long. The role is usually imagined as an argumentative one, occupied by somebody willing to challenge the prevailing view. But perhaps that interpretation misses something important.

The aim was not opposition for its own sake. It was coverage, because groups have a tendency to converge. And convergence is not a bug. It is one of the reasons teams exist in the first place.

Shared understanding creates speed. Alignment reduces friction. Trust enables coordination. A group that agrees with itself feels efficient.

Until it doesn’t.

What begins as alignment can slowly become something else. Questions disappear. Assumptions become invisible. Silence begins to resemble agreement. People stop asking how they know something because everyone around them seems to know it too. Confidence acquires the appearance of completeness.

And perhaps that is why strong teams are not immune to blind spots. They may even be especially vulnerable to them.

Which is perhaps reason enough to keep asking what might be missing.

Or perhaps not.

This piece is about labels, stories and the strange way repeated narratives gradually acquire the feeling of truth…which means it turns out to be about many of the same things I usually write about after all.

A few years ago I came across the Rosenhan Experiment.

The details are fascinating, but one idea stayed with me long after I had forgotten most of the study itself.

Once people were given a psychiatric label, ordinary behaviour often stopped looking ordinary. Everything became interpreted through the diagnosis. The label arrived first. The evidence followed.

The more I thought about it, the less it felt like a lesson about psychiatry.

It felt like a lesson about being human.

Because labels are rarely neutral. Once we decide someone is difficult, talented, reliable, emotional, high potential, disorganised, strategic or lazy, we begin seeing them through that lens. The label becomes a shortcut. New information gets filtered through an existing story.

The unsettling part is that this doesn’t only happen to other people.

It happens to us.

Looking back, I spent much of my childhood collecting labels without realising it.

The wording varied, but the message was remarkably consistent…

“Capable of more.”

“Needs to apply himself.”

“Easily distracted.”

“Has significant potential.”

“Could achieve much higher standards with greater consistency.”

The comments were rarely cruel. Most were probably accurate. But reading them now, what strikes me is not any individual report. It is the repetition.

Year after year, the same themes appeared. Looking back, I realise the reports were rarely describing failure. If anything, they described proximity. I was usually close enough to demonstrate understanding, close enough to show capability, close enough to convince adults that more was possible. The frustration seemed to come from the gap between what I occasionally demonstrated and what I consistently delivered.

At the time, those comments felt like feedback on behaviour. Looking back, I suspect they were doing something more powerful. Repeated often enough, observations have a habit of hardening into identity.

A teacher’s comment is easy to dismiss. A single performance review is easy to forget. Even a moment of correction passes quickly. But when similar messages arrive from multiple directions over many years, they begin to accumulate. The individual incidents blur together, while the underlying narrative grows stronger. Eventually, you stop hearing a series of observations and start hearing a description of who you are.

The child who forgets things.

The student who doesn’t quite apply himself.

The employee with enormous potential.

The person who always seems to be nearly there.

What makes this process so difficult to notice is that the evidence rarely feels fabricated. I did forget things. I was distracted. I did leave tasks unfinished. The story survives because it contains elements of truth. A half-true story is harder to escape than a false one. It cannot be disproven. It can only be ignored.

The problem is not that the narrative is false. The problem is that it gradually becomes the only narrative available.

The tragedy is rarely misjudgment. It is reduction.

The moments that support it become highly visible, while the moments that challenge it receive remarkably little attention. I can still recall many of the corrections that punctuated school, university and the early stages of my career. I remember the feeling of being called back, redirected or reminded. I remember the subtle embarrassment of discovering that I had missed something which appeared obvious to everyone else.

What I struggle to recall with the same clarity are the countless occasions where things worked exactly as intended. Success has a peculiar tendency to disappear into the background. Mistakes linger. Corrections leave residue. The brain seems to archive them differently.

Over time, the resulting picture can become surprisingly distorted. Not because it is inaccurate, but because it is incomplete. The mind begins constructing a biography from moments of friction while quietly overlooking much of the evidence that points in other directions.

Years later, it was my son’s ADHD diagnosis that brought a great deal of clarity to experiences that had previously felt disconnected.

Like many parents, I began reading. Listening. Trying to understand a world that was suddenly much more relevant than it had been before.

The unexpected part was how often I found myself in the pages.

Patterns I had never connected began quietly connecting themselves. Behaviours that had felt random started to look less random. Old memories acquired new context. Experiences that had always existed as isolated incidents began forming recognisable shapes.

Yet I gradually realised that understanding carries its own risk. Labels are useful because they help us organise reality. They become dangerous when they begin replacing it…not because they’re inaccurate, but because they’re efficient. Once we have the label, we stop updating.

I found myself revisiting old memories and reinterpreting them through a new lens. Forgotten tasks, missed details and unfinished projects suddenly appeared to fit together. There was comfort in that. But there was also a subtle trap. Every explanation has a tendency to expand beyond its useful boundaries.

Before long, I noticed how easy it was to start viewing every struggle as evidence of ADHD while paying far less attention to the moments that contradicted the story. The periods of deep focus. The ability to learn quickly. The projects that were completed. The situations in which energy, curiosity and performance aligned remarkably well.

The diagnosis explained something real. It did not explain everything.

And that is where I found myself returning to Rosenhan.

Because the most powerful labels are often the ones we apply to ourselves. Once they take hold, they begin influencing what we notice, what we remember and how we interpret our experiences. The label no longer sits outside us. It becomes part of the lens through which we observe ourselves.

At the same time, another pattern became increasingly difficult to ignore.

Running alongside the corrections and reminders was a very different message.

The same school reports that described inconsistency also described potential.

The same teachers who pointed out distractions often expressed confidence that I was capable of more.

The same managers who highlighted gaps frequently spoke about future opportunities.

Looking back, I realise I was absorbing two stories at once.

One suggested that something about me needed fixing.

The other suggested that something about me was worth investing in.

For a long time I assumed those messages cancelled each other out. Now I suspect they were pulling in opposite directions simultaneously.

The corrections taught me where to look for flaws.

The expectations taught me where to look for possibility.

Both shaped behaviour.

Both influenced identity.

And both became part of the internal conversation.

I absorbed the corrections as truth. I absorbed the expectations as noise. I don’t know why that was. I just know it was.

Praise always felt speculative. Criticism felt like evidence.

That conversation followed me into adulthood.

Into performance reviews.

Into leadership roles.

Into coaching conversations.

Into moments where I found myself rewriting an email one more time, checking a proposal one more time, or preparing just a little more thoroughly than the situation required.

On the surface, it looked like conscientiousness.

Underneath, I suspect there was often something else.

A lingering memory of being corrected.

A desire to avoid missing something important.

A determination not to become the person described by the old story.

Many people with ADHD eventually develop remarkably sophisticated compensation strategies. From the outside they often look like strengths. Attention to detail. Preparation. High standards. Relentless follow-through.

Sometimes they are strengths.

Sometimes they are adaptations.

Often they are both.

The challenge is that successful adaptation can make the original narrative even harder to question. When the system works, the effort remains invisible. When something slips through, the old explanation immediately reappears.

There it is again.

Proof.

Confirmation.

Evidence that the story was right all along.

Yet the older I get, the less convinced I am that human beings are best understood through labels, even accurate ones.

They are useful.

They explain patterns.

They provide language for experiences that previously felt confusing.

But they also conceal.

Every label illuminates certain aspects of reality while pushing others into shadow.

What interests me now is how often the same pattern appears far beyond ADHD.

In organisations.

In families.

In schools.

In leadership teams.

Someone becomes “the difficult one.”

Someone else becomes “the future leader.”

One employee is known for their creativity. Another for their lack of attention to detail.

Over time, behaviour starts getting interpreted through those identities. The same action can be viewed completely differently depending on who performs it. One person’s challenge is seen as insight. Another’s is seen as resistance. One person’s mistake is an exception. Another’s is confirmation.

The label arrives first.

The evidence follows.

Perhaps that is why old school reports still feel strangely powerful decades later. Not because of the specific comments they contain, but because of the narratives they helped establish. Many of us are still responding to expectations formed years ago by teachers, parents, managers and, eventually, ourselves.

And the question that keeps me awake is not whether the label is true.

It’s how much of what I believe about myself is observation,

and how much is simply a story that became familiar through repetition.

Because once a label arrives first, it can take a very long time before we realise we have stopped looking beyond it.

I’ve been around gyms for most of my adult life, that’s around 3 decades, so long enough to watch training trends come and go, and long enough to have been guilty of most of them myself.

At various points I’ve become deeply interested in rest intervals, velocity-based training, force-velocity profiling, contrast loading, accommodating resistance, periodisation models, recovery technologies, supplements, peptides, breathing protocols, and enough other rabbit holes to keep a reasonably active ADHD brain entertained for several lifetimes.

Most of it is interesting. Some of it is useful. A small amount of it is genuinely valuable.

But every now and then I find myself looking around a gym and noticing something slightly awkward: the people making the most progress are often not the people thinking about training the most. They’re usually the people doing it.

The strange thing is that most people already know this. If I took someone who had never exercised before and told them to sleep a bit more, walk every day, lift some weights a few times a week, eat mostly sensible food, and continue doing that for the next five years, nobody would accuse me of revealing ancient secrets. Most people would nod politely, then immediately search YouTube for something more sophisticated.

Which is understandable.

The fundamentals feel almost insulting.
Sleep a bit more.
Walk every day.
Lift some weights.
Repeat for several years.

Nobody wants that to be the answer.
Sometimes there is more to it.
Most of the time there isn’t.

Humans are attracted to complexity in strange ways. It feels valuable. It feels intelligent. It feels like effort. The fundamentals, by contrast, feel like nothing is happening. You can’t show a complex periodisation model on Instagram and feel proud. You can’t post a photo of consistency. You can’t point to a spreadsheet of sleep hours and feel clever.

So people keep looking for the next thing. A new protocol. A new tool. A new metric. A new protocol to optimise the protocol. And the industry keeps delivering it, because it works. Consistency is boring. Complexity sells.

And this isn’t just a fitness problem. It’s the same failure mode in human psychology showing up in a different context. The same brain, doing the same thing.

In organisations, the pattern is identical. Nobody ever walks into a struggling organisation and says, “You know what this needs? Fewer things.” Instead, everybody starts building, knowingly or not, accumulating in ways that mirror exactly what we do in the gym.

A new framework appears, followed shortly afterwards by a new process, a steering committee, a dashboard and several workshops. Before long there are enough governance structures to run a small operation.

The interesting part is that none of these things are inherently bad. In fact, that’s precisely why organisations end up accumulating so much of them. The new report exists because somebody wanted visibility. The new governance process exists because something went wrong once. The additional approval step exists because somebody made a mistake that was expensive enough to become memorable. The workshop exists because there was a genuine capability gap. The dashboard exists because somebody wanted better information.

Viewed individually, most organisational complexity is surprisingly reasonable. Every addition makes sense when viewed on its own. The problem only appears when viewed collectively.

A bit like body fat, actually. Nobody wakes up one morning twenty kilograms overweight because of a single decision. It’s the accumulation that matters. One snack doesn’t matter. One missed walk doesn’t matter. One skipped session doesn’t matter. Until eventually it does.

Organisational complexity often behaves the same way. Each addition seems trivial. Then one day nobody can quite work out why simple decisions require six meetings and a steering committee.

Eventually the thing still functions. Just much more slowly.

And beneath all of this complexity sits a question that I suspect most organisations don’t enjoy asking: are we actually struggling with a knowledge problem, or are we struggling with an execution problem? A knowledge problem means we genuinely don’t know what to do. An execution problem means we already know…we just aren’t doing it consistently.

That is a much less comfortable conversation, partly because execution lacks glamour. Nobody gets excited about consistency. Nobody writes books called The Seven Habits of Repeatedly Following Through on What You Said You Would Do. Nobody attends conferences on the revolutionary power of having the difficult conversation you should have had three months ago. Yet that is often where performance lives. Not in discovering the next answer, but in applying the current one.

Again. And again. And again.

The fitness industry has spent decades finding increasingly sophisticated ways to package consistency. I sometimes wonder if organisations do exactly the same thing. Not because the fundamentals are wrong. But because the fundamentals are boring.

And boring rarely feels like progress. Even when it is.

Almost everybody has had this experience…

You leave a meeting and something feels off.

Nothing dramatic happened. Nobody stormed out. No catastrophic decision was made. The slides looked professional, the discussion seemed productive, and the meeting ended on time.

From a management perspective, it was practically a triumph.

Yet as people walk out, somebody says:

“That felt a bit strange.”

And everybody immediately knows what they mean.

Nobody asks for evidence. Nobody requests supporting documentation.

The observation lands because everyone felt it., but the strange thing is that nobody can quite explain it…at least not yet.

I’ve become increasingly interested in this phenomenon.

Not because it only happens in organisations. It doesn’t.

It happens in sport. It happens in medicine. It happens in families.

It happens almost everywhere humans gather.

People often notice things long before they can explain them.

A coach watches an athlete and senses something has changed. A clinician becomes uneasy despite normal test results. A parent knows something is bothering their child before a single word is spoken. A leader walks into a room and feels a shift in atmosphere.

The observation arrives before the explanation.

Which is awkward, because we tend to prefer explanations.

That preference is understandable. Explanations feel rational. They feel defensible. They fit neatly into reports, presentations, governance structures, and decision logs.

Observations are messier…especially when they arrive carrying uncertainty.

Yet reality has an annoying habit of arriving in exactly that form.

This may explain one of the stranger contradictions in organisational life.

Most failures look obvious afterwards…painfully obvious.

After the strategy fails, everyone can explain why. After the leader leaves, everyone can explain why. After the culture deteriorates, everyone can explain why.

The confidence is remarkable.

If an archaeologist examined the post-mortem reports of modern organisations, they might reasonably conclude that human beings possess supernatural predictive abilities.

Apparently everybody knew, but nobody acted…but everybody knew.

Humans are exceptionally good at post-rationalising. In hindsight, causes become clearer, signals become stronger, stories become tidier, and reality becomes easier to explain.

The danger is that explanation creates the illusion that perception existed all along.

It didn’t.

Or at least not in the form we imagine.

What often existed was something much messier.

A concern. A hesitation. A conversation over coffee. A nagging sense that something wasn’t quite right.

I’ve seen versions of this play out repeatedly.

Someone raises a concern. Not a dramatic concern. Just an observation.

A project feels more fragile than the status report suggests. A team feels less engaged than the survey indicates. A strategy sounds increasingly convincing and increasingly detached from reality.

The observation lands politely and then disappears…not because people disagree, just because nobody can quite prove it.

Six months later the same observation returns, now supported by declining results, missed targets, resignations, or customer complaints.

Suddenly everybody agrees!

The strange thing is that it wasn’t necessarily more accurate. It was simply easier to defend.

One of the stranger features of modern organisations is that they often demand certainty from problems before they are willing to pay attention to them.

Can we prove it?

Can we quantify it?

Can we establish causality?

Can we justify escalating it?

All reasonable questions.

The difficulty is that reality rarely provides certainty in advance. The first signs of change usually arrive incomplete…as discomfort, as ambiguity, as patterns that are difficult to defend and impossible to ignore.

Organisations are often designed to filter noise, and that is usually a good thing…until something genuinely important arrives disguised as noise, then the filters become part of the problem.

Perhaps healthy organisations are not distinguished by their ability to eliminate uncertainty. Perhaps they are distinguished by their ability to remain curious about it. To investigate observations before they become conclusions. To explore questions before they become problems. To treat uncertainty as information rather than inconvenience….because most important signals arrive long before they become respectable.

A concern raised early is an opinion. The same concern raised six months later is insight. The difference is rarely accuracy. It is usually timing. Reality rarely announces itself. It usually whispers first, and the challenge is not hearing it. The challenge is trusting what you heard before everyone else can hear it too.

Most organisations claim they want strategic thinking….what they actually reward is rapid administrative responsiveness….and these are not the same thing.

The modern workplace increasingly resembles a casino designed by project managers.

Lights flashing. Notifications everywhere. People sprinting between meetings carrying emotional support water bottles and unfinished thoughts.

Everyone is “across it.” - but nobody has read anything longer than four paragraphs in six weeks.

And somehow this is considered operational maturity.

A strange thing happens when execution becomes culturally sacred.

The organisation slowly loses tolerance for cognition that does not immediately convert into visible output.

Reflection starts looking suspiciously unproductive. Questions become uncomfortable because they slow momentum. Nuance starts sounding like poor alignment.

Eventually the highest-status person in the room becomes the one capable of replying to emails while simultaneously attending three meetings and quietly dissociating.

This is often called leadership.

The problem is not execution itself. Execution matters. Airlines generally benefit from pilots eventually landing the plane.

The problem is that many organisations have accidentally created environments where continuous execution becomes a substitute for thinking entirely.

Not intentionally.

Socially.

People learn quickly what gets rewarded.

Speed. Certainty. Visibility. Responsiveness. Optimism. Calendar density.

Meanwhile hesitation starts feeling risky. Deep work becomes antisocial. Dissent feels inefficient. Exploration appears…indulgent.

Eventually the organisation starts producing a very specific type of person.

Highly functional. Operationally exhausted. Strategically narrower every quarter.

You can see this happening in leadership teams everywhere.

Meetings become performative. Language becomes increasingly confident. Nobody says “I don’t know.”

PowerPoints become emotionally smoother. Complexity gets translated into traffic-light colours for senior management.

Every problem acquires a deadline regardless of whether the problem understands time. The organisation begins aggressively simplifying reality in order to maintain movement.

This works surprisingly well…for a while. And that is partly what makes it dangerous.

Many executives now exist inside uninterrupted cognitive fragmentation.

Slack. WhatsApp. Email. Teams. Board papers. Quarterly targets. Escalations. “Quick calls.” “Quick follow-ups.” “Quick thoughts.”

There are now entire corporate ecosystems where nobody has had an uninterrupted hour to think.

Then leaders wonder why originality drops.

Why strategy feels recycled.

Why adaptation slows.

Why everyone sounds the same.

Why decisions become politically safer.

Why innovation decks start resembling AI-generated hostage videos.

The human nervous system was not built for permanent attentional shrapnel.

Neither was judgment.

One of the stranger features of modern work is how busyness became a prestige signal.

People now openly brag about sleep deprivation, impossible calendars, message volume, back-to-back meetings, and being “slammed.”

Imagine an airline pilot proudly announcing:

“I haven’t properly rested or reflected in months but thankfully I’m making decisions much faster now.”

Nobody would board the aircraft.

In corporate environments this often gets promoted.

The deeper problem is that execution consumes optionality.

Every rushed decision closes alternative pathways before they can fully emerge.

Every overloaded system becomes more dependent on familiar patterns because familiarity is metabolically cheaper.

This is why stressed organisations become repetitive.

Not because people stop caring.

Because the system no longer has enough cognitive surplus to explore properly.

Eventually curiosity itself starts feeling operationally irresponsible.

This is where many organisations quietly drift into strategic blindness.

Not a movie-scene dramatic collapse…something slower…more civilised.

The organisation simply becomes less capable of updating itself.

People continue speaking confidently. Targets continue getting tracked. Town halls continue happening. The strategy offsite still has artisanal pastries.

Meanwhile reality starts moving faster than the institution’s ability to rethink its assumptions.

And because execution-heavy environments generate enormous amounts of visible activity, leaders often mistake motion for adaptation.

This becomes especially dangerous during uncertainty.

Under pressure, many organisations increase the exact conditions that reduce adaptive thinking.

More reporting. More alignment sessions. More operational oversight. More urgency theatre. More performative responsiveness.

The organisational equivalent of shaking the vending machine harder because the snack got stuck.

Then they act surprised when innovation narrows.

When risk detection weakens.

When dissent disappears.

When political behaviour rises.

When people stop telling the truth early.

At this stage the organisation still looks healthy on paper.

Glaciers usually do.

The interesting thing is that genuinely elite environments rarely operate this way.

Aviation does not solve complexity by adding seven more status meetings.

Formula 1 teams do not improve strategy by ensuring nobody has uninterrupted thought for three consecutive months.

Special operations units do not treat cognitive exhaustion as a leadership competency.

Serious performance environments understand something corporate culture increasingly forgets:

Cognitive quality is operational infrastructure, not a luxury.

Which means they actively protect it.

They build pause into systems outsiders mistakenly interpret as pure speed.

Review loops. Challenge functions. Decision audits. Protected thinking time.

Pre-mortems. After-action reflection. Structured dissent.

Why?

Because they understand that accelerated stupidity compounds faster than almost anything else.

Corporate environments often copy the aesthetic of high performance while ignoring the cognitive architecture underneath it.

So they recreate urgency, pressure, speed, and intensity without recreating reflection, recovery, challenge, or adaptive space.

The result is an organisation permanently in motion but increasingly incapable of reconsidering itself.

“Corporate environments often copy the aesthetic of high performance while ignoring the cognitive architecture underneath it.”

Eventually the organisation becomes highly efficient at producing exhausted people who can no longer think beyond the system they are trapped inside.

At that point leadership teams are no longer steering the organisation.

They are managing the emotional comfort of continued motion.

The meetings continue. The dashboards continue. The quarterly language continues.

Everyone remains extremely busy.

Meanwhile the organisation slowly loses the ability to distinguish movement from progress.

And because the system still feels operationally intense, almost nobody notices the thinking disappeared years earlier.

Good or bad.
Fast or slow.
Delivered or missed.

But experienced operators eventually learn to watch something else.

Not the decision itself.

The texture surrounding it.

How much effort it takes to think.

Healthy Systems Feel Lighter

Healthy systems often make difficult decisions surprisingly lightly.

Not casually.
Not recklessly.

Lightly.

People can hold unfinished ideas without panic.

Conversations move.

Questions stay open a little longer.

Someone says something half-formed.
Another person pulls on a loose thread that may or may not matter.

Disagreement does not immediately feel operationally dangerous.

The system bends without immediately hardening.

When Thinking Starts Becoming Heavy

Unhealthy systems feel different.

Even simple decisions begin acquiring strange amounts of weight.

Emails get rewritten three times.

Meetings repeatedly circle questions that were supposedly settled last week.

Tiny ambiguities trigger disproportionate escalation.

People ask for reassurance before moving on things they previously handled independently.

Nobody says:

“Thinking suddenly feels heavier here.”

But you can feel it.

The Dashboard Usually Looks Fine

The dangerous part is that this rarely appears in formal metrics.

Delivery remains acceptable.
Escalations stay manageable.
Meetings still end with agreement.

On paper, nothing appears badly wrong.

Sometimes the organisation even appears more disciplined during this phase.

Cleaner meetings.
Shorter discussions.
More alignment.
Less dissent.

From the outside, it can look like maturity.

From the inside, it can feel like the organisation is becoming increasingly unable to think beyond what already feels operationally safe.

Reprocessing The Same Uncertainty

One of the clearest signs is revisit frequency.

How often organisations reopen decisions they already made.

Not because conditions changed.

Because nobody fully trusts the original judgement.

So the system burns energy reprocessing the same uncertainty repeatedly.

Healthy systems metabolise uncertainty once.

Fragile systems keep reopening it in slightly different language.

At scale, this creates a hidden tax on organisational cognition.

Not dramatic dysfunction.

Just continuous low-grade friction.

Conversational Compression

Another signal is conversational compression.

Healthy environments can tolerate exploratory dialogue.

Conversations wander slightly.

Someone throws out an unfinished thought.
Somebody else challenges it.
A third person reframes the problem entirely.

Not every useful idea arrives fully organised.

Stressed systems become narrower.

Everything must become executable immediately.

People stop thinking out loud.

You notice more polished answers.
Fewer unfinished sentences.
Less visible uncertainty.

Discussion becomes less about discovery and more about closure.

Certainty starts outperforming curiosity.

Many organisations quietly train exploratory thinking out of people while believing they are improving execution.

Systems Usually Tighten Before They Break

You see similar patterns in elite sport.

Athletes under excessive cognitive load often become mechanically tighter before performance visibly drops.

Movement loses fluidity before output disappears.

Organisations often behave the same way.

The Atmosphere Changes First

Experienced leaders often detect this intuitively.

Not through KPIs.

Through atmosphere.

They notice the increased hesitation.
The emotional flattening.
The shortening of debate.
The subtle rise in defensive communication.

They notice the organisation becoming operationally heavier.

Because by the time performance decline becomes measurable, the cognitive strain has often been accumulating for months.

Sometimes much longer.

Most organisations do not collapse because they stop functioning.

They collapse because functioning gradually becomes cognitively unaffordable.

The dangerous thing about performance decline is that it rarely looks like decline while it’s happening.

It often looks like professionalism.

Calendars become tighter.
Language becomes more certain.
People stop exploring and start executing.
Humour disappears.
Curiosity narrows.
Meetings become increasingly operational.

From the outside, this can even look impressive.

That is partly why organisations miss it.

We are very good at detecting landslides.
We are much worse at detecting glaciers.

Decisions that used to feel light become expensive.
Simple tasks require more recovery.
Optionality narrows.
People become less adaptive, but often more decisive.

And because the outputs may still look strong for a while, the early symptoms are frequently rewarded rather than challenged.

Exhausted leaders get promoted for commitment.
Rigid thinking gets mistaken for clarity.
Emotional flattening gets interpreted as stability.

The system mistakes narrowing for maturity.

That’s the trap.

Where It Shows Up First

You see it in leadership meetings first.

Senior teams stop asking exploratory questions and start asking executable ones.

The discussion becomes narrower.
Faster.
Cleaner.

Fewer loose threads.
Fewer uncomfortable tangents.
Less tolerance for ambiguity.

It feels like alignment.

Sometimes it is.

Sometimes it is a system quietly losing cognitive flexibility.

Because adaptive capacity and resilience are not the same thing.

A resilient system can absorb pressure and continue functioning.

An adaptive system can still change shape under pressure.

Many organisations pride themselves on resilience while slowly losing adaptability.

Deadlines still get met.
Decisions still get made quickly.

But the range of thinking available to them quietly shrinks.

The same ideas circulate.
The same people dominate decisions.
The same assumptions go unchallenged.

Meetings become increasingly operational because operational conversations are cognitively cheaper than exploratory ones.

Execution starts replacing thinking.

And in high-performance environments, this can continue for a surprisingly long time without anyone recognising the cost.

The Metrics Miss It

The people experiencing it often still look highly capable.

They are not underperforming in any obvious sense.

In fact, many become faster and more decisive for a period of time.

But there is a difference between output and adaptability.

A system can maintain output while becoming progressively more fragile underneath.

That is why most performance metrics detect decline too late.

Dashboards are very good at measuring visible outcomes.
They are much worse at detecting narrowing perception.

The early warning signs tend to appear elsewhere:

In shortened patience.
In certainty language.
In disappearing curiosity.
In reduced appetite for experimentation.
In how quickly discussions move to closure.

You see it when people stop saying:

“What else might be true?”

and start saying:

“This is obviously the answer.”

The Cost Of Certainty

Ambiguity is metabolically expensive.

Over time, organisations begin unconsciously rewarding the people who reduce ambiguity fastest, even if they are also reducing possibility.

That is why some leadership teams become progressively less exploratory while continuing to appear highly functional.

Like a glacier, the movement is slow enough to normalise while it is reshaping the landscape underneath.

And by the time the damage becomes visible in the numbers, the valley has often already been carved.

I suspect this is where leadership development may need to evolve next.

Less focus on performative resilience.
More focus on protecting adaptive capacity before the system becomes cognitively frozen.

Because most organisational decline does not begin with failure.

It begins with a gradual loss of cognitive range that nobody notices quickly enough.

Or are they capacity failures?

Same leader. Same data. Completely different call.

You’ve seen it.

End of the day.
Fifth meeting in a row.
Travel week.

The conversation gets shorter.

Options thin out.

Someone says, “this is probably the right call.”

People nod a little too quickly.

Nothing obviously wrong happens.

That’s usually when something is off.

We like to blame ego, or poor judgment…or the wrong person being in the room.

Sometimes that’s true. Most of the time, it’s less dramatic.

People are just tired.

Not visibly tired….operationally tired.

The kind that sounds like:

• “Let’s just move this forward”

• “We can revisit later”

• “This is the best option we have”

It all sounds reasonable.

That’s usually where it starts to slip.

Call it a discipline problem if you want.

It doesn’t behave like one.

What goes first isn’t accuracy.

It’s range.

You stop looking. You start choosing.

Pattern recognition takes over in situations that don’t quite match.

You lean toward the safest option, or the fastest one.

Sometimes both….and it passes for decisiveness, and you don’t feel the shift as it happens.

Which is why senior teams are so exposed to it.

Awareness doesn’t fix this.

Most people in the room already know something feels off.

What changes things is constraints.

The kind that get resisted because they’re inconvenient.

The Capacity Stack

Not a wellness routine.

This is the part that decides whether your thinking holds up or quietly gets worse.

Sleep

Everyone agrees it matters….then schedules like it doesn’t.

This isn’t just “try to get more.”…you need actual boundaries.

Which tends to mean:

• no early meetings after late travel

• not pretending 5 hours is sustainable

• not wearing exhaustion as proof of commitment

Most teams say resilience matters….you don’t see much evidence of it in the calendar.

Light and movement

This is where people disengage, because it sounds like lifestyle advice, which is usually where it gets dismissed…until energy becomes unpredictable.

And then everything feels harder than it should.

You don’t need a fixed protocol…you need to not spend the entire day indoors, stationary, and cognitively loaded.

Decompression

Almost no one does this properly.

One meeting ends, another starts. Or there’s a “break” that adds more input.

Then patience drops, and decisions speed up.

You’re not switching states….you’re carrying one straight into the next.

Decision buffers

This is where resistance shows up.

Because speed looks like competence, it also covers for poor thinking.

Try:

• no real decisions in the last 90 minutes of the day

• anything vaguely strategic waits 24 hours

• discussion and decision separated, even briefly

It feels slow….but that’s part of the point.

Stop rules

Most teams don’t define these.

So decisions get made anyway.

Late. Rushed. Low energy.

Then defended later with surprising certainty.

Set rules for when decisions don’t happen, and you’ll remove a lot of avoidable errors without needing better people.

If decisions get worse under pressure, the setup was already shaky.

Most teams try to improve decision quality by improving thinking.

Workshops. Frameworks. Better questions.

All reasonable.

They don’t hold if the conditions underneath are unstable.

A simple check

Where do your decisions start to slip?

• late in the day

• under time pressure

• after back-to-back meetings

• during travel

• when energy is inconsistent

You don’t need to think too hard about it.

Then do one thing.

Pick a constraint.

Just one.

Run it for a week.

If nothing changes, ignore this.

If something does, it’s probably not where you thought the problem was.

Evidence (for people who need it)

• Sleep loss reduces cognitive flexibility and shifts risk

• Decision fatigue pushes people toward defaults

• Cognitive load narrows the number of options you consider

(Harrison & Horne • Baumeister • Danziger • Sweller • Shah & Oppenheimer)

Consensus can lower tension in the room while raising risk outside it.

Many bad decisions are not made by one overconfident person.

They are made by six cautious people trying not to offend each other.

That sounds glib.

It isn’t.

It describes a failure mode common in leadership teams, boards, investment committees, and executive groups.

And because it often feels collaborative in the moment, it can be hard to detect.

We romanticise consensus as if agreement signals judgement.

Often it signals something else: social comfort, conflict avoidance, reputational risk management.

Sometimes consensus improves decisions.

Sometimes it quietly protects people from disagreement.

Those are not the same thing.

Agreement is not accuracy

A room can agree and still be wrong.

Decades of social psychology show how easily groups suppress dissent under pressure to conform. Solomon Asch’s experiments showed people would abandon their own obviously correct judgement to align with a group’s incorrect answer, not because they believed the group was right, but because the cost of standing out felt higher than the cost of being wrong.

Irving Janis later showed how cohesive, high-functioning groups can slide into groupthink when the desire for unanimity overrides realistic appraisal of alternatives.

He built much of that argument from cases like the Bay of Pigs Invasion, where pressure toward unanimity appears to have crowded out dissent.

High-functioning people.

Poor collective judgement.

The danger is rarely overt coercion.

It is softer than that.

Someone hesitates.

Someone self-censors.

Someone decides not to be the person who slows the room down.

And weak assumptions survive scrutiny not because they were tested—

but because they were not challenged.

That is not consensus.

That is friction avoidance.

Consensus can produce premature convergence

This is rarely stated aloud.

But often true.

Consensus can function as a social technology.

It protects:

• Harmony

• Status

• Political capital

• Identity

• Future relationships

All valuable things.

But they can come at a cost.

The risk is that the room converges too early.

And premature convergence is often where decision quality degrades.

You see this in strategy reviews, risk committees, hiring panels, and boards.

A proposal accumulates enough nods to feel inevitable.

Dissent starts feeling disruptive.

And the threshold for challenge quietly rises.

Not because the decision improved.

Because the social cost of objection increased.

That is a very different mechanism.

When everyone owns it, no one owns it

Consensus often diffuses responsibility.

That is one reason it feels safe.

If everyone supported it, no one can be singled out if it fails.

This is classic diffusion of responsibility, associated with the work of Bibb Latané.

The decision feels robust because many people touched it.

But distributed input can easily become diluted ownership.

And those are not the same.

Consensus can slow decisions without improving them

This is the part many organisations struggle to admit.

More voices do not always produce better judgement.

Sometimes they produce negotiated ambiguity.

That is something else.

High-performing teams often use a different model:

• Debate widely

• Decide clearly

• Commit fully

Input from many.

Commitment from one.

That is not autocracy.

It is clarity.

It is why principles like “disagree and commit,” often associated with Jeff Bezos, matter.

They preserve dissent without making unanimity the standard.

Subtle difference.

Huge implications.

Why dissent feels costly

Because dissent is rarely evaluated as information.

It is often experienced as threat.

Threat to cohesion.

Threat to competence.

Threat to hierarchy.

And under threat, groups simplify.

They seek closure fast.

That often looks like consensus.

It may actually be anxiety reduction.

Important distinction.

Better than consensus

Maybe the goal should not be consensus.

Maybe the goal is well-structured disagreement.

Some mechanisms help:

• Red teams

• Pre-mortems

• Assigned dissent roles

• Explicit decision owners

• “What would have to be true for this to fail?”

These do not make decisions slower.

They often make them better.

Because they lower the social cost of challenge.

And that is usually the real bottleneck.

The stronger standard

The strongest teams are not those with the least disagreement.

They are those where disagreement is least threatening.

That is a very different standard.

And much rarer.

The uncomfortable question:

Is your team seeking the best decision—

or merely the least objectionable one?

It takes a damn good meeting to be better than no meeting.

Most don’t clear that bar.

Yet calendars stay full, not because the work demands it, but because the system does.

The cost no one prices in

Ask a simple question: what does this meeting cost?

Ten people. Sixty minutes. You’re already into four figures…before a word is said.

Now add context switching. Pre-reads. Recovery time.

The real cost is higher than it looks, and rarely accounted for.

Yet meetings are still scheduled like they’re free.

They’re not.

Most meetings don’t have a job

Try this in your next meeting:

“What decision are we here to make?”

Watch what happens.

Silence. Vague answers. Multiple interpretations.

If there’s no decision, there’s no reason to meet.

What most teams call meetings are:

• Status broadcasts

• Alignment theatre

• Low-stakes updates dressed up as collaboration

They feel productive.

They rarely move anything forward.

A meeting should do one thing: move a decision.

If it doesn’t, it’s leakage.

Timing isn’t neutral

Same team. Same data. Different moment. Different outcome.

Under cognitive load, the brain shifts. Less control, more shortcuts, lower-quality judgement.

You see it every day:

• Late afternoon calls drift

• End-of-week meetings default to safe options

• Post-travel sessions lack sharpness

This isn’t motivation. It’s capacity.

Yet organisations schedule as if energy is constant.

It isn’t.

Agenda is a filter, not admin

“No agenda” sounds harmless. It isn’t.

It removes the forcing function.

A clear agenda does two things:

• Clarifies the decision

• Tests whether the meeting is needed at all

If you can’t write it clearly, you won’t solve it verbally.

So the meeting expands…more voices, more noise, less progress.

Agenda isn’t about structure.

It’s about constraint.

Why this persists

Meetings don’t just solve work problems. They solve social ones.

They signal:

• Inclusion

• Visibility

• Control

• Safety

Cancel a meeting and you don’t just remove time, you remove a signal.

That’s why organisations drift toward more meetings, not fewer.

It feels like coordination.

It’s often reassurance.

Meetings are often insurance

Many meetings are not held to improve decisions.

They are held so nobody can be blamed for them.

That changes how you see consensus.

Consensus often isn’t quality control.

It’s reputational risk hedging.

Get enough people in the room and accountability diffuses.

The decision feels safer.

It often gets worse.

That’s not collaboration.

That’s institutional insurance.

Meetings are often the default

In many organisations, a meeting is what happens when nobody has designed an alternative.

Need alignment? Book a meeting.
Need an update? Book a meeting.
Need to avoid thinking alone? Book a meeting.

The meeting becomes the default option.

And defaults are sticky.

Not because they’re optimal.

Because they avoid friction.

That’s how low-value habits become operating norms.

The real issue: lack of constraints

Some teams don’t have too many meetings.

They have too few rules governing them.

• No cost awareness

• No decision ownership

• No energy consideration

• No entry criteria

So the system defaults to volume.

And volume hides inefficiency.

A simple operating model

Run this for one week…not as a theory, as a constraint:

1. No agenda, no entry: If it’s not written, it doesn’t happen

2. No decision, no meeting: Every meeting must move a named decision

3. One owner: Not consensus…ownership

4. Protect energy windows: No strategic meetings late-day or post-travel

5. Default to async: If it’s an update, write it

What actually changes

Fewer meetings.

Sharper decisions.

Because you stop treating time as the constraint, and start treating attention as the asset.

The uncomfortable question

If every meeting appeared as a line item on a P&L,

Which ones would survive procurement scrutiny?

The Meeting

The room is quiet. A major decision is on the table. Data is incomplete, the timeline is compressed, and the stakes are high.

The CEO leans forward and says, “There’s no other way.”

The discussion ends. Heads nod. The decision moves forward.

Not because every option was explored.
Not because the evidence was definitive.
But because certainty reduced the collective discomfort of not knowing.

This is how many strategic decisions are made. And it reveals a dangerous assumption embedded in leadership culture: confidence is treated as a proxy for competence.

The Seduction of Certainty

In many organisations, the most certain voice often wins the room. Confidence conveys control, authority, and momentum. It reassures teams and signals decisiveness to stakeholders.

Listen carefully to the language of certainty:

• “It’s obvious.”

• “There’s no other way.”

• “This is the only path that makes sense.”

These statements rarely signal clarity. They signal collapsed optionality…a premature convergence on a single solution before the problem has been fully explored.

Behavioural research consistently shows that individuals overestimate the accuracy of their judgments, a phenomenon known as overconfidence bias (Kahneman, 2011). In group settings, this bias is amplified by authority dynamics, where the most confident voice exerts disproportionate influence regardless of actual expertise.

What Happens to the Brain Under Threat

Under perceived threat, the brain prioritises speed over flexibility. The prefrontal cortex, responsible for strategic thinking and cognitive flexibility, becomes less effective, while more reactive neural systems dominate.

Amy Arnsten’s research demonstrates that stress impairs prefrontal cortex functioning, reducing our capacity for nuanced judgement and increasing reliance on habitual responses (Arnsten, 2009).

In leadership contexts, this manifests as:

• Narrowed attention and reduced situational awareness

• Increased reliance on familiar or dominant solutions

• A preference for decisive action over exploration

• Greater susceptibility to groupthink and authority bias

Confidence, in these moments, often functions as a coping mechanism, providing psychological relief from uncertainty rather than evidence of sound reasoning.

Confidence as a Structural Signal

Confidence is not merely an individual trait; it is reinforced by organisational systems. Many companies implicitly reward certainty through promotion criteria, performance evaluations, and cultural norms that equate decisiveness with leadership strength.

Research by Anderson and Kilduff (2009) shows that individuals who display confidence are more likely to attain influence within groups, independent of their actual competence. Over time, this creates a reinforcing cycle:

1. Confidence signals authority.

2. Authority increases influence.

3. Influence validates confidence.

4. Alternative perspectives are suppressed.

The result is a culture where certainty becomes a structural advantage, even when it undermines decision quality.

A Contrast: When Competence Creates Options

Some organisations deliberately counteract this tendency by designing decision processes that preserve optionality.

NASA provides a powerful example. Following the Challenger disaster, the agency introduced rigorous simulation, dissent protocols, and probabilistic risk assessments. Engineers are encouraged to express uncertainty in numerical probabilities rather than definitive statements, ensuring that multiple scenarios are considered before commitment. This approach embeds humility and exploration into the decision process, improving both safety and strategic outcomes.

Similarly, Netflix promotes a culture of “informed captains,” where leaders are empowered to make decisions but are expected to rigorously test assumptions and consider alternative options. The emphasis is not on projecting certainty but on demonstrating the quality of the thinking that precedes action.

These organisations illustrate what it looks like when competence creates options rather than collapsing them.

The Cost of Collapsed Optionality

When confidence is rewarded over competence, organisations face several hidden risks:

Strategic Blind Spots

Premature convergence limits the exploration of alternative strategies, increasing vulnerability to unforeseen changes.

Reduced Cognitive Diversity

Team members may withhold dissenting views when confronted with a highly confident authority figure, leading to groupthink.

Escalation of Commitment

Confident decisions are more likely to be defended even when evidence suggests they should be reconsidered.

Fragile Decision-Making

Strategies built on certainty rather than exploration are less adaptable when conditions change.

These dynamics are particularly dangerous in complex environments, where no single “obvious” solution exists.

Reopening Strategic Space

If confidence narrows thinking, leadership must intentionally reintroduce optionality. A simple yet powerful intervention is the question:

This prompt:

• Reduces psychological defensiveness

• Encourages counterfactual thinking

• Signals intellectual humility

• Expands the range of strategic options

Small interventions like this can have asymmetric impact, significantly improving decision quality at minimal cost.

What Organisations Should Reward Instead

If confidence is a poor proxy for competence, leaders should look for more reliable signals:

• Exploration before commitment – Multiple plausible options are considered prior to convergence.

• Intellectual humility – Willingness to update views as new information emerges.

• Comfort with uncertainty – Recognition that ambiguity is inherent in complex decisions.

• Inquiry-based language – Questions that expand thinking rather than statements that close it.

• Probabilistic thinking – Expressing judgments in terms of likelihoods rather than certainties.

From Decisiveness to Decision Quality

This perspective does not argue against decisiveness. Organisations require timely action. The distinction lies between decisiveness and premature certainty.

Effective leaders:

• Explore broadly before committing.

• Establish clear ownership of decisions.

• Remain willing to adapt as new information emerges.

• Separate confidence in execution from certainty in prediction.

Competence is revealed not by how certain a leader appears, but by the quality of the thinking that precedes action.

Practical Leadership Interventions

Leaders can embed this mindset through simple structural changes:

1. Language Audits

Monitor and challenge certainty-based language in meetings.

2. Option Generation Norms

Require teams to present multiple viable options before strategic decisions.

3. Psychological Safety for Dissent

Encourage respectful disagreement to counteract authority and overconfidence biases (Edmondson, 1999).

4. Pre-Mortem Analysis

Ask teams to imagine that a decision has failed and identify potential reasons why (Klein, 2007).

5. Probabilistic Forecasting

Adopt forecasting practices that emphasise likelihoods and continuous updating of beliefs (Tetlock & Gardner, 2015).

The Strategic Implication

Treating confidence as a performance metric creates fragile organisations. It rewards certainty over curiosity and speed over judgement. Organisations that prioritise optionality and inquiry are better equipped to navigate uncertainty and sustain performance.

Confidence reassures.
Competence creates options.

A Question for Leaders

Where in your organisation does confidence masquerade as competence?

This question is not merely reflective. It is diagnostic. The answer often reveals where strategic blind spots are most likely to emerge.

References

• Anderson, C., & Kilduff, G. J. (2009). Why do dominant personalities attain influence in face-to-face groups? The competence-signaling effects of trait dominance. Journal of Personality and Social Psychology.

• Arnsten, A. F. T. (2009). Stress signalling pathways that impair prefrontal cortex structure and function. Nature Reviews Neuroscience.

• Edmondson, A. C. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly.

• Kahneman, D. (2011). Thinking, Fast and Slow.

• Klein, G. (2007). Performing a project premortem. Harvard Business Review.

• Tetlock, P. E., & Gardner, D. (2015). Superforecasting: The Art and Science of Prediction.

Most leadership teams don’t have a decision problem.

They have a scoring problem.

And it’s quietly wrecking judgment.

The lie leaders tell themselves

“We reward good decisions.”

You don’t.

You reward whatever happened to work.

And in uncertain environments, outcomes are a noisy signal at best.

A strategy work, you praise.
The same strategy fails, you get out the scapel for a post-mortem.

Same thinking.
Different result.

Nothing changed except:

• Noise

• Uncertainty

• Context

Yet the verdict flips.

That’s not leadership.

That’s luck…with better branding.

You don’t remember the decision.
You remember the story you told once you knew how it ended.

The uncomfortable truth

If you evaluate decisions by results alone, you are training your team to chase luck.

Not judgment.

Not quality thinking.

Luck.

Over time, three shifts happen.

Quietly.

Systematically.

1. Risk gets hidden

People stop taking intelligent bets.

Not because they lack courage.

Because they understand how the game is actually scored.

Bad outcome = career risk.

So they:

• Delay decisions

• Over-consult

• Add another layer

• Default to consensus

You call it alignment.

They call it career preservation.

The story improves faster than the thinking ever did.

2. Thinking gets distorted

Teams don’t optimise for what was right.

They optimise for what sounds reasonable once the result is in.

So the story gets tidied.

The uncertainty quietly disappears.

The decision becomes “clear in hindsight.”

Of course it does.

You’ve sat in that meeting.

Everyone nods.

It sounds rational.

It wasn’t.

3. Learning breaks

If outcome = judgment, then failure = blame.

So what happens?

People rewrite history.

“We knew that would happen.”
“We should have seen it.”

No, you didn’t.

You just got a result and worked backwards.

And once that starts, learning is over.

Where this shows up (and no one calls it out)

You’ll hear it:

“Great call.”
“Poor decision.”

Usually said with complete confidence.

Based entirely on the result.

Not the process.

Not the information available at the time.

Not the constraints.

Just the outcome.

You’re not reviewing decisions.

You’re scoring the coin flip after it lands.

The part leaders don’t like hearing

Your environment is shaping this.

Not your people.

You’ve built a system where:

• Outcomes are visible
• Process is invisible
• Uncertainty is inconvenient

So people optimise for what’s measured.

That’s on you.

The question most teams avoid

Is it helping people do the right thing,
or just do things right?

Because under pressure, those diverge fast.

Doing things right is safe.

Doing the right thing is exposed.

One protects you.

The other tests you.

Most organisations say they want the second.

Their incentives quietly prefer the first.

What high-performing environments do differently

They separate decision quality from outcome quality.

Not as philosophy.

As discipline.

After any meaningful decision, they ask:

• What did we know at the time?

• Where were we guessing?

• What part of this outcome was noise?

• Would we make the same call again?

That last question is the test.

If the answer is yes, the decision stands.

Even if it failed.

If the answer is no, the thinking gets fixed.

Even if it worked.

No drama.

No theatre.

Just signal.

The provocation

If a decision in your team fails tomorrow:

Do you reward the quality of the thinking?

Or the comfort of the outcome?

Be honest.

Your answer tells you everything about the system you’ve built.

You don’t get the outcomes you celebrate.

You get the decisions you reinforce.

The mistake most teams don’t see

When a decision goes wrong, teams look at:

• The data

• The people

• The strategy

They rarely look at timing.

But timing shapes everything.

Same team. Same information.
Different moment in the day, different outcome.

Late afternoon.
Fatigue is up.
Control is down.
Reactivity is higher.

Yes. This is the right move.

You’re not adding theory.
You’re adding proof that this is real-world, not opinion.

Keep it tight. No citations in-text. No over-explaining.

Where to insert it

Right after:

Late afternoon.
Fatigue is up.
Control is down.
Reactivity is higher.

Final insert (in your voice)

Use this:

Late afternoon.
Fatigue is up.
Control is down.
Reactivity is higher.

Parole boards approve ~65% of cases early in a session.
Close to zero just before a break.

Executives make worse calls late in the week.
Doctors simplify decisions at the end of long shifts.

Same standards.
Different moment.

What you get isn’t poor intelligence.
You get compromised judgement.

Same standards.
Different moment.

What you get isn’t poor intelligence.
You get compromised judgement.

Most teams don’t design for this.
They just push through it.

Decision buffers: protecting thinking quality

The assumption in most environments:

Faster decisions = better performance

Faster decisions feel efficient.

They usually just compress thinking quality.

High-quality judgement isn’t constant.

It fluctuates with:

• Energy

• Emotional state

• Cognitive load

Ignore that, and speed becomes noise.

Decision buffers are simple constraints that protect against this.

Not complex frameworks.
Just rules.

For example:

• Sleep on high-stakes decisions

• No strategic discussions late in the day

• Delay responses to emotionally loaded inputs

These aren’t about slowing down.

They’re about placing decisions in the right conditions.

Because the same brain performs differently depending on when it’s used.

Stop rules: protecting against drift

Most teams don’t know when to stop.

So discussions drift.

Energy drops.
Ego rises.
Sunk cost creeps in.

And the illusion is:

“We’re still working on it, so it must be improving.”

In reality, decision quality peaked earlier.

Everything after that just feels like progress.

Stop rules solve this.

They create pre-committed exit points.

Before you enter the discussion, you define:

• When we stop debating
• When we assign ownership
• When we make the call

Examples:

• 30 minutes → assign a decision owner
• ~70% of data → commit
• Noticeable energy drop → pause and reset

Two things happen:

Emotional bias drops.
Cognitive capacity is preserved for what actually matters next.

Without stop rules, teams don’t optimise decisions.

They exhaust themselves making them.

Control: reducing cognitive load in the room

This is the one that gets missed.

Ambiguity around ownership creates invisible load.

If no one owns the decision:

• Everyone feels responsible

• No one feels accountable

This drives:

• Over-discussion

• Defensive thinking

• Social friction

And most importantly:

It reduces thinking quality.

Because attention splits.

Between solving the problem and managing the room.

Simple fixes:

• Clear decision owner

• Defined roles in the room

• Explicit boundaries: “this is not yours to solve”

Control isn’t about hierarchy.

It’s about removing unnecessary cognitive load.

And most teams underestimate how quickly load degrades judgement.

Why this matters more than most frameworks

There’s no shortage of decision-making models.

Most of them assume:

• Stable conditions

• Rational actors

• Consistent energy

Real environments don’t work like that.

They are:

• Time-pressured

• Emotionally loaded

• Cognitively constrained

So the question isn’t:

“What is the best decision framework?”

It’s:

“What conditions are we asking people to think inside?”

Because that determines the outcome.

Every time.

A simple way to apply this this week

Don’t roll out a system.

Just introduce one constraint.

Pick one:

• Add a buffer to one high-stakes decision

• Introduce a stop rule in one meeting

• Clarify ownership before discussion starts

Run it for a week.

Observe:

• Speed of decisions

• Quality of thinking

• Energy in the room

You don’t need a full redesign.

You need a constraint that shifts behaviour.

This week, a decision will go wrong.
Don’t start with who.
Start with when.