# Problem Atlas Template

A problem-driven roadmap tool designed to help teams prioritize with evidence, pain, reach, and business value—not requests or guesses. Copy, adapt, and make it your own.

---

## 1. Problem Statement (Clear, Solution-Free)

Write **what hurts**, not what fixes it.

**Not:**
“Customers need SMS.”

**But:**
“Practices lose 18% of appointments to no-shows, costing $2,400/month in lost revenue, primarily due to lack of confirmation visibility.”

**How to check yourself:**
Read it aloud without naming *any* technology or feature.
If you can’t, it’s a solution in disguise.

We’re trained to jump to answers. Resist.

---

## 2. Evidence Level (How Validated Is This?)

Rate how confident you are based on real discovery work:

* ★☆☆☆☆ **Hypothesis** — We think this hurts.
* ★★☆☆☆ **Initial Signal** — A few customers mentioned it.
* ★★★☆☆ **Validated** — Interviews confirm it; pattern clear.
* ★★★★☆ **Deep** — Observed in action; quantified impact; workarounds documented.
* ★★★★★ **Rooted** — Root causes understood; edge cases mapped; ready for responsible solution design.

**Why this matters:**
This forces honesty. Most teams say “validated” when one customer complained once.

---

## 3. Pain Metrics (How Much Does It Hurt?)

Three numbers tell the story:

* **Frequency:** How often does this bite? Daily? Monthly? Only at scale?
* **Severity:** How much does it cost when it happens? Time, money, frustration?
* **Workaround Cost:** What do customers spend today trying to cope?

**Example (Hypothetical):**

* Frequency: Every month-end close
* Severity: 90 minutes of manual processing
* Workaround: Staff stay late; practice pays overtime ($240/month)

The workaround cost is the hidden one.
If customers are already spending to solve it themselves, it’s real.

---

## 4. Reach (Who Feels This?)

Record who is affected, and how deeply:

* % of all customers
* % of ICP (ideal customers)
* Segments most affected

**Why this matters:**
Some problems touch many users shallowly.
Others hit a smaller group—your target buyers—*deeply*.
The latter are far more valuable to solve.

---

## 5. Business Value (What’s It Worth?)

Not “this would be cool.” Be concrete:

* **Revenue at risk:** How much ARR is threatened if unsolved?
* **Revenue unlocked:** Expansion or new sales this enables
* **Cost avoided:** Support tickets, churn, manual workarounds
* **Strategic value:** Does solving this unlock other problems, create a moat, or open segments?

**Example (Hypothetical):**

* Retention risk: $[AMOUNT] ARR ([NUMBER] customers considering churn)
* New sales: $[AMOUNT] pipeline blocked by this
* Support cost: [NUMBER] hrs / month of tickets
* Strategic: Unlocks enterprise segment (required for purchase)

This is where you stop being a feature factory and start being a business.

---

## 6. Stage (Where Are We?)

Stage = how well you understand the problem.
(Not “planned / in progress / done.”)

Choose one:

* **Hypothesis** — We think this is painful
* **Discovery** — Interviewing customers; validating
* **Validated** — Confirmed real and worth solving
* **Solution Design** — Exploring how to solve it
* **Building** — Implementation in progress
* **Validating Solution** — Shipped to beta; measuring impact
* **Solved** — Live; adopted; metrics improved

**Key insight:**
You can be “building” and still be in the *hypothesis* stage.
That’s how teams waste months.

---

## How to Use This Template

For each problem, create an entry with these six elements:

1. Problem Statement
2. Evidence Level
3. Pain Metrics
4. Reach
5. Business Value
6. Stage

Your Atlas becomes a map of real problems, not a wishlist of features. It helps prioritize based on pain, value, and confidence rather than loud opinions or competitor checklists.