Your PowerPoint Is Logical. Your Organisation Is Not.

There is a small tragedy that plays out in meeting rooms every week.

A team builds a perfectly logical improvement plan. The problem is clear. The process has been mapped. The benefits have been quantified. The slides are elegant. The roadmap has phases, workstreams, milestones, governance forums, and just enough arrows to suggest momentum without alarming Finance.

Everyone agrees. Then almost nothing changes.

Or worse, things change briefly and then slowly return to normal, like a hotel towel that has been folded into a swan and then remembers it is a towel.

This is the great disappointment of business improvement: logic wins the meeting and loses the workplace. Not because people are stupid or lazy. But because human behaviour is not produced by logic alone. It is produced by threat, reward, identity, habit, bias, trust, attention, and the social cost of doing something different.

A PowerPoint can explain the future. It cannot make the nervous system feel safe. That distinction matters.

Because organisations are not process systems. They are human systems. And human systems do not change simply because the case for change is rational.

The Problem: We Design Improvement for Rational People Who Do Not Exist

In the previous articles, we looked at why organisations should not be treated as machines, why they behave more like cognitive systems, why empowerment needs guardrails, and why clarity must come before tools. This article goes one level deeper: if organisations are human systems, then improvement must account for how humans actually think, decide, avoid, copy, protect, and act under pressure.

This is where many improvement efforts go wrong. They are logically strong but psychologically weak. They assume people will adopt a better process because it is better. They assume behaviour follows instruction. It rarely does.

Under pressure, the brain is not a calm executive with a spreadsheet. It is a threat-detection machine wearing office clothes. If a new process feels risky, if a dashboard feels like surveillance, if a change threatens status, if a decision exposes someone to blame, or if the new way requires more mental effort than the old way, logic begins to lose its charm.

This is why so many technically sensible initiatives fail in strangely human ways. At CoEcosystem, we help organisations design improvement around how people actually think and behave, not how the slide deck hopes they will behave. Learn more at CoEcosystem’s website.

A Better Framework: The Human System Test

Before asking people to adopt a new process, tool, system, or way of working, leaders should test whether the human system is ready for it. The question is not, “Does this make sense?” The better question is, “Will this survive contact with the human brain?”

Explore the Human System Test in our community discussion.

1. Does This Feel Like Threat or Reward?

The brain pays close attention to threat. This is inconvenient for leaders, but excellent for survival. A change may be rationally positive and still feel threatening. It may threaten competence: “Will I look bad while learning this?”; status: “Will this reduce my influence?”; autonomy: “Am I losing control?”; certainty: “What happens if this goes wrong?”; or belonging: “Will my group approve of this?”

These reactions are invisible. No one writes “status threat” in the risk register. Instead, it appears as the famous corporate phrase, “We just need to think through the implications,” which sometimes means thoughtful governance and sometimes means the organisation has detected danger and is looking for a cave.

The lesson is simple: if the new behaviour feels punishing, exposing, embarrassing, or unsafe, people will avoid it even when they understand it. If it feels rewarding, useful, socially approved, and safe enough to try, adoption becomes much easier.

2. How Much Cognitive Load Are We Adding?

Cognitive load is the mental effort required to understand, decide, remember, interpret, and act. It is one of the most underappreciated costs in business.

Organisations are remarkably good at adding cognitive load while calling it improvement. A new system requires new fields. A new process requires new exceptions. A new dashboard requires new interpretation. A new governance model requires new meetings. A new methodology requires new language. Everyone receives training, which is the traditional business method of saying, “We have designed something difficult and now expect you to cope.”

The problem is that the human brain has limited working capacity. When people are overloaded, they do not become strategic. They become narrow, reactive, defensive, and attracted to shortcuts. They fall back on habit. They avoid ambiguity. They use the old spreadsheet because it is familiar, even if the new platform is technically better.

This is why adoption is often less about communication and more about friction. If the new way requires too much mental effort, people will not use it consistently. Not because they disagree. Because their brain has a limited budget, and the organisation has already spent most of it.

The useful question is: are we making the better action easier, or merely more correct?

3. What Identity Are We Asking People to Change?

Most change programs talk about behaviour. Fewer talk about identity. This is a mistake, because identity is often where resistance lives.

A senior expert may resist a new standard because it makes their hard-won judgment feel replaceable. A manager may resist empowerment because being the decision-maker is part of their status. A team may resist centralisation because local control is part of their pride. A professional may resist a new tool because it makes them feel like a beginner again.

When improvement threatens identity, logic alone is a weak instrument. You cannot spreadsheet someone out of feeling diminished.

This is why good change language matters. If a new system is framed as “removing manual work,” some people hear efficiency. Others hear redundancy. If a process standard is framed as “reducing variation,” some hear quality. Others hear, “Your local expertise is no longer trusted.” If AI is framed as “doing the thinking,” knowledge workers may quietly conclude that the organisation has misunderstood their value.

