Skip to content

borghei/Claude-Skills / project-management/discovery/jtbd-workshop

jtbd-workshop

Verified

Plans and runs a 2, 4 or 8-hour Jobs-To-Be-Done workshop: switch interviews, forces of progress, scored outcome statements. Use when you need to know why customers switch, or to ground strategy in jobs before writing PRDs.

assets/workshop_agenda_8hr.md

View on GitHub
# JTBD 8-Hour Full-Day Workshop Agenda

**Format:** 8-hour full-day workshop (can be split into two 4-hour days)
**Output:** Full job hierarchy, ODI-scored outcomes, forces maps for top 3 jobs, 10-15 opportunity statements with owners
**Participants:** 6-12 (full product trio + 2-3 customer-facing roles + 1-2 exec stakeholders + at least 1 live customer for switch interview)
**Required pre-work:** 6-10 switch interview transcripts read by all participants
**Facilitator:** Pair (lead facilitator + note-taker)
**Materials:** Miro/FigJam board, printed canvases, sticky notes, timer, recording setup for live interview

---

## 0:00 - 0:30 | Welcome + JTBD Primer + Contracts (30 min)

- Round-robin intros (~45 sec each)
- Workshop goal: produce a complete JTBD foundation for [segment] -- hierarchy, outcomes, forces, opportunities
- 10-minute JTBD primer:
  - The four schools we'll combine: Christensen (hierarchy), Ulwick (outcomes), Klement (stories), Moesta (forces)
  - Definitions and the format strictness rules
- Workshop contracts:
  - Time-boxed -- the timer is the boss
  - No solutions during morning blocks
  - All output traces to customer voice
  - Disagreement is welcome; consensus is not the goal -- clarity is
  - Phones on silent during live interview

---

## 0:30 - 1:30 | Live Switch Interview (60 min, recorded)

- A customer joins (in person or remote)
- One facilitator runs the switch interview (`assets/switch_interview_script.md`)
- Other participants observe silently, take notes
- 60-minute interview with the four-anchor timeline (First Thought, Passive Looking, Active Looking, Deciding, First Use)
- Customer leaves at end

---

## 1:30 - 2:00 | Live Interview Debrief (30 min)

- Each participant writes their top 3 quotes from the interview (5 min)
- Round-robin: read out top quotes (15 min)
- Initial snippet wall: jobs, pains, gains, forces emerging from the live interview (10 min)

---

## 2:00 - 2:15 | Break (15 min)

---

## 2:15 - 3:15 | Snippet Wall from Pre-Read Transcripts (60 min)

- Participants pull additional snippets from the 6-10 pre-read transcripts (30 min)
- Each snippet on a separate sticky:
  - Job snippet (what is the customer trying to do?)
  - Pain snippet (what's bad about the current state?)
  - Gain snippet (what would be better?)
  - Force snippet (push, pull, anxiety, habit moment)
- Affinity clustering on the wall (30 min)

---

## 3:15 - 4:00 | Lunch (45 min)

---

## 4:00 - 5:00 | Build Job Hierarchy (60 min)

- From the clustered snippet wall, draft the job hierarchy (30 min):
  - One "big job" at the top (Christensen format)
  - 5-8 sub-jobs that decompose the big job
- Validate hierarchy against transcript quotes -- every sub-job must reference >=2 transcripts (15 min)
- Write Klement-format job stories for top 3 sub-jobs (15 min)
  ```
  When [situation], I want to [motivation], so I can [outcome].
  ```

---

## 5:00 - 5:45 | Decompose into Outcomes (45 min)

- Pick top 3-5 sub-jobs by importance (dot vote, 5 min)
- For each, brainstorm 5-8 desired outcomes in Ulwick format (35 min)
- Quality test each outcome (verb present? metric present? not a solution?) (5 min)
- Target: 25-40 outcomes total across the top sub-jobs

---

## 5:45 - 6:00 | Break (15 min)

---

## 6:00 - 6:45 | Score Outcomes with ODI (45 min)

- Brief refresher on Importance x Satisfaction scoring (5 min)
- Pair scoring: pairs of participants score independently (25 min)
- Reconcile pairs -> agreed score per outcome (10 min)
- Calculate opportunity scores; rank outcomes (5 min)

---

## 6:45 - 7:30 | Forces-of-Progress Maps for Top 3 Jobs (45 min)

- 15 minutes per job:
  - Push: what is bad about the current state?
  - Pull: what is attractive about the alternative?
  - Anxiety: what worries customers about switching?
  - Habit: what ties them to the current way?
- Identify the dominant force per job (which is the biggest barrier or enabler?)

---

## 7:30 - 8:00 | Synthesis: Opportunity Statements + Owners (30 min)

- Write 10-15 opportunity statements from the top-scored outcomes (15 min):
  ```
  [Verb] [object] [context] -- [outcome to achieve]
  ```
- Assign owners (named owner + 30-day next step) for top 5-10 opportunities (10 min)
- Define downstream hand-off (PRD, roadmap, experiments, assumption tests) (5 min)

---

## Post-Workshop Deliverables

Within 5 business days, facilitator produces:

- Workshop summary doc (5-10 pages)
- Job hierarchy diagram
- Outcome list with ODI scores (CSV with Importance, Satisfaction, Opportunity score)
- Forces-of-progress canvases (top 3 jobs)
- 10-15 opportunity statements with named owners and 30-day next steps
- Klement-format job stories ready for backlog
- Link to switch interview recordings and transcripts (for traceability)

Hand off downstream:

- Top opportunities -> `discovery/identify-assumptions/` (validate riskiest assumptions)
- Top opportunities -> `discovery/brainstorm-experiments/` (design tests)
- Job hierarchy + outcomes -> `execution/create-prd/` Section 5 + 6
- Top desired outcomes -> `execution/outcome-roadmap/` (become roadmap themes)
- Job stories -> `execution/job-stories/` for backlog decomposition
- Jobs + outcomes -> `execution/north-star-metric/` (top outcome often becomes the NSM input)

---

## Optional Two-Day Split

If 8 hours in one day is impractical:

**Day 1 (4 hours):** Welcome + primer + live interview + debrief + snippet wall
**Day 2 (4 hours):** Job hierarchy + outcome decomposition + ODI scoring + forces + synthesis

Schedule Day 2 within 5 business days of Day 1 to retain context.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall