Leadership Frameworks Under Load

Real Leadership in the Field Series

I have read the books, and took the classes. I have taken their frameworks into factories, startups, and small teams that were already under load. They usually make sense at first. The analogy lands. The steps feel reasonable. Everyone nods.

Then you try to run them in the real world.

Parts of them work. You see improvement. The work feels focused and intentional.

Then you realize something uncomfortable about where the improvement is actually coming from.

The parts that worked were things you already knew. The framework did not teach you how to run your operation better. It gave you permission to focus and a story to tell. The clever metaphors dissolve into fundamentals you recognized long before the book.

The more detailed the guidance becomes, the less it fits the conditions we are operating in. No spare time. No extra people. No clean handoffs. No ability to pause the system and implement.

You strip away process. You ignore steps. You keep only the parts that survive contact with reality and drop the rest.

What is left looks suspiciously like what you already knew.

A concrete example: Switch by Dan Heath

I took that book into a factory during a ramp up phase. The core metaphor is solid. The rider does not control the elephant. Behavior changes when you shape the path, not when you argue with people. That part is true.

I did not come to this unprepared. I had been with the operation since startup. I knew the process, the people, and the constraints. I had been leading teams for decades across multiple manufacturing environments.

I took the framework seriously. I tried to apply it faithfully.

Context matters here. We were running extruded rubber compound. Four different compound materials, over 100 different shapes, lengths, and contours. Each of the compounds behaved very differently. The extruded material was then rolled up and stored for curing later in giant molds. We were still learning what good looked like while maintaining production.

The book lays out a clear framework:

Direct the Rider

This is about clarity and focus.

1. Find the bright spots → Look for where the change is already working and do more of that, instead of obsessing over what is broken.

2. Script the critical moves → Do not tell people to “be better” or “be more strategic.” Tell them exactly what to do differently, step by step.

3. Point to the destination → Make the goal concrete and visible so people know what “better” actually looks like.

Motivate the Elephant

This is about emotion and energy.

1. Find the feeling → Facts are not enough. People move when they feel something, not when they understand something.

2. Shrink the change → Break the change into small, doable steps so it does not feel overwhelming.

3. Grow your people → Frame the change as an identity shift. “We are the kind of people who do X.”

Shape the Path

This is where environment and systems come in.

1. Tweak the environment → Change the surroundings so the right behavior is easier and the wrong behavior is harder.

2. Build habits → Reduce the need for constant decision-making by turning behaviors into routines.

3. Rally the herd → Use social norms. People follow what they see others doing.

Reasonable on paper. We tried them under load.

What actually happened

Find the bright spots → Yes, find where it is working and do more of that. This was data gathering. We found pockets where runs worked and where they did not. Some operators performed better. Some compounds behaved more predictably. We trained and rotated accordingly. Incoming material quality was outside our control, so gains were partial.

Script the critical moves → A strong idea in theory. In practice, we did not yet know what the critical moves were. We had to discover them under load. That took time, so early gains were limited.

Point to the destination → Yes. The goal was concrete and visible. We tracked variation and met on it weekly. This part mattered. It gave everyone shared understanding of where problems were. It allowed faster response when variation spiked. It built collective knowledge about patterns.

Find the feeling → Under real pressure, emotion followed results. On good days morale rose. On bad days it dropped. The framework did not change that dynamic.

Shrink the change → Yes, this one worked. We took an “eat the elephant one bite at a time” approach. This fit with how the system actually learned. These were small incremental changes that we came up with together as a team from our feedback loops.

Grow your people → Yes, this was the main part of the strategy in shrinking the change. It had little impact on its own. It was supportive, not transformative. I do believe over time this investment had real potential. It was always offset with turnover and relearning.

Tweak the environment → We praised operators when their inputs were on target and corrected when they were not. We did this weekly. We had no reliable way to measure the impact. Even so, I still believe this mattered.

Build habits → We gave operators more authority to stop running something that was not working. On paper this is seductive. Giving authority back to the operators is a big deal. You have to run the product though. You can shut it down for a shift and try later, but you cannot just not do it. So this became more of a moral victory over time as it does give them some control back.

Rally the herd → We shared what was working and by whom. This is where attention alone can temporarily lift performance.

Some of these we could not measure directly. All in all we increased about 15%, which is a great improvement. I consider that a win.

At the end of it, the gains we saw came from things we already understood before we opened the book.

Gather data. Address variation. Share information. Change one thing and watch what moves. Repeat what works.

We did not need a framework to know this. We needed time, attention, and enough capacity to sustain the changes once they started to work. That was the real constraint.

So where the framework made a difference was not what it taught us, because frankly it did not teach us how to run our operation any better. What it did was give us some motivation to move and a story to sell. My director used it to explain what we were doing to management. It landed extremely well at that level. Several people there were familiar with the book and the story resonated. The framework translated our work into language leadership already trusted. It did not change what we were doing on the floor. It changed how that work was understood above us. It gave legitimacy to work that otherwise might have looked like basic process improvement. The framework was not magic, and it could not get past the limitations we had. The incoming material variation, the turnover of operators, the overtime needed to compensate → none of that changed.

We could have improved more. Maybe twenty five percent if a real professional who does this for a living came in and pushed hard. This was one department out of five. All of them needed attention. We were still coming out of a startup phase. I was managing the team and running the factory because there was no one else with the capacity to do it.

This is the part leadership writing skips.

Insight does not change systems. Sustaining power does.

Consultants can create motion by temporarily adding capacity and focusing attention. That extra ten percent looks real.

None of it works without operator buy-in.

Then they leave.

Six months later, I doubt that a top consultant would have done better than what we achieved on our own. Not because we were exceptional. The system still lacked the capacity to hold the change beyond the 15% we reached. No extra headcount. No slack. No redundancy. No room to absorb mistakes. That temporary boost fades. A year later we were still hovering around the 10 to 15% level. It never got higher until we started investing some real money here.

The constraint was not clarity. It was capacity. We were learning while shipping, with no slack in the system. That limited how much change we could absorb and sustain.

Performance rises when attention rises, then drifts back when attention normalizes.

Leadership advice works best at the moment it is introduced and falls back quietly later. Without significant structural change, systems return to baseline. The advice assumes a world where you can pause, plan, and roll out. Small teams do not live there. They learn under load, adapt while shipping, and cut process to survive.

When you strip away the theater, what remains is basic system work done patiently over time.

It is not glamorous. It does not scale neatly.

It endures.

I really like the book Switch. I like the Heath brothers and their work. I recommend you read it. Just understand that the real magic is not in the clever metaphors or the nine-step framework. The real magic is in the fundamentals underneath it all.

Small teams do not struggle because they lack insight. They struggle because they lack slack.

Without structural change, systems return to baseline. Not because the advice was wrong, but because the system cannot hold the gain.

Frameworks can create motion. Capacity determines durability.