REPLY Definition of root cause (SD6791)

[SDMAIL Ralf Lippold]

Posted by  Ralf Lippold <ralf_lippold at web.de>

Hi Jack,
hi discussion participants,

I have been really struck by the interest this first posting initiated 
amongst the system dynamics community.

Thanks a lot for starting it:-))

As I moderate a group on the questions around "Lean Thinking" 
(http://www.xing.net/lean) the posted question is one of the key 
"mysteries" in understanding disfunctional processes. From my personal 
experience I have added some thoughts on the initial quote:

> The System Improvement Process (SIP) is designed to solve any difficult
> social problem. Its four main steps are:
>
> 1. Problem Definition – Identify the problem
>
> 2. System Understanding (Analysis) – Analyze the problem/system until
> key cause

This can't be more than the "key cause" that can be understood by the 
people involved when questioned the "5-Whys" in a very deep manner. The 
questions should be asked until the 5th question or a phase where there 
emerges no additional seeable reason.

So you avoid at least the "quick fix" that leads into the "Fixes that 
Fail" archetype and even more trouble than you could image.

> and effect relationships are understood.

The cause and effect will be probably never be fully understood as 
systems are complex and as you change one parameter in there all the 
others change (if not immediately than over time).

> This step is so
> important it has 5 substeps.
>
> 3. Solution Convergence – Use that knowledge to converge on a solution.
>
> 4. Implementation – Implement the solution.

Try to use the "solution" in a small, to be overlooked part of the 
system so possible negative impact on the overall system is put to a 
minimum (especially in car production or manufacturing processes instant 
changes in the system will bring real disturbance into it).

> ....
> I had two questions: (1) Is this a productive and sufficiently
> unambiguous definition of root cause?

Not quite from my point of view as too complicated especially on the 
shopfloor or at places where the "real" work is done.

> (2) Is finding the root cause
> really the most important step in the average SD analysis for difficult
> problems?

The searching for the root cause will emerge -eventually- in deeper 
understanding what is going on in the system and how the different parts 
are connected. This will lead to a shared vision and understanding - 
this is the real benefit of the method.

This are my instant thoughts on the issue (that is more complex as we 
all probably think)

Cheers,

Ralf
Posted by  Ralf Lippold <ralf_lippold at web.de>
posting date  Fri, 7 Mar 2008 00:31:05 -0500