<h2 id="59f22abd-aad6-4858-9e8e-b13ee9149832" data-toc-id="59f22abd-aad6-4858-9e8e-b13ee9149832" style="text-align: left; font-size: 24px; line-height: 1.2;">8D Step 2: Define the Problem Poster</h2><p>A problem-solving effort can only be as effective as the problem definition that guides it. If the problem is poorly defined, teams often investigate the wrong causes, implement ineffective solutions, and waste valuable time and resources.</p><p>This poster focuses on the second discipline of the 8D methodology: <strong>Define the Problem</strong>. It provides practical guidance for creating clear, objective, and measurable problem statements that establish a strong foundation for the rest of the investigation.</p><p></p><img src="https://ezycourse.b-cdn.net/5664/cmqr0c1r3ag93j6plbmr291vs.png" alt="image" containerstyle="position: relative; width: 458px; height: auto; cursor: pointer; margin: 0px auto;" wrapperstyle="display: flex;"><p></p><hr><h2 id="51e01199-0389-4806-a6b0-7c9b057f1276" data-toc-id="51e01199-0389-4806-a6b0-7c9b057f1276" style="text-align: left; font-size: 24px; line-height: 1.2;">What This Poster Covers</h2><h3 id="09daa627-9e6d-4d6e-8f8f-2c2b061b32c7" data-toc-id="09daa627-9e6d-4d6e-8f8f-2c2b061b32c7" style="text-align: left; font-size: 20px; line-height: 1.2;">Why Problem Definition Matters</h3><p>The poster explains why a clear problem definition is critical to successful problem solving.</p><p>A well-defined problem helps teams:</p><ul><li><p>Create a common understanding</p></li><li><p>Focus on the real issue</p></li><li><p>Avoid jumping to conclusions</p></li><li><p>Determine what data is needed</p></li><li><p>Establish a baseline for improvement</p></li><li><p>Build credibility and drive action</p></li></ul><p>It reinforces a key message:</p><p><strong>If you define the problem wrong, you cannot solve it right.</strong></p><hr><h3 id="5d31fe89-328a-40b5-afd0-fe535a141bb0" data-toc-id="5d31fe89-328a-40b5-afd0-fe535a141bb0" style="text-align: left; font-size: 20px; line-height: 1.2;">The Goal of Problem Definition</h3><p>Before investigating causes or developing solutions, teams must be able to clearly answer questions such as:</p><ul><li><p>What is happening?</p></li><li><p>Where is it happening?</p></li><li><p>When does it occur?</p></li><li><p>How often does it happen?</p></li><li><p>How large is the impact?</p></li><li><p>Who is affected?</p></li></ul><p>The poster emphasizes that problem statements should be understandable by everyone involved in the investigation.</p><hr><h3 id="aedeae8a-dab0-4032-8924-718a10cda91a" data-toc-id="aedeae8a-dab0-4032-8924-718a10cda91a" style="text-align: left; font-size: 20px; line-height: 1.2;">Characteristics of a Good Problem Definition</h3><p>The poster outlines the key attributes of an effective problem statement.</p><p>A strong problem definition is:</p><h4 id="a5fb0ad0-f6ea-41a9-ba49-e10d2868c56b" data-toc-id="a5fb0ad0-f6ea-41a9-ba49-e10d2868c56b" style="text-align: left; font-size: 18px; line-height: 1.2;">Specific</h4><p>Clearly describes the issue without being vague or overly broad.</p><h4 id="c9788730-819c-4ade-bc98-2f67d9eb3b37" data-toc-id="c9788730-819c-4ade-bc98-2f67d9eb3b37" style="text-align: left; font-size: 18px; line-height: 1.2;">Measurable</h4><p>Uses facts, numbers, and objective evidence whenever possible.</p><h4 id="2fea7181-cbd2-444d-a1fb-b9b91120a5d8" data-toc-id="2fea7181-cbd2-444d-a1fb-b9b91120a5d8" style="text-align: left; font-size: 18px; line-height: 1.2;">Observable</h4><p>Based on actual conditions rather than assumptions or opinions.</p><h4 id="22d3deed-f1a5-4bc3-8865-cd79987e6ee3" data-toc-id="22d3deed-f1a5-4bc3-8865-cd79987e6ee3" style="text-align: left; font-size: 18px; line-height: 1.2;">Relevant</h4><p>Aligned with organizational priorities and business needs.</p><h4 id="51d3ec31-31a0-4f97-a227-cb624eed3f83" data-toc-id="51d3ec31-31a0-4f97-a227-cb624eed3f83" style="text-align: left; font-size: 18px; line-height: 1.2;">Bounded</h4><p>Has a defined scope and timeframe.</p><h4 id="b5843f9e-15f4-4dc3-bbbf-b354cbcbfbff" data-toc-id="b5843f9e-15f4-4dc3-bbbf-b354cbcbfbff" style="text-align: left; font-size: 18px; line-height: 1.2;">Understandable</h4><p>Can be easily understood by all stakeholders.</p><hr><h3 id="ddd66dc7-6adc-4bb7-9781-130149dfa5ed" data-toc-id="ddd66dc7-6adc-4bb7-9781-130149dfa5ed" style="text-align: left; font-size: 20px; line-height: 1.2;">What to Include in a Problem Statement</h3><p>The poster provides a practical framework for documenting the problem.</p><p>Teams are encouraged to define:</p><h4 id="1c6395c2-e7ed-4962-b8f7-57ef564ea2f4" data-toc-id="1c6395c2-e7ed-4962-b8f7-57ef564ea2f4" style="text-align: left; font-size: 18px; line-height: 1.2;">What?</h4><p>What is happening?</p><h4 id="b557d0ee-07d6-4654-87df-f1295c5c2924" data-toc-id="b557d0ee-07d6-4654-87df-f1295c5c2924" style="text-align: left; font-size: 18px; line-height: 1.2;">Where?</h4><p>Where is the problem occurring?</p><h4 id="1b60fd9a-7313-4a1b-aa03-d44a4dad8b31" data-toc-id="1b60fd9a-7313-4a1b-aa03-d44a4dad8b31" style="text-align: left; font-size: 18px; line-height: 1.2;">When?</h4><p>When does it happen?</p><h4 id="6bfd157b-3466-43a4-ac3f-b0bfe8647f5c" data-toc-id="6bfd157b-3466-43a4-ac3f-b0bfe8647f5c" style="text-align: left; font-size: 18px; line-height: 1.2;">How Often?</h4><p>How frequently does the problem occur?</p><h4 id="7a488515-631e-41af-b23f-043739470e97" data-toc-id="7a488515-631e-41af-b23f-043739470e97" style="text-align: left; font-size: 18px; line-height: 1.2;">How Big?</h4><p>What is the size of the gap or impact?</p><h4 id="5d10c5e8-c30c-4e8d-b10d-86a910c23529" data-toc-id="5d10c5e8-c30c-4e8d-b10d-86a910c23529" style="text-align: left; font-size: 18px; line-height: 1.2;">Who?</h4><p>Who is affected by the issue?</p><p>This structure helps teams create complete and objective problem definitions.</p><hr><h3 id="42f69b4f-f07d-4758-bd2f-618bf2a7316d" data-toc-id="42f69b4f-f07d-4758-bd2f-618bf2a7316d" style="text-align: left; font-size: 20px; line-height: 1.2;">Moving Beyond Symptoms</h3><p>One of the most valuable concepts presented in the poster is the distinction between symptoms and problems.</p><p>The poster illustrates the progression from:</p><p><strong>Symptom → Investigation → Problem Definition → Root Cause Analysis</strong></p><p>This helps teams avoid the common mistake of treating symptoms while overlooking the underlying issue.</p><hr><h3 id="993d268a-10e8-4ba5-9daf-bed6fd5f5e7b" data-toc-id="993d268a-10e8-4ba5-9daf-bed6fd5f5e7b" style="text-align: left; font-size: 20px; line-height: 1.2;">Common Mistakes to Avoid</h3><p>Many problem-solving efforts fail because teams define the problem poorly.</p><p>The poster highlights common mistakes such as:</p><ul><li><p>Being too vague</p></li><li><p>Jumping directly to causes</p></li><li><p>Defining problems too broadly</p></li><li><p>Using opinions instead of facts</p></li><li><p>Ignoring customer impact</p></li><li><p>Failing to establish scope or timeframe</p></li></ul><p>These errors often lead investigations in the wrong direction.</p><hr><h3 id="860200a4-31c0-4911-b552-3164a1b49242" data-toc-id="860200a4-31c0-4911-b552-3164a1b49242" style="text-align: left; font-size: 20px; line-height: 1.2;">Tools That Support Problem Definition</h3><p>The poster identifies several tools that can help teams understand and define problems more effectively.</p><p>Examples include:</p><ul><li><p>KPI and performance reports</p></li><li><p>Trend analysis</p></li><li><p>Run charts</p></li><li><p>Pareto analysis</p></li><li><p>Process maps</p></li><li><p>Voice of the Customer (VOC)</p></li><li><p>Customer feedback</p></li><li><p>Direct process observation</p></li></ul><p>These tools help teams move from assumptions to evidence-based understanding.</p><hr><h3 id="fa346fbf-f872-4bab-a341-a19126b535e5" data-toc-id="fa346fbf-f872-4bab-a341-a19126b535e5" style="text-align: left; font-size: 20px; line-height: 1.2;">What Good Problem Definition Looks Like</h3><p>The poster outlines characteristics of a strong problem statement, including:</p><ul><li><p>Team agreement on the problem</p></li><li><p>Clearly defined scope</p></li><li><p>Data-supported conclusions</p></li><li><p>Understanding of the impact</p></li><li><p>Clear criteria for success</p></li></ul><p>When these elements are present, teams are better prepared for root cause analysis and the development of corrective actions.</p><hr><h2 id="b414cc4b-a771-47eb-82af-dd2d92d89683" data-toc-id="b414cc4b-a771-47eb-82af-dd2d92d89683" style="text-align: left; font-size: 24px; line-height: 1.2;">Ideal For</h2><p>This poster is particularly valuable for:</p><ul><li><p>Problem-Solving Teams</p></li><li><p>Quality Professionals</p></li><li><p>Continuous Improvement Programs</p></li><li><p>Lean Practitioners</p></li><li><p>Engineering Teams</p></li><li><p>Manufacturing Operations</p></li><li><p>Supervisors and Managers</p></li><li><p>Frontline Leaders</p></li><li><p>Corrective Action Programs</p></li><li><p>Kaizen Teams</p></li></ul><hr><h2 id="c05f4db7-be66-491d-8b34-7206d9ca57ae" data-toc-id="c05f4db7-be66-491d-8b34-7206d9ca57ae" style="text-align: left; font-size: 24px; line-height: 1.2;">Use This Poster To</h2><ul><li><p>Train employees on 8D Step 2</p></li><li><p>Improve problem-definition skills</p></li><li><p>Support root cause analysis efforts</p></li><li><p>Reinforce data-based decision making</p></li><li><p>Prevent teams from chasing symptoms</p></li><li><p>Standardize problem statements</p></li><li><p>Improve the effectiveness of investigations</p></li></ul><hr><h2 id="25162f11-09fa-4ed5-9c3a-d93ed8cdc4f1" data-toc-id="25162f11-09fa-4ed5-9c3a-d93ed8cdc4f1" style="text-align: left; font-size: 24px; line-height: 1.2;">Define the Problem Before Solving It</h2><p>Strong problem-solving begins with a strong understanding of the problem itself. This poster helps teams create clear, measurable, and actionable problem definitions that serve as the foundation for successful root cause analysis, corrective actions, and long-term improvement.</p>

Problem Solving Poster: 8D Step 2 (Define the Problem)

Learn how to define problems clearly using facts, data, and measurable gaps so your team can focus on the real issue and avoid wasted effort.

Problem Solving Poster: 8D Step 2 (Define the Problem)

Key Features

Short Description

Description

Specifications

Related Products

CI Term Poster: 10-Year-Old Mindset

A3 Poster (Project Area): Why Are We Asking Questions?

PS Tools Poster (Data Collection/Observation): Sampling Plan

A3 Report Template Overview Poster