A Job to be Done is the outcome a persona is “hired” to achieve, stated independent of any one solution. It’s the spine that ties a persona to the use cases a builder can implement, with a business case (sizing + impact) explaining why it’s worth building.
There is intentionally no problems/ folder. The “problem” is the gap between the job and today’s
reality, captured here under Why it’s hard (and in sector/why-this-is-hard.md)
and in each design’s how-might-we question.
| Job to be done | Persona(s) | Side |
|---|---|---|
| Find convenient, dignified food support | Reba, Marguerita | client |
| Distribute all donated food each session | Gladys | provider |
| Distribute the right food to the right pantries before it spoils | Dan | provider |
A note on evidence. The need behind each job is validated from the event. The “how they do it today” flow is largely a gap. Caravan Studio’s design events surface desired future states and data gaps, not detailed current-state workflows. That depth is expected to come from interviews (Iteration 2+) and from designing with the community.