Thirty years inside
the same missing layer.
The infrastructure that C-Coach provides was not designed at a desk. It was built because nothing that already existed did what was needed.
Where the instinct came from.
I grew up in a working class family. From an early age that meant getting involved. Helping in my dad's business, building, fixing, learning how things worked by working on them alongside him.
The instinct to look at a system, understand its components, and find what is missing when it fails has never left me.
My first work outside the family was split between a bank and a residential blind college. The college stays with me.
The young people there could not do things for themselves. Not because of their impairment. Because from birth, everything had been done for them. They arrived without the capacity for independence, and the thing that had taken it from them was the very support that was supposed to help.
The distinction between doing something for someone and building their capacity to do it themselves has sat at the centre of everything built since.
The same absence.
Every time.
The career that followed took me inside large organisations across financial services and insurance. Some of them had significant HR functions. Real investment. Real resource. Real intent.
In every one of them, the same thing was missing.
There was always a complete framework for the technical side of the work. Processes, compliance, product knowledge, structured inductions. People knew what they needed to do.
What was absent was any framework for how they did it. How they communicated. How they built relationships. How they performed under pressure, navigated difficulty, and converted capability into output. That layer had no structure, no measurement, and no permanent infrastructure behind it.
More pressure on a system
that needed something fixed.
When performance fell short, the answer was always the same. Push harder. Set higher expectations. Ask more of people who were already giving what they had.
Think about driving a car with a badly inflated tyre. Driving faster does not solve it. It destroys the tyre. It puts pressure on the suspension. It burns more fuel.
One element that is not where it needs to be puts strain on every other part of the system. Eventually it is not just the tyre that goes. It is everything that ran through it.
That is what I watched happening to people. The structural layer was absent. Nobody named it. So organisations did the only thing available to them: they asked for more effort from a system that needed something fixed, not something harder.
Looking for something
that would reach it.
I went looking for something that would address the structural layer properly. I used what existed. Training programmes, leadership workshops, coaching interventions, engagement initiatives.
I leaned into them fully, inside organisations that had the resource to deploy them properly.
None of them reached it. They addressed the symptoms with genuine care. The cause stayed untouched.
The infrastructure I needed did not exist. So I built it.
Built empirically.
Proven in practice.
What became C-Coach was not designed at a desk. It was built inside real organisations, through years of application, observation, and honest assessment of what worked and what did not.
Understanding how people actually change. How behaviour shifts, what conditions it requires, what causes it to revert. How that process works at the individual level, through the manager, and across an organisation simultaneously.
Every element of the infrastructure exists because of what that process revealed. The framework, the sequence, the measurement, the manager layer: all of it designed around one question.
How do you equip people to change, sustainably, at scale?
That understanding was later subjected to formal neuroscientific and psychological review, drawing on published research across both disciplines, to ground what practice had shown in the science of how human behaviour actually works.
Infrastructure that stays.
Results that are real.
C-Coach is not a programme with a delivery date and an exit. It is infrastructure that stays, measures, and is accountable for the results it produces.
Performance and wellbeing are not competing priorities. They are two consequences of one structural cause being addressed. When the infrastructure is in place, both move.
If you want to understand what that means for your organisation, the starting conversation is the right first step.
The first conversation is focused, specific, and worthwhile.
It is not a sales call. It is a structured conversation about whether C-Coach is the right fit for your organisation and what that would mean in practice.
Start a conversation →