WHAT THEY HAD ALREADY BOUGHT

Over three years, the company spent €2.4 million trying to fix its culture. Agencies. Diagnostics. Organisational psychologists. Engagement platforms. Leadership programmes. New behaviours, written, tested and rewritten. Change campaigns with a name and a launch film.

None of it was bad work. The suppliers were good, the sequencing was sensible, and the story of who the company wanted to be was told at every all-hands and printed on every wall. People nodded. People meant it.

Performance kept softening anyway. Customers kept leaving.

By the time we spoke, the company had an internal explanation for that, and everybody more or less believed it. The market had got harder. The organisation was too big to turn quickly. People were resistant to change. All plausible, all partly true, and none of it had produced a single week of movement.

THE QUESTION UNDERNEATH THE QUESTION  

They came with a clear brief: how do we change employee behaviour?

That is a reasonable question and an expensive one, because it sends you shopping. Once we peeled it back, the question they actually needed answering was simpler and much closer to the P&L: how do we return the business to positive growth and stop customers leaving?

So we mapped what was in the way. Everything, without ranking it, without arguing about it, and without anyone defending their function. Twenty-nine possible blockers went up: pricing, structure, technology, competitors, market conditions, and twenty-four more of the same kind. Some were real. Some were inherited grievances. All of them were things the leadership team could name.

THE MISSING WORD

Reading the list back, one thing was obvious the moment you stopped looking for it.

The word "customer" did not appear once.

Twenty-nine blockers in a business that exists to serve consumers, and the consumer was in none of them. Not in the strategy language, not in the meeting agendas, not in the dashboards that decided what people worried about on a Monday morning. A B2C business had quietly written its own customer out of its operating system, and it had taken years to do it.

When we put that to the team, the answer came back instantly, with no hesitation at all.

"Well, of course we did. It's implied."

That confidence is the interesting part. Nobody in that business had ever decided to deprioritise the customer. There was no meeting, no memo, no vote. An organisation of eight thousand people had made a decision that no individual in it had made, and then produced a reason for it on the spot that everyone found satisfying.

WHY NOBODY HAD SEEN IT  

This is the part worth slowing down on, because it is the part that repeats everywhere.

Organisations behave as though they have a mind of their own. They develop preferences, blind spots, taboos and reflexes that outlive the people who created them, and they defend those reflexes with real conviction. That is not a metaphor SSC invented to sell sessions. It has been documented for fifty years, and it holds up.

• People do not have reliable access to why they do what they do. In 1977, Richard Nisbett and Timothy Wilson published the study that made this uncomfortable for everyone. Across a run of experiments, people confidently reported the reasons for their own choices, and those reports were often demonstrably wrong. What the mind produces on demand is a plausible account, not an accurate one. "It's implied" is that mechanism working exactly as designed.

• Organisations protect the very thing that is hurting them. Chris Argyris spent a career on what he called organisational defensive routines: the practices that stop embarrassment or threat from surfacing, and which cannot themselves be discussed. The undiscussable becomes undiscussable, and then the fact that it is undiscussable becomes undiscussable too. Argyris also found, awkwardly, that the smartest and most successful professionals are often the worst at this, because they have rarely failed at anything and so have never had to examine how they think.

• Culture lives below the level anyone can report on. Edgar Schein's model puts the artefacts on top, the values you can say out loud in the middle, and underneath both, the assumptions that have stopped being visible precisely because they work. You cannot survey your way to that layer. You are asking people about water they are swimming in.

• Structure produces behaviour. Donella Meadows put it plainly: systems cause their own behaviour. Change the people and keep the structure, and the same pattern reappears in different faces within a year. Which is why the €2.4 million kept buying real change that failed to hold.

Put those four together and the case stops being a story about one telecoms business. Every organisation is running assumptions nobody chose, defended by explanations nobody has tested, generated by a structure nobody designed. The bigger you get, the more of them you accumulate. The more successful you are, the less anyone is incentivised to say so out loud.

WHAT CHANGED 

The exclusion had been invisible. Once it was visible, it became optional.

Within weeks, customer language was back in leadership meetings, in strategy documents, and in the dashboards. The insight moved from one executive to the whole leadership team, and the next CEO address turned on a single word. Not a programme, not a relaunch, not a new set of behaviours. One word that everyone had assumed was already there.

The €2.4 million was not the problem. Nothing they had bought was designed to find something that nobody could see and everybody could explain. The block came off, and the work they had already paid for started doing what it was supposed to do.

WHAT THIS CASE DOES NOT PROVE

Worth saying plainly, because you will read plenty of case studies that do not.

This is one engagement, written up by us, with the changes reported by the client rather than measured against a baseline we set beforehand. It is a strong story and it is not a dataset. The client is available to speak to anyone considering this seriously, which is the only real verification a single case can offer.

Every SSC engagement now runs on measurement taken before the session and again at two, six and twelve months, so the next generation of these write-ups will carry numbers we did not choose after the fact.

IF YOU RUN SIXTY PEOPLE, NOT EIGHT THOUSAND

The scale is the least transferable thing here. The mechanism is the point.

You do not need three years and €2.4 million to write something essential out of your business. A scale-up does it faster, because the assumptions that got you from five people to fifty are laid down under pressure and then never revisited. The thing that made the company work at one size quietly becomes the thing holding it at the next. The founder who had to check everything. The customer promise that made sense when there were nine customers. The senior hire everyone works around rather than talks to.

The Startup Genome research on premature scaling, based on around 3,200 high-growth tech startups, found that roughly three quarters of them failed by scaling something before it was ready. The same study found that founder experience, education, age and country of origin had no bearing on whether a company failed. It is fifteen years old and drawn from tech startups rather than scale-ups generally, so treat it as a signal rather than a proof. The signal is this: the failure is structural, and it is not a competence problem.

Which is good news, if you can find the structure.

Ask your leadership team what is in the way of the number you need to hit. Write down everything they say. Then read the list back and look for what is not on it.

That absence is usually the expensive one.