# 📈 Case studies & ROI

The fastest way to judge a tool is *"what did it save someone like me?"* This page collects
real, attributed stories of time and effort saved with PM Skills — and the template to add yours.

> **Status — building this with real data.** The entries below the line are **illustrative
> templates** (composite scenarios, *not* customer quotes) that show the format and the kind of
> outcome to expect. They're placeholders to be replaced with **real, named stories** as people
> submit them — see [Add your story](#add-your-story). Nothing here is presented as a testimonial
> from a real person until it is one.

## The shape of the win

The pattern is consistent: the skill removes the *blank page and the structure debate*, so you
spend your time on judgement, not formatting.

| Deliverable | Typical "before" | With the skill | What changed |
|---|---|---|---|
| PRD | ~1–2 days (drafts, template hunts, reviews) | ~20–30 min to a reviewable draft | structure + success metrics + risks are already there |
| Incident postmortem | half a day, often skipped | ~15 min | blameless structure, timeline, action items with owners |
| QBR / board deck | 2–4 hours | ~20 min | narrative + slide-by-slide storyline from the numbers |
| Exec update | 30–60 min of rewriting | ~5 min | tight, audience-tuned, 250 words |

> Treat these as *ranges to validate with your own runs*, not guarantees — they depend on your
> inputs and review bar. The honest pitch isn't "10x faster"; it's "a shippable first draft
> instead of one you redo."

---

## Featured stories

> ⬇ **Illustrative templates** — replace with real submissions. Format = Role · Skill · Before → After · Quote.

### 1. From a fuzzy idea to a reviewable PRD — *(illustrative)*
- **Who:** Senior PM, B2B SaaS *(illustrative — replace with a real submitter)*
- **Skill:** [`prd-template`](skills/prd-template/) (+ [`rice-prioritisation`](skills/rice-prioritisation/))
- **Before → After:** ~2 days of drafting and template-wrangling → **~25 minutes** to a draft engineering could review.
- **Quote:** *"[Replace with a real one-line quote about the outcome.]"*

### 2. Postmortems that actually happen — *(illustrative)*
- **Who:** Eng lead, fintech *(illustrative)*
- **Skill:** [`incident-postmortem`](skills/incident-postmortem/)
- **Before → After:** postmortems were skipped under time pressure → **~15 minutes**, so they get written every time.
- **Quote:** *"[Replace with a real quote.]"*

### 3. The quarterly story, in one sitting — *(illustrative)*
- **Who:** Founder / Head of Product *(illustrative)*
- **Skill:** [`qbr-deck`](skills/qbr-deck/) (+ [`executive-update`](skills/executive-update/))
- **Before → After:** ~3 hours assembling the narrative → **~20 minutes** to a slide-by-slide storyline.
- **Quote:** *"[Replace with a real quote.]"*

---

## Add your story

Saved time with a skill? **[Submit a 2-minute ROI story →](../../issues/new?template=roi-story.yml)**
(or open a [Discussion](../../discussions)). With your permission we'll feature it here, on the
site, and in the README — credited to you and your team.

What makes a story land:
- A **concrete before → after** (hours/days, not "faster").
- The **specific skill(s)** you used.
- One honest sentence on **what it changed** (and any rough edges).

> Want it measured, not just claimed? Every skill is also **[eval-scored on a public
> rubric](https://mohitagw15856.github.io/pm-claude-skills/leaderboard.html)** — that's the
> quantitative half; these stories are the qualitative half.