A better approach is to preserve dignity while changing behaviour. Show people what is still valued. Explain what human judgment is now needed for. Make the new identity attractive. The aim is to say, “Your expertise is being moved to higher-value work.”

That is not spin. It is behavioural design.

4. What Habit Are We Competing Against?

Old ways of working are not just processes. They are habits. And habits are powerful because they reduce effort. They allow people to act without thinking too much.

This is why a new process can be understood and still ignored. Understanding happens in the meeting. Habit happens on Tuesday at 4:48 pm when the customer is waiting, the system is slow, the manager is unavailable, and the old shortcut is sitting there like a biscuit.

The old habit has advantages. It is familiar, fast and has worked before. It may even be unofficially rewarded. The new behaviour, by contrast, is fragile. It requires memory, effort, confidence, and reinforcement.

So improvement must be designed as habit replacement, not information transfer. Otherwise, training becomes a pleasant cultural ritual in which everyone learns the new way and then returns to the old one with slightly more guilt.

Most improvement initiatives fail because they are designed for logic, not for people. Lasting change happens when we reduce threat, lower cognitive load, protect identity, and redesign the conditions that shape daily behaviour.

A Practical Example: The Knowledge Management Platform Nobody Fed

Imagine a professional services organisation that introduces a new knowledge management platform.

The business case is excellent. People are wasting time reinventing documents, searching old folders, and asking colleagues for templates. The new platform promises one source of truth. Better knowledge sharing. Faster onboarding. Less rework. More consistency.

It makes perfect sense.

And after six months, the platform is mostly empty.

The traditional diagnosis is predictable. “People need more training.” “Leaders need to reinforce usage.” “We need better compliance.” “We need to make uploading mandatory.”

Possibly. But the human-system diagnosis asks different questions.

Does uploading knowledge feel rewarding, or does it feel like unpaid clerical work? Are people afraid their material will be judged? Does sharing reduce their status because expertise is part of their value? Is the platform easy to use at the moment people finish the work, or does it require extra effort later? Are teams praised for contributing reusable knowledge, or only for delivering client work under pressure? Does the system make people look generous and competent, or exposed and replaceable?

Suddenly, the problem is not a knowledge platform problem. It is a reward, identity, habit, and cognitive load problem.

The solution may be surprisingly different. Make contribution part of project closure. Create simple templates. Let experts attach their name and reputation to useful material. Make the platform easier than asking around. Build a ritual where teams share “one thing worth reusing” every fortnight.

One approach mandates uploading.

The other makes sharing feel useful, visible, safe, and worth repeating.

See how we teach this approach inside the CoEcosystem Academy.

The Real Shift

The next generation of improvement leaders will not be satisfied with process logic alone. They will understand that every business improvement initiative is also a psychological event.

A new dashboard changes what people think will be noticed. A new workflow changes where people feel control. A new standard changes what local expertise means. A new AI tool changes how people understand their value. A new operating model changes status, identity, and social rules.

This does not make improvement soft. It makes it accurate.

Human behaviour is not an annoying obstacle to business improvement. It is the medium through which business improvement happens. Ignore it, and the best-designed process becomes a museum exhibit. Understand it, and even modest changes can produce disproportionate results.

Knowledge workers often fail to act as the PowerPoint suggests because the PowerPoint does not experience pressure, politics, fatigue, status anxiety, competing priorities, or the small daily gravitational pull of habit. People do.

That is why improvement must be designed for humans under real conditions, not ideal employees in theoretical workshops.

Because in the end, the organisation does not change when the slide is approved. It changes when the nervous system decides the new behaviour is safe enough, easy enough, valuable enough, and repeated enough to become the new normal

Further Reading

If this idea resonates with you, these books are useful companions for going deeper.

1. Your Brain at Work, David Rock. A practical book on how the brain handles focus, threat, overwhelm, insight, and social situations at work. It is useful for understanding why cognitive load and perceived threat can quietly undermine performance and change adoption.

2. The Righteous Mind, Jonathan Haidt: A powerful exploration of moral psychology and why people often reason after they intuit. It helps explain why logical arguments alone rarely move people when identity, loyalty, fairness, or group belonging are involved.

3. Switch, Chip Heath and Dan Heath. A highly practical book on behaviour change. Its rider, elephant, and path metaphor is especially useful for leaders trying to combine rational direction, emotional motivation, and environmental design.

4. Tiny Habits, BJ Fogg. A practical guide to habit formation. It reinforces the idea that behaviour change depends on making actions small, easy, triggered, and rewarding rather than relying on motivation alone.

5. The Progress Principle, Teresa Amabile and Steven Kramer. A useful book on motivation and meaningful work. It shows how small wins and a sense of progress can have a powerful effect on engagement, creativity, and persistence.

6. Noise, Daniel Kahneman, Olivier Sibony, and Cass R. Sunstein. A useful companion for understanding inconsistency in human judgment. It is relevant for organisations trying to improve decision quality in systems where people interpret similar situations differently.

Discussion Question

Where is your organisation currently relying on logic, training, or communication when the real barrier may be threat, cognitive load, identity, or habit?