Blog

aleksandra-mazur-80011.jpg

Why mind-based approaches are
not enough

 

Most development work in organisations still assumes a simple model: if people understand something clearly enough, they will do it differently.

As a result, we design for insight. We build programmes around mindset, reflection, behavioural frameworks, and structured models of change. We help people articulate what “good” looks like and why it matters. And yet, the transfer into real-world behaviour often remains inconsistent. This isn’t because people lack understanding. It’s because understanding alone is not sufficient in the moments where behaviour actually needs to change.

The real test of development is under pressure

In calm reflection, most people can access new perspectives quite easily. They can identify better choices, rehearse different responses, and commit to new behaviours. The challenge is that workplace behaviour rarely happens in reflective conditions.

It happens in:

  • difficult conversations

  • performance pressure

  • time constraints

  • status dynamics

  • emotional activation

In those moments, people don’t primarily operate from insight. They operate from state. And state is not something you can think your way out of in real time.

Why the “knowing–doing” gap persists

The familiar gap between knowing what to do and actually doing it is often framed as a motivation or accountability issue. But in practice, it is frequently a capacity under load issue.

When pressure rises, the nervous system shifts into protective patterns. Attention narrows. Cognitive flexibility reduces. Familiar responses become more dominant. This is not a failure of will. It is how human systems are designed to function under stress. This means that adding more conceptual clarity doesn’t necessarily change outcomes in the moments that matter most.

Where mind-based approaches reach their limit

Cognitive and behavioural models absolutely have value. They help people name patterns, reflect more effectively, and design better strategies.

But they tend to operate at the level of:

  • interpretation

  • intention

  • planning

The limitation appears when we assume that this level directly determines real-time behaviour in complex environments. Because behaviour is not only generated by thought. It is also generated by physiological state, emotional arousal, and embodied habit. In other words: people don’t just execute decisions. They enact states.

What a more embodied approach adds

An embodied approach doesn’t replace cognitive learning. It completes it. It shifts attention toward what is happening in the system while behaviour is forming, not just after it has occurred.

In practice, that means development work also pays attention to:

  • how people shift under interpersonal pressure

  • what happens in the body during feedback or challenge

  • how quickly someone moves into contraction, control, or withdrawal

  • whether they can stay present when discomfort arises

These are not “soft” factors. They are the conditions under which all behaviour is produced.

Implications for L&D and coaching practice

If we take this seriously, it changes what we think we are developing. We are not only building insight or capability in the abstract.

We are also building:

  • capacity to stay present under pressure

  • flexibility of response in real time

  • tolerance for discomfort without shutdown or over-control

  • awareness of internal state as it shifts

This moves development from purely cognitive change into capacity-building in context.

A useful question

Alongside “What should people do differently?” it can be useful to ask:

“What happens in people under pressure that makes the desired behaviour harder to access?”

That question often leads somewhere more practical than additional models or frameworks. It leads into how behaviour is actually generated in the moment.

Closing

If we want development to translate more reliably into behaviour, we need to work with the full system that produces behaviour — not just the thinking layer. That means taking cognition seriously, but not exclusively. Because in real organisational life, people don’t behave from understanding alone. They behave from the state they are in when it matters.

 

Let’s start a conversation…