Firefighting Kata

27 months ago I wrote a piece about a “firefighting culture” where I described the actual process used to fight fires – following PDCA.

I have learned a few things since then, and I want to tighten my analogy a bit.

What is the core thinking behind true firefighting? This is actually closer to home than you may think. Many companies have situations that are on fire – in that they are destructively out of control.

I recall Mr. Iwata lecturing a group of managers in a large aerospace company in Seattle. He listened patiently to their grand plans about how the transformed operation would look. Then his remarks cut to the chase.

“Your house is on fire. This is not the time to be thinking about how you will decorate it.”

The question is – does urgency force a change in the thinking or approach?

I say it does not. However urgency does stress people’s skills and capabilities to deal with the situation to the limit – and beyond. Thus, it is best if those skills are thoroughly developed before there is a crisis, when the stakes are not so high. This is how high-risk professions train. They work to develop ingrained habits and skills for handling chaos before it is real.

So let’s go to our hypothetical burning building and look at what happens – as a matter of routine – even though every situation is different.

The target condition is a generally a given: The fire is extinguished, things are cooled down enough that there will be no re-ignition.

What is the current condition? Yes, the building is on fire. (doh!) But there is more to it than that.

What is stopping us from putting this fire out right now?

What is the layout of the building? Its construction? Where are the air shafts, sources of fuel, oxygen? Are there hazards in the building? Is there a basement under the main floor? Is there anyone inside?

Because they are (hopefully) skilled and practiced, gaining this information is routine, and hopefully they are getting most of it on the way.

The fire chief on site is going to develop an overall strategy for attacking the fire, and deploy his forces accordingly.

One thing they do not do – they don’t go creating action item lists, they don’t go hunting for fires, and they don’t just go into reaction mode.

Neither do they have a detailed “action plan” that they can blindly follow. Simply put, they are in an vague situation with many things that are still not known. These things will only be revealed as they progress.

What is the first problem?

The initial actions will be more or less routine things that help the effort, and gain more information. They are going to ventilate the roof to clear smoke, and they are going to first work to rescue any people who are trapped.

This is their initial tactical target condition.

As they move toward that target, they will simultaneously gain more knowledge about the situation, decide the next objective, and the actions required to achieve it.

Cycle PDCA

As they carry out those actions, either things will work as predicted, and the objective will be achieved or (more likely) there will be surprises. Those surprises are not failures, rather they are additional information, things that were not previously understood.

Because this is dangerous work, if things get totally strange, they are going to back-out and reassess, and possibly start over.

As they go, they will work methodically but quickly, step by step, never leaving fire (unsolved problems) behind them, always having an escape path.

And, at some point along the way, what must be done to accomplish the original objective, put out the last of the fire will be come apparent.

Why are they so good at this?

Simple. They practice these things all of the time, under constant critical eyes of trainers. Every error and mistake is called out, corrected, and the action is repeated until they routinely get it right. Even though they are very good at what they do, they know two things:

  1. They can get better.
  2. Their skills are perishable.

So, although each fire is different, they have kata that they practice, continuously – from basic drills to training in more complex scenarios. They are putting these things to use now that there is real urgency.

What about the rest of us?

In business, we tend to assume that crisis will either not occur, or when it does will be within our domain of being able to handle it… but we often get surprised and our problem solving skills are stretched to the breaking point.

Why?

Because we have never really practiced those skills, and if we have, we have not been critical enough of how we went about solving routine problems, and we are sloppy.

When there is no urgency, we can get away with being sloppy. When method is not critical, anything more or less works. But when things are complicated, messy, and right now, there isn’t time to practice. “You go to war with what you’ve got.” What that really means is that, however ill-prepared you are, you now have to deal with reality.

Problem solving is as important to a business (and I include any human enterprise, profit or not in this) as it is to the firefighters. Business has technical skills, as firefighters have handling hoses, operating their equipment, etc. But no matter how competent firefighters are at their technical tools, they are lousy firefighters if they have not practiced quickly solving problems related to putting out fires.

