Frame
Describe what is happening, where, and for whom.
Improvement Tool Guide
Describe the performance gap clearly, factually, and without assuming a cause or prescribing a solution.
When to use it
How it works
Describe what is happening, where, and for whom.
Quantify the gap using a useful baseline and timeframe.
Explain the customer or business impact.
Check that the statement contains no unverified cause or embedded solution.
Example
During the last quarter, 38% of applications required rework, adding an average of two days and creating repeated customer contact.
Template walkthrough
Use the preview and callouts together. The goal is not to fill every space—it is to make the team’s thinking visible enough to test, discuss, and improve.

Describe what is happening, where, and for whom.
Quantify the gap using a useful baseline and timeframe. Explain the customer or business impact.
Check that the statement contains no unverified cause or embedded solution.
Before you begin
Common failure modes
From tool to improvement
Green Dot helps teams define the real performance gap, understand the work, and focus improvement effort before solutions outrun the evidence.
The problem statement is a concise description of the issue that needs to be addressed. In process improvement, defining the problem is a critical step in solving the problem. As the saying goes, “a well-defined problem, is a half-solved problem”.
A good problem statement can serve as the main touchstone for a project team as they undertake any improvement effort. The problem statement helps to create a shared need by clearly explaining what the problem is, where the problem is occurring, who is impacted by the problem, and why the problem needs to be addressed.
Regarding process improvement, defining the problem from the business’s and the customer’s perspective is often one of the first steps in the project. The problem statement helps to establish the project’s key focus and set the parameters for the project scope. This perspective can support the selection of the right project team expertise, while giving clear direction to that team on where to target their improvement efforts.
As the team gets started in their improvement efforts, it is important to note that the problem statement is meant to guide the team, not confine it. As the team conducts further exploration of the problem, and as a result, gains new learning, it is important that the team revisits the problem statement and updates it accordingly. It is through this iterative process that the team verifies that they are working on the right problem across the entirety of the project.
All of our tools and templates are available in Word or PowerPoint format to allow organizations to purchase and customize the templates to their brand standards.
Join now and gain access to all the tools in our digital toolbox.
Want to Learn More about Using Problem Statements?
The primary role of the Lean Six Sigma Yellow Belt is to act as the organization’s eyes and ears, helping to detect when an opportunity might exist for the organization to improve. If you would like to advance your skills in helping project teams to not only articulate the problem, but to gain traction on actually solving the problem, please consider participating in our Lean Six Sigma Yellow Belt Certification Course.
The Yellow Belt leads local-level improvement efforts that are considered “low hanging fruit” projects – meaning the project complexity is low and that the project can be completed with minimal data and on a short timeline of 60-90 days. The Yellow Belt’s primary focus is to reduce process waste, making processes easier to perform and more efficient.
Need help completing you Problem Statement?
Schedule a 30 minute coach call today and let’s talk through the details.
Continue learning
Sign up for our newsletter to get the latest articles, tools, templates, podcasts, and improvement tips. All delivered right to your inbox!
Let’s nerd out!