Getting to the right problem statement in an A3

For those of you that are in favor of A3 problem solving methods or for those of you that are experimenting in your daily work... or perhaps those of you that have been compelled by me to use an A3, you know that getting to a solid problem statement is one of the more frustrating but potentially rewarding efforts.

Working to get to a good problem statement is essential and here are a couple tips I often relay to individuals that seems to have helped me.

1. ) Don't infer solutions within a problem statement. A problem statement is not really effective if you are taking a shortcut through the left hand of an A3. Avoid statements like "We do not have a process to do 'X'" It automatically assumes that a process will fix what ever the real problem is. As natural problem solvers this is one of the most difficult habits to break and I struggle with it myself.

2.) Work with a Lean buddy. Have a trusted person that you don't feel shy about looking a little dumb in front of. The meanancing value of a good A3 session is to continually boil down details using the 5-whys and get to the true nature of a problem.

3.) Use these four guiding questions with your Lean buddy to help shape a problem statement.

• What is the problem you want to address? 
• Why do you think it is a problem? (you got data to support that?)
• How would you describe the problem? (what's the result or impact?)
• Why do you think this problem needs to be addressed now?

We have good resources at our disposal at UMHS through the Michigan Quality System (MQS) to help with developing our Lean and A3 methods. If you are interested in learning more about structured problem solving, resources at UMHS, or what irons we currently have in the fire around specific problems using this method I encourage you to seek me out so we can chat.