Process Firefighting, Sometimes the Result of Process Arsonists?
I was talking with someone a few weeks back about the analogy of “fire fighting” in a workplace (something that applies in factories and hospitals… any workplace, basically). Typically problem solving involves just fixing the immediate problem. For example, if an item is missing (a part for assembly or a medication for a patient), the fire fighting approach stops when we “put the fire out” meaning we can now build our product or treat our patient.
Maybe this is a bad analogy, showing we don't know much about fire fighting (I would suspect). Does a fire crew all just leave once a fire is doused, or does somebody stay to investigate the root cause? Do they see what can be learned to prevent fires at other places? I bet they do. Can anyone shed some light on true “fire fighting?” Are we being unfair to fire fighters when we use this analogy in the workplace? If you know more about REAL fire fighting, please click on “comments” to share your thoughts.
The knock on workplace fire fighting is that we don't stop to analyze the root cause, nor do we focus on future prevention. When a part or medication is missing, do we (when we have a moment) stop and figure out WHY that happened (not WHO messed up)? Do we stop to improve the process so it can't happen again?
Thinking about medications that go missing in a nursing unit. we might ask questions like:
- Was there not a dedicated, well labeled location for that patient's medications?
- Is there not a standardized process for what to do with medications when they arrive from the pharmacy?
- If this was a stocked medication, does our standard inventory level need adjusting?
- Did the pharmacy have a slow delivery process? If so, what can be done to improve that process?
Depending on the particulars, there are MANY things that can be done after the medication has been found. Now, once the “fire” is out (we have the medication), we might have to first continue our value adding work (giving the medication to the patient). We might not have the luxury of immediately “stopping the line” to get a problem solving team together.
But, I bet later that day we would have some time to work on the process. We might identify a countermeasure to try, or we might better document the problem, setting it aside until a kaizen team can work on it, if it's a bigger problem. Simple fixes should be done immediately, but bigger fixes might have to wait. Such is life.
One other topic that came up was how some people LOVE fighting workplace fires. They get a rush from it. They're the hero. If we fix the process, maybe that person loses their chance to be a hero. Maybe they have less of incentive to be a part of the fix (of course, we have to let them find other ways to feel valuable, since fixing the process is important for the customer — our patient).
Not participating in fixing root causes is one thing. The person I was talking to asked if some people purposefully create problems (or allow them to happen) so they can fix them. I asked, “that would be a process arsonist then, right?” I'd like to think that doesn't happen much in workplaces, yet alone hospitals.
I did a google search for the term “process arsonist” and surprisingly couldn't find any references. Did I coin a new term?? Have you ever seen a “process arsonist”?
Please check out my main blog page at www.leanblog.org
The RSS feed content you are reading is copyrighted by the author, Mark Graban.
, , , on the author's copyright.