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/pre_work_email.md

View on GitHub
# JTBD Workshop Pre-Work Email Template

Send this email 5-7 days before the workshop. Participants should arrive having read the assigned transcripts and reflected on the warm-up questions.

---

**Subject:** Pre-work for [Date]'s JTBD workshop -- 30 min reading + reflection

Hi team,

We're running a [2-hour / 4-hour / 8-hour] Jobs-To-Be-Done workshop on **[Date]** at **[Time]** in **[Location/Link]**. The output will be:

- A validated job hierarchy for our [segment] customers
- ODI-scored desired outcomes
- A forces-of-progress map for our top job(s)
- 5-15 opportunity statements with owners

To make the workshop time count, please complete the following 30 minutes of pre-work:

---

## 1. Read 2-3 customer switch interview summaries (~20 min)

Attached / linked below are switch interview summaries from customers who recently switched to (or away from) our product. Read carefully -- the entire workshop is grounded in these voices.

- **[Customer 1 -- segment / role]:** [link or attachment]
- **[Customer 2 -- segment / role]:** [link or attachment]
- **[Customer 3 -- segment / role]:** [link or attachment]

As you read, mark:

- The moment the customer first realized they needed something different (the "first thought")
- What pushed them toward switching (push of the situation)
- What pulled them to the alternative (pull of the new solution)
- What worried them about switching (anxiety)
- What kept them tied to the current way (habit)

---

## 2. Reflect on these warm-up questions (~10 min)

Bring written notes to the workshop:

1. In one sentence, what is the [segment] customer trying to *get done* when they use our product? (Avoid feature language.)
2. Name three things customers tell us they want -- and the *underlying outcome* each one points to.
3. From the transcripts, what surprised you about how customers describe their job? Anything that contradicts our internal assumptions?

---

## 3. Workshop ground rules to keep in mind

- We are not solving problems on workshop day. Solution-mode is banned during morning blocks.
- All output must trace to customer voice. If we cannot find a transcript quote for a claim, we mark it as an assumption to validate.
- Demographic framing ("enterprise customers", "millennials") will be redirected to job framing ("customers trying to close the books in 5 days").
- Timeboxes are firm. The timer is the boss.

---

## 4. What to bring

- Your notes from the pre-read
- A laptop (we'll use Miro/FigJam) OR be prepared for in-person sticky notes
- A coffee, and an open mind

---

## Logistics

- **Date:** [Date]
- **Time:** [Time -- include timezone]
- **Location:** [Room / Zoom link]
- **Facilitator:** [Name]
- **Workshop length:** [2 / 4 / 8 hours]
- **Break schedule:** [Brief / Mid-point / Lunch + breaks for 8hr]

Questions? Reply or ping me directly.

Thanks for investing the prep time -- it makes the workshop work.

[Facilitator name]

---

## Pre-Work Checklist (for facilitator)

Before sending the email:

- [ ] Switch interview transcripts collected (minimum 4 for 4hr, 6+ for 8hr)
- [ ] Transcripts summarized (1-page summaries are easier to read than 60-min transcripts)
- [ ] Identifying details redacted (customer name, company name, sensitive info)
- [ ] Calendar holds sent to all participants
- [ ] Workshop board (Miro/FigJam) set up with templates
- [ ] Live interview customer confirmed (8hr format)
- [ ] Recording consent secured (live interview, 8hr format)
- [ ] Lunch ordered (8hr format)
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