Contact ME

Comments? Suggestions? Compliments? I'll take them all.

Please use the form on the right to contact me.

 

 

         

123 Street Avenue, City Town, 99999

(123) 555-6789

email@address.com

 

You can set your address, phone number, email and site description in the settings tab.
Link to read me page with more information.

The A3 Report: Why It Is Useful - Template Included

@Work

Eldon Kao
Continuous Improvement Blog

The A3 Report: Why It Is Useful - Template Included

Eldon Kao

What is it?
The A3 Report is a structured problem solving approach and one-page communication that summarizes a problem solving project from start to finish. The name is derived from the size of paper the report is presented on: A3 or 11'x17' Tabloid). 

Purpose
The A3 report can be used as a tool for problem solving as organized steps or used to summarize past problems for easy analysis. As everything is captured on a single page, it is possible to see the full picture and get a broad perspective of the problem. 

How To Use
Step 1: Record short description of the problem as the title.
Step 2: Record the names of the owner and team members. There should be only one name as owner.  
Step 3: Record origination date and revision date to keep track of the revision history.  
Step 4: What is the impact of the problem on KPI metrics if left unresolved? How does the problem impact safety, quality, schedule, culture, and/or environment?
Step 5: The problem description should be written as a story line. The description should justify why the problem solving approach was implemented and be in a language that everyone can understand. Elaborate on the problem and quantify the impact stated above. Use supplemental information such as pictures/charts/graphs to help communicate the issue. 
Step 6: The goal/objective should be a description of what you hope to accomplish by addressing the problem stated above. The goal should be a measurable (quantifiable) improvement with relevant KPI or metric. A due date is also required to ensure actions are performed in a timely manner.
Step 7: Problem/Root Cause analysis is performed using tools such as brainstorming, 5 why's, or fishbone diagram etc. Make sure your problem statement is clear and concise before moving on to this step or your root cause will not be effective. Include also any supporting data/evidence that supports the conclusions reached. You can not proceed to next step until true root cause is established. 
Step 8: Countermeasures include necessary preventive actions that address the root cause identified in Step 7. More than one preventive action may be required. Short term or interim
Step 9: Ensure that adequate time has elapsed after implementing the countermeasures in Step 8 before claiming results. Revisit the KPIs established in Step 4 and Goal in Step 6, do the results reflect this? If you fall short or did not have impact here, it may be because true root cause was not found in Step 7 or that the countermeasures in Step 8 were not effective. 
Step 10: Future steps and additional applications. How can you optimize your results? What other areas could benefit from this solution? Can you use this to reduce risk in other areas of the organization?