<aside> 🧩
Evergreen reference for the Scenario-Based Problem Statement workshop. Visuals are live embeds of the FigJam board, so they stay current. A portable Markdown copy with static screenshots (for Gemini / NotebookLM) lives alongside it.
</aside>
A workshop that turns a pile of assumed problems into sharp, root-cause problem statements, problem checklists, and user stories the team can build against.
The full FigJam template at a glance: intro checklist, the problem dump, Table 1, and Table 2.
The full FigJam template at a glance: intro checklist, the problem dump, Table 1, and Table 2.
| Deliverables produced | Problem Statements, Problem Checklists, User Story Statements |
| Milestone | Continuous Discovery |
| Project phase | After Sprints Begin |
| Typical week | Sprint 1 |
| Owned by | Product Management |
| Who takes part | Internal Teammate |
| Trainer-facilitated | Always |
| Time needed | A substantial amount of working sessions over the course of a sprint |
| Practices taught | Shared Ownership, Agility, Collective Decision Making |
The team learns how to write clear problem statements based on real situations users face today. Starting from what is happening in the world right now, the team describes the problem, the user's needs and goals, and turns those into user stories the team can act on.
Why it's valuable. Teams waste time when they jump to solutions before they understand the problem. Writing clear problem statements keeps the team focused on what users actually need, so the work solves a real problem.
When to use: during discovery, after sprints begin, when the team is deciding what to solve.
How often. Do this during discovery whenever the team is trying to understand a new problem. Come back to it as you learn more from research.
Where problem statements fit across the project milestones.
Where problem statements fit across the project milestones.
Expected outcome. By the end of this workshop, the team will have produced its Problem Statements, Problem Checklists, and User Story Statements.
These are the ideas the team must hold before they touch the tables. They come straight from the workshop board.