A mid-sized site. A nice place to work. Friendly.

But under the surface, some people felt squeezed.

Things were normally steady. Whenever something slipped, the pattern was familiar:

“Fred will fix it — he always does.” Fred was the company guy who stayed late, popped in at weekends, and quietly held things together. A bit of overtime here, a heroic push there, and the site reset just enough to survive the next Ops meeting.

The work got done.

Dashboards stayed yellow or green.

Any reds came with believable reasons — often true enough not to challenge.

On the surface the site looked stable.

Under the surface, margins were tightening. People complained that things were getting harder:

“We’re seeing more issues… I thought we fixed that… I need to stay late again… It used to be better… Maybe we need more staff… I’m not sure I can keep doing this… People are making more mistakes… Some always get away with it.”

The stability wasn’t structural — it was compensated.

The systems underneath were inconsistent, undocumented in places, and dependent on people remembering how things worked rather than the organisation defining how things worked. Leaders tolerated small deviations because the heroes — the people who always worked longer to fix things — absorbed them.

Over time, what should have been systemic signals were masked by individual effort.
Minor issues didn’t escalate.
Workarounds accumulated quietly.

The site had become efficient at coping, not consistent at performing.

It wasn’t getting better, but some people were working ever harder to try to push.

They felt stuck.

This is the risk of hero culture:

the better the people are, the less visible the system becomes.
When customer demand increased sharply — higher volume, tighter deadlines, more variation — the operation tipped.

The heroes who had been compensating could no longer keep pace. Firefighting became constant.

“Go and see Fred, he’ll sort it” stopped working. Fred was exhausted.

Fred would normally go to Bob, but Bob was off sick. The informal support structure collapsed within days.

Leaders spent their time recovering yesterday’s issues instead of controlling today’s work. Protected underperformance — people not keeping up, making repeated mistakes, delivering poorly but never being managed — suddenly became highly visible. Drift accelerated. Standards softened. Managers became more reluctant to challenge or ask critical questions; they didn’t want to demotivate people who already looked drained.

So more and more slid.
Issues increased.

Actions stopped closing.

Meetings became tense excuse sessions, longer and less productive, until someone senior finally said, “There are too many meetings — you’re falling behind — stop them,” removing what little structure was left.

The site didn’t fail dramatically; it simply lost the ability to control the work.

Pressure didn’t break the system — it revealed that the system had been broken for a long time.

GLM entered at this point — not with more KPIs, motivation, or “push harder” messaging, but by stabilising the operation so leaders could think again. The first priority was Visible Calm: reducing noise, clarifying the immediate plan, and creating headspace to lead.

Next, GLM rebuilt system integrity: roles clarified, routines standardised, and load rebalanced so the operation no longer relied on a handful of high performers. Leaders regained authority by holding expectations consistently, not selectively. Protected performance was addressed fairly, removing the silent weight carried by strong performers. Critical questioning became safe again.

Finally, GLM redesigned key processes using BIND — Behaviourally Intuitive (By) Design. Instead of more rules or more training, the system was reshaped so the right behaviour became the easiest behaviour — even when tired, stressed, or under pressure. Friction dropped. Drift slowed. Escalations rose (a healthy signal). The site became more resilient and more scalable.

When the next demand spike arrived, the operation didn’t wobble.

It held — because the system, not the heroes, was doing the work.