# Jobs-to-be-Done · Gains & Pains Matrix
**Clarify what users are really trying to accomplish**  
*Prodora Template · prodora.io*

List the key jobs users hire your software (or current system) to do. For each job, capture the pains they experience today and the gains they hope for. This becomes the foundation for prioritization and scope.

---

## Project details

| Field | Value |
|-------|-------|
| **System / App** | |
| **Primary Users** | |
| **Date** | |

---

## Matrix

| # | Job to be Done<br>*(What is the user trying to achieve?)* | Current Pains<br>*(Obstacles, workarounds, risks)* | Desired Gains<br>*(Outcomes that would feel like progress)* | Priority<br>*(H / M / L)* |
|---|----------------------------------------------------------|----------------------------------------------------|-------------------------------------------------------------|---------------------------|
| 1 | | | | |
| 2 | | | | |
| 3 | | | | |
| 4 | | | | |
| 5 | | | | |
| 6 | | | | |

---

## How to use the Priority column

- **H (High)** — Critical job that is frequent or high-stakes. Solving the associated pains creates immediate value.
- **M (Medium)** — Important but not daily or blocking. Good candidate for later phases.
- **L (Low)** — Nice-to-have or rare. Keep visible but protect scope.

---

## Insights & Next Steps

*After filling the matrix, note patterns: Are many pains caused by the same root issue? Which gains would create the biggest shift in how people work?*

**Patterns observed:**


**Recommended focus for the first version:**


---

*Prodora · prodora.io · Product-led software. Built to fit.*