Step 1: Identify
Define a clear, measurable problem statement that the team agrees on.
Every improvement starts with a clear problem. In Step 1, you define a measurable problem statement that the whole team agrees on — grounding your effort in data, not assumptions. A well-written problem statement describes the current state (As-Is), the desired state, and the measurable gap between them. This is where the discipline starts: no jumping to solutions, no blaming, no guessing. Just observation, measurement, and clarity.
Key Questions This Step Answers
- What specific, measurable gap exists between where we are and where we need to be?
- Who is affected by this problem and how can we quantify the impact?
- Is this problem within our team's sphere of influence to solve?
- Do we have enough data to prove this is a real problem, not just a perception?
Guiding Questions
- What is the current state (As-Is)?
- What is the desired state?
- What is the gap between current and desired?
- How does this impact the organization?
Tools Used in This Step
Problem Statement
Define As-Is, Desired State, and Gap
RequiredImpact Assessment
Quantify the problem impact
List Reduction
Narrow a long list of candidate problems to a manageable shortlist through structured elimination
Weighted Voting
Prioritize options by distributing a fixed number of votes across candidates
Impact Metrics
Capture quantitative baseline metrics (financial cost, time wasted, defect rate, customer satisfaction) before improvement begins — enables ROI calculation in Step 6
Tips
- •Use the As-Is / Desired State / Gap framework to ensure your problem statement is specific and measurable
- •Avoid jumping to solutions — focus only on describing the problem
- •Quantify the gap with data whenever possible (%, $, time)
- •Interview stakeholders at multiple levels for a well-rounded view
Best Practices
- ✓Write the problem statement as a neutral observation, not a blame assignment
- ✓Include both leading indicators (predictive) and lagging indicators (historical)
- ✓Define the scope boundary — what is in and out of this improvement effort
- ✓Validate the problem with data before committing the team to solving it
- ✓Ensure the problem is within the team's sphere of influence to solve
Facilitation Guide
Gather the team for a 60-minute session. Start with each person silently writing what they believe the problem is (5 min). Share and cluster similar statements (15 min). Draft a unified As-Is / Desired State / Gap statement together (20 min). Quantify the impact with available data (15 min). Close by confirming team agreement on the statement (5 min).
Completion Criteria
Before moving to the next step, ensure these criteria are met:
- Problem statement is written with As-Is, Desired, and Gap
- Impact has been assessed
- Team members have been identified
Read more in The Never-Ending Quest
Chapter 4 of the PIPS book covers Step 1 in depth — with real-world case studies, facilitator notes, and common pitfalls.
Browse Chapters