---
title: "Define the problem"
source: 18F Guides
source_url: https://github.com/18F/guides
licence: CC0-1.0
domain: engineering
subdomain: 18f-guides
date_added: 2026-04-25
---

It's critical that you deeply understand and articulate the problem you're solving. With this deep understanding, you can be comfortable exploring, evaluating, and pivoting to different solutions.

Just as importantly, you need to bring everyone along with you. Your partners and teammates need to agree on the problem you're tackling and the problems you are not tackling. A well-written problem statement helps align and motivate your team around a common goal, providing focus and keeping distractions at bay.

## Considerations: A good problem statement...

- Defines the overlying problem

- Surfaces the major challenges, focusing on the pain points that are most frequent, urgent, or encumbering

- Articulates the impact of the problem, including who the problem affects and how much it affects them

- Informs decisions about solutions without prescribing a specific solution

- Inspires key stakeholders to commit to solving the problem

## Activities: How to get there

Problem statements can be written at different levels or granularities, and you will likely find yourself defining the problem multiple times over the course of an engagement.

- Understand the initial problem statement that led to your engagement with the client, and work with the client to periodically revise and refine it based on research.

- Ask probing questions to uncover symptoms or solutions masquerading as root causes.

- Draw on user and/or market research to validate pain points.

- Prioritize pain points and research themes based on frequency, urgency, or impact.

## Incorporation: What to do next

- Document the problem throughout implementation and keep it visible and central. Refer to it regularly to help the team stay focused.

- Use the problem statement to create the vision.

- Use the problem statement to surface and resolve possible disagreements among stakeholders.

- As you absorb new information, regularly reconsider the problem and update as appropriate.

## Resources

- [What is a problem statement](https://docs.google.com/presentation/d/1KDf3rppwlkZGzNsG-dn1CbkaYWlO8B1H2Is54646A4A/edit#slide=id.g1d7a840d6b_0_78): An overview of what a problem statement is, what makes one strong vs. weak, and problem statements in the context of our work at 18F.

- [How to build a problem statement (1)](https://medium.com/eightshapes-llc/how-to-build-a-problem-statement-d1f21713720b): A format / exercise for generating problem statements.

- [How to build a problem statement (2)](https://docs.google.com/document/d/1GjzpUHQZGWG8lEzg8ZAMqRG3tZhaw_V010OUnt9yKeI/edit#): Elements of a good problem statement, along with sample formats and examples.

- [How to build a problem statement (3)](https://app.mural.co/t/gsa6/m/gsa6/1614280571328/064874369c7597eb3467fec790202b46ffe41f99): An exercise to identify the problems experienced, who is affected, and the impacts, as well as understand hopes and fears for the initiative.

- [How to prioritize problem statements (1)](https://guides.18f.gov/methods/discover/kj-method/): KJ Method, a general prioritization method involving brainstorming, [affinity grouping](https://guides.18f.gov/methods/decide/affinity-mapping/), and ranking (e.g., [dot voting](https://guides.18f.gov/methods/discover/dot-voting/)).

- [How to prioritize problem statements (2)](https://www.mindtheproduct.com/enter-matrix-lean-prioritisation/): 2x2 Prioritization Matrix, a method often used to prioritize tasks or backlog items but that can be used more generally to sort items based on factors such as Effort vs Value.

- [How to identify the root cause of a problem](https://guides.18f.gov/methods/discover/five-whys/): Five Whys, an iterative process for uncovering the root cause underlying the observable problem.
