In the world of Lean Six Sigma, the DMAIC methodology stands as a cornerstone for process improvement and problem-solving. Within this framework, the D2 phase, or Problem Description, serves as the critical foundation upon which your entire improvement project is built. Understanding how to craft a clear, concise, and comprehensive problem description can mean the difference between a successful project and one that struggles to gain traction.
This comprehensive guide will walk you through the essential steps of creating an effective D2 Problem Description, complete with practical examples and actionable insights that you can apply immediately to your improvement initiatives. You might also enjoy reading about How to Identify and Handle Influential Points in Statistical Analysis: A Complete Guide.
Understanding the D2 Problem Description
The D2 Problem Description is the second deliverable in the Define phase of DMAIC (Define, Measure, Analyze, Improve, Control). While D1 focuses on forming the project charter, D2 specifically articulates what problem you are addressing, where it occurs, when it happens, and what impact it has on your organization. You might also enjoy reading about Scoping Lean Six Sigma Projects: Best Practices for the Define Phase Explained.
A well-crafted problem description creates alignment among stakeholders, establishes clear boundaries for your project, and ensures that everyone involved understands exactly what you are trying to solve. Without this clarity, teams often find themselves pursuing solutions to symptoms rather than addressing root causes.
The Essential Components of a D2 Problem Description
The What: Defining the Problem Clearly
Begin by stating what the problem is in objective, measurable terms. Avoid vague language and focus on facts rather than assumptions or opinions. Your problem statement should be specific enough to guide your improvement efforts but broad enough to avoid jumping to solutions prematurely.
Example: Instead of writing “Customer service is terrible,” a more effective problem description would be: “Our customer service response time has increased from an average of 2 hours to 6 hours over the past quarter, resulting in a 35% increase in customer complaints.”
The Where: Identifying Location and Scope
Clearly specify where the problem is occurring. This might include physical locations, departments, process steps, or product lines. Being specific about location helps contain your project scope and prevents unnecessary expansion into areas that are functioning properly.
Example: “This problem is occurring specifically in the Northeast regional distribution center, affecting outbound shipments to retail customers. The Southwest and Midwest centers are maintaining acceptable performance levels.”
The When: Establishing Timeline and Frequency
Document when the problem started, how often it occurs, and whether there are any patterns or trends. This temporal information can provide valuable clues about potential causes and helps establish a baseline for measuring improvement.
Example: “The issue began in January 2024 and occurs on approximately 40% of all orders processed during peak hours (10 AM to 2 PM). Historical data shows this problem was negligible (less than 5% of orders) prior to December 2023.”
The Impact: Quantifying the Business Effect
Express the problem’s impact in terms that matter to your organization: cost, time, quality, customer satisfaction, or safety. Whenever possible, use numerical data to demonstrate the significance of the problem and justify the resources needed to address it.
Example: “This problem is costing the organization approximately $45,000 monthly in expedited shipping fees, overtime costs, and customer credits. Additionally, customer satisfaction scores have decreased from 4.2 to 3.1 out of 5.0.”
How to Gather Data for Your Problem Description
Collecting Baseline Metrics
Start by gathering quantitative data that establishes the current state. This might include process cycle times, defect rates, cost figures, or customer feedback scores. Your data should cover a sufficient period to identify trends and patterns rather than isolated incidents.
Sample Data Set:
- Average order processing time (October 2023): 18 minutes
- Average order processing time (November 2023): 22 minutes
- Average order processing time (December 2023): 28 minutes
- Average order processing time (January 2024): 35 minutes
- Average order processing time (February 2024): 37 minutes
- Average order processing time (March 2024): 39 minutes
Conducting Stakeholder Interviews
Speak directly with people who experience the problem daily, including frontline employees, managers, and customers. Their qualitative insights can reveal nuances that data alone might miss and help you understand the full scope of the problem’s impact.
Reviewing Process Documentation
Examine existing process maps, standard operating procedures, and historical performance reports. This review helps you understand how the process should work versus how it actually functions, highlighting gaps and deviations.
Writing Your Problem Description: A Step-by-Step Approach
Step 1: Draft Your Initial Statement
Begin with a single sentence that captures the core problem. This statement should be factual, specific, and focused on the gap between current and desired performance.
Example: “Order processing times in the Northeast distribution center have increased by 117% over the past six months, exceeding the target completion time of 20 minutes per order.”
Step 2: Add Supporting Details
Expand your statement with additional context about where, when, and how the problem manifests. Include relevant data points that demonstrate the problem’s significance and trends.
Example expansion: “Analysis of 2,500 orders processed between October 2023 and March 2024 reveals that processing times have steadily increased from 18 minutes to 39 minutes per order. This trend is most pronounced during peak operating hours and affects approximately 60% of all orders handled by the facility.”
Step 3: Quantify the Business Impact
Connect the problem to business outcomes that resonate with leadership and stakeholders. Use financial metrics, customer impact measures, or operational efficiency indicators.
Example: “This performance decline has resulted in missed delivery commitments for 1,200 customers, generated $135,000 in additional labor costs due to extended work hours, and contributed to a 26% increase in customer service inquiries related to order status.”
Step 4: Define Boundaries and Exclusions
Clearly state what your project will and will not address. This prevents scope creep and helps manage stakeholder expectations.
Example: “This project will focus exclusively on the order processing workflow within the Northeast distribution center. It will not address inbound receiving processes, inventory management systems, or carrier selection protocols, as these areas are performing within acceptable parameters.”
Common Pitfalls to Avoid
Jumping to Solutions
One of the most frequent mistakes is embedding assumed solutions within the problem description. For instance, stating “We need a new software system” assumes you know the root cause. Instead, focus on describing the problem objectively and let the data guide you to appropriate solutions later in the DMAIC process.
Using Vague or Subjective Language
Terms like “often,” “sometimes,” “poor quality,” or “slow” lack the precision needed for effective problem-solving. Replace these with specific measurements, percentages, or frequencies derived from actual data.
Making the Scope Too Broad
Attempting to solve every related problem simultaneously dilutes your efforts and reduces your chances of success. A tightly focused problem description leads to more effective analysis and sustainable improvements.
Validating Your Problem Description
Once you have drafted your D2 Problem Description, validate it with your team and stakeholders. Ask these critical questions:
- Does everyone understand exactly what problem we are solving?
- Is the problem statement supported by data rather than opinions?
- Have we clearly defined the scope and boundaries?
- Can we measure improvement against this baseline?
- Does the business impact justify the resources required?
If the answer to any of these questions is no, revise your description until you achieve consensus and clarity.
Putting It All Together: A Complete Example
Problem Description: The Northeast regional distribution center is experiencing order processing times that exceed the standard target of 20 minutes per order. Data collected from October 2023 through March 2024 shows processing times have increased from 18 minutes to 39 minutes, representing a 117% increase. This problem affects approximately 60% of orders processed during peak hours (10 AM to 2 PM) and occurs Monday through Friday. The extended processing times have resulted in $135,000 in additional labor costs over the six-month period, caused 1,200 late shipments, and contributed to a customer satisfaction score decline from 4.2 to 3.1. This project will focus on identifying and eliminating factors that extend order processing times within the picking, packing, and staging workflow. The project will not address receiving operations, inventory accuracy, or transportation scheduling, as these processes are meeting performance standards.
Transform Your Organization’s Performance
Mastering the art of writing effective D2 Problem Descriptions is just one component of the powerful Lean Six Sigma methodology. When properly applied, these skills enable you to drive meaningful improvements that deliver measurable results for your organization. Whether you are looking to reduce costs, improve quality, enhance customer satisfaction, or streamline operations, the structured approach of DMAIC provides the framework you need for success.
The examples and techniques outlined in this guide give you a solid foundation, but true expertise comes from hands-on practice and expert guidance. Professional training helps you avoid common pitfalls, accelerates your learning curve, and provides you with tools and templates that make implementation easier.
Enrol in Lean Six Sigma Training Today and gain the comprehensive skills needed to lead successful improvement projects in your organization. Whether you are pursuing Yellow Belt, Green Belt, or Black Belt certification, professional training provides the knowledge, practice, and credentials that employers value. Take the next step in your professional development and join thousands of professionals who have transformed their careers and their organizations through Lean Six Sigma expertise. Contact a certified training provider today to explore your options and start your journey toward becoming a recognized problem-solving expert.