Likewise, no matter how good you are at keeping your books straight, managing your order base, scheduling production, whatever routine things you do, if you have not practiced problem solving skills on a daily basis, you are likely not very good at it. Daily kaizen is practice solving problems. The side-benefit is your business gets better as a result.

The difference is that firefighters know it is important, so they practice, subject themselves to the critical eye of professional trainers and coaches. In business, nobody teaches “problem solving” except in the most vague way.

 

“All we do is fight fires.”

Hopefully you wish you were that good.

Toyota Kata: Avoid Pareto Paralysis

A great key point comes out on page 124 of Toyota Kata by Mike Rother.

…a Toyota person once told me to focus on the biggest problem. However, when I tried to do this I noticed a negative effect: We got lost in hunting for and discussing what was the biggest problem. When we tried gathering data and making Pareto charts, it took a lot of time and the biggest problem in the Pareto chart was usually “other” which put us back into debating options. By the time we decided what the biggest problem was, the situation at the process had changed. This effect is called Pareto paralysis, and I encourage you to avoid it. Pareto paralysis delays your progress as people try to determine the “right” first step to take.

[…] it matters more that you take the first step than what the first step is.

I have seen this many times with my own eyes. It is a common problem when “problem solving” is taught as “application of the seven tools” and “correct” use of the tools becomes more important than understanding the problem or making actual progress.

Hirano, I believe, has been quoted as saying:

Waste often comes disguised as useful work.

That is what is happening here. The team thinks they are working to solve the problem when, in reality, they are still trying to decide what problem to work on. The gridlock may be driven by fear of working on the wrong problem. But in reality, there is no wrong problem, there is only the one that is in your way.

Here is something else I commonly see. When they discover “problem solving” many organizations want to immediately undertake large projects that involve “stretch goals” and breaking down complex issues. They look at operational metrics that are actually aggregated – total inventory, total lead time, productivity of the entire factory, total defect rates, total lead time through the system. While those metrics are nice to gage progress, they do not give you any actionable information.

Even worse is using averages. Averages aggregate even more, and “bad” tends to be countered by “good” in many average calculations. What is important is to look at each instance vs. an external, discrete, and objective standard or specification. Average defect rates tell you nothing at all about what to work on. But this unit had this defect, or this part dimension was this amount out of specification DOES.

Put another way, there are very few big problems. Big “problems” are the aggregated symptoms of many small problems.

This is good news and bad news.

The good news is that small problems can usually be understood, cleared and sometimes solved fairly quickly. The bad news is that it takes work to do this. The other bad news is that there isn’t any other way that actually works.

Doing a good job working on large complex issues requires engaging across the organization, time, and a high level of skill at understanding the situation, framing the problem, getting to causes, working on solutions, testing understanding, etc. Doing it well requires a mentor who is intimately familiar with the thinking behind problem solving.

This skill can not be gained in a “problem solving” or “A3” class, at least not one that simply walks the team members through the process once or twice. Skill comes from practice, and effective practice comes from starting simple, working in an environment where it is safe to experiment and to be wrong. This means working on shop floor issues that can be isolated from one another, the effect of a test or simulation can be seen immediately. The factory and production organization that Steven Spear describes in his research about Toyota is actually designed deliberately to facilitate this kind of work.

Another common mistake is setting up performance targets too early. If the processes are inherently unstable – if there is no sense of takt time, you are having problems with consistent quality or delivery, the first goal is simply to get to the point where you actually know how things are performing against an indicator of stability. Again, this is usually much simpler than setting a high level target and then trying to break down and stratify all of the issues out there. Set that stability target, study the process, and take on the disruptions as you see them. If there is a debate about which one to start with, then start with the simplest one so you can improve your capabilities.

In the end, it is about taking on problems as they come up, where they come up. That thinking is facilitated by the way you structure the flow, the work, and the organization itself. Get to the shop floor, stand in the chalk circle, and ask “What is stopping this team member from being successful right now.”