Improvement Tool Guide

Problem Statement

Describe the performance gap clearly, factually, and without assuming a cause or prescribing a solution.

The job this tool doesDescribe the performance gap clearly, factually, and without assuming a cause or prescribing a solution.
Use it toDescribe the performance gap clearly, factually, and without assuming a cause or prescribing a solution.
Best withThe people who know and experience the work
OutcomeA clearer, evidence-based next step
Use Problem Statement when the team needs a shared way to think, learn, and decide.

When to use it

Choose the tool because it fits the question.

  • People disagree about the problem
  • A project is starting with a preferred fix
  • The impact and scope are unclear

How it works

Use a simple, disciplined sequence.

1

Frame

Describe what is happening, where, and for whom.

2

Explore

Quantify the gap using a useful baseline and timeframe.

3

Make it visible

Explain the customer or business impact.

4

Decide and learn

Check that the statement contains no unverified cause or embedded solution.

Example

What it can reveal

During the last quarter, 38% of applications required rework, adding an average of two days and creating repeated customer contact.

Template walkthrough

See how Problem Statement organizes the work.

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.

Problem Statement template preview
A small preview of the Green Dot template. Use the numbered guide to prepare the conversation before downloading or customizing the file.
1
Set up the question

Describe what is happening, where, and for whom.

2
Work through the evidence

Quantify the gap using a useful baseline and timeframe. Explain the customer or business impact.

3
Close with a decision

Check that the statement contains no unverified cause or embedded solution.

Before you begin

Bring enough context to make the tool useful.

  • Write down the specific question, decision, or gap the team needs to address.
  • Bring recent observations, customer evidence, process data, or examples—not memory alone.
  • Include people who perform, receive, or are affected by the work.

Common failure modes

A completed template is not the same as learning.

  • Starting with a preferred answer and using the tool to justify it.
  • Completing the template alone when the work crosses people or functions.
  • Stopping when the fields are filled instead of naming the next test, owner, or decision.

Problem Statement

Summarizing the Who, What, When/Where, and Why of the Problem

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”.

Share
Tweet
Post
Problem Statement

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.

Downloadable Problem Statement Template

Download the Free "Design Challenge Statement" Template (PDF)

Purchase the template to customize for your own organization

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.

Or, become a member and Enjoy Unlimited Downloads

Join now and gain access to all the tools in our digital toolbox.

Want to Learn More about Using Problem Statements?

Lean Six Sigma Yellow Belt Training, continuous improvement certifications

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

Connect Problem Statement to the work around it.

Improvement Nerds Podcast

Never Miss an Improvement Nerds Episode

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!

Sign up today!

* indicates required
/ ( mm / dd )

Be Sure to Follow Us on Social Media