## Problem Statement A problem statement is a concise description of an issue that needs to be addressed, often contrasted with a solution statement or a set of user requirements. Concisely define the challenge that needs to be addressed: 1. **Problem:** describe the problem, including the context, background, and any contributing factors. 2. **Impact:** explain the negative consequences of the problem, including how it affects stakeholders, such as customers, employees, or the organization. 3. **Scope:** define the boundaries of the problem, including any limitations or constraints that must be considered when developing a solution. This helps to focus the team's efforts and prevents getting sidetracked. Define must-have, nice-to-have, and out-of-scope features. 4. **Assumptions:** list any assumptions made when defining the problem, such as underlying beliefs. Being explicit about assumptions helps identify biases. 5. **Unknowns:** list any areas that require further investigation to understand the problem and develop a solution. This section highlights knowledge gaps and helps the team prioritize research efforts. 6. **Goals:** provide a high-level description of the desired outcomes, which guides the development of a solution and helps establish success criteria. 7. **Anti-goals:** identify potential adverse outcomes to avoid when developing a solution to ensure the solution does not inadvertently create new problems or exacerbate existing ones.