When Lean runs out of steam in a company, the tools are rarely the reason. The reason is behaviour, and above all management's behaviour, which is what both the research and decades of practice point to with remarkable consistency. This article gathers what the literature says about the management patterns that carry an improvement culture beyond its first six months.
Culture follows behaviour, not posters
The most widespread mistake is to believe that culture is changed with value words on the wall, a kick-off and a poster in the canteen. The single best source for the opposite is John Shook, industrial anthropologist and former Toyota manager, in his award-winning article "How to Change a Culture: Lessons from NUMMI" (MIT Sloan Management Review, 2010).
Shook was there when Toyota and General Motors reopened GM's closed plant in Fremont, California, in 1984 as the joint venture NUMMI. Before it closed in 1982 the plant had been one of GM's worst, known for absenteeism, conflict and dismal quality. Within a few years the same plant, staffed with essentially the same workforce, was among the best in North America. The workforce was essentially unchanged; what had changed was the system around it and the way the managers behaved.
Shook's conclusion is simple and counter-intuitive: you don't change culture by first changing how people think. You begin by changing what people do, that is, defining the desired behaviour, making it easy to perform and reinforcing it consistently. The culture follows after. It aligns with organisational psychologist Edgar Schein's classic model, which Shook himself refers to: culture is changed through visible actions and routines, not through appeals to values.
For an owner-manager the point is usefully concrete: there is no need to wait for the culture to be ready. What is needed is to define a few actions and then hold firm on them.
Why improvements crumble, and why it's rarely the employees
When an improvement doesn't hold, it's tempting to point at a lack of engagement among the employees. The research points elsewhere.
Nelson Repenning and John Sterman of MIT described, in "Nobody Ever Gets Credit for Fixing Problems That Never Happened" (California Management Review, 2001), what they call the improvement paradox: many companies invest in improvement programmes, but few create lasting results. The cause lies in how the new routines interact with the organisation's existing structure and incentives, rather than in the chosen tools.
They named the mechanism the capability trap: the more pressure rises, the more the organisation falls back on "working harder" rather than "working smarter". Firefighting becomes the norm, and here is the decisive part: the company comes to reward the firefighting. The one who, through a heroic effort, rescues a late order becomes the hero. The one who quietly built a routine so the fire never arose is not seen. Over time the "firefighters" get promoted, and the organisation learns that prevention doesn't pay.
What this describes is not lazy employees but a system that rewards the wrong behaviour. The quality pioneer W. Edwards Deming said it already in Out of the Crisis (1986): the vast majority of problems, which he put at around 94 per cent, stem from the system, and the system is management's responsibility. Employees essentially do what the system makes possible and rewards.
That is why we at Prozanta work from the premise that operational problems are usually behavioural problems, and that the system shapes the behaviour. If the improvement is to hold, you have to change what is rewarded, not scold those who respond sensibly to it.
The management patterns that carry an improvement culture
If management's behaviour is the decisive variable, which behaviour is at issue? The literature from Shook through Jeffrey Liker and Gary Convis (The Toyota Way to Lean Leadership, 2011) to Mike Rother (Toyota Kata, 2009) points to a few patterns that recur. Rother's concept of the coaching kata captures the core: the leader's role is not to deliver the answers, but to ask, every day, the questions that build the problem-solving capability of the employees.
In practice, the load-bearing patterns look like this:
- •Be present at the board meetings, both physically and mentally. A quick glance through the door will not do. What the leader spends time on tells the organisation what matters.
- •Ask open questions rather than dictating solutions. When the leader delivers the answer, the learning stops. Daily Management only works once the team owns the problem.
- •Treat deviations as learning, not blame. As Shook describes it from Toyota: a problem that becomes visible is a gift, not an accusation. Blame teaches people to hide problems; curiosity teaches them to solve them.
- •Follow up every time on what was agreed last time. Missing follow-up is the most frequent reason a good routine quietly dies.
The patterns sound simple, and they are simple to describe. The difficult part is doing them consistently, including on the days when operations are on fire. That is where most fall away, and where the difference is settled between an improvement that holds and one that quietly disappears.
What you can do tomorrow
The research only becomes valuable when it turns into action. Four concrete steps:
✓Four concrete steps
- →Assess your own behaviour honestly. How often do the board meetings get skipped when things are busy? The answer says more about your improvement culture than any strategy.
- →Choose one behaviour to change, and hold firm on it until it sticks. Experience says that one change carried through moves more than ten that are merely started.
- →Ask the managers closest to operations what they actually experience. They know better than anyone where the system rewards firefighting over prevention.
- →Make the change visible. If management changes its behaviour somewhere the rest of the building can see it, the rest of the building follows; if it happens behind a closed door, nothing happens at all.
An improvement culture does not arise from value words on a wall. It is built up or broken down by what management does day after day, and that work is as undramatic as it is decisive. It is the reason we stay in operations until the new behaviour is anchored, not just until the presentation has been delivered.
To read on about why improvements don't hold, you'll find our review here: Why Lean implementations often fail.
Sources
- Shook, J. (2010). How to Change a Culture: Lessons from NUMMI. MIT Sloan Management Review, 51(2). (Winner of the Richard Beckhard Memorial Prize.)
- Repenning, N. P. & Sterman, J. D. (2001). Nobody Ever Gets Credit for Fixing Problems That Never Happened. California Management Review, 43(4), 64–88.
- Schein, E. H. (2010). Organizational Culture and Leadership (4th ed.). Jossey-Bass. — see also MIT Sloan School of Management.
- Liker, J. & Convis, G. (2011). The Toyota Way to Lean Leadership. McGraw-Hill. — elaborated at Lean Enterprise Institute.
- Rother, M. (2009). Toyota Kata. McGraw-Hill.
- Deming, W. E. (1986). Out of the Crisis. MIT Press. — see The W. Edwards Deming Institute.
The references show the professional basis. Sources are reproduced in their original language.
