Agent skill · product strategy · borghei
jtbd-workshop
Run a full Jobs-To-Be-Done discovery workshop with switch interviews, forces-of-progress mapping, ODI outcome scoring, and opportunity statements across 2hr, 4hr, and 8hr formats.
Why this skill is useful
Provides structured methodologies and templates for conducting JTBD workshops that the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
JTBD Workshop Expert Overview Run a Jobs-To-Be-Done (JTBD) workshop end-to-end. This skill is the workshop facilitation companion to the execution/job-stories/ skill (the writing format for backlog stories). Where job-stories/ produces When/Want/So statements for individual backlog items, this skill produces the upstream discovery output -- the job hierarchy, the forces driving switching behavior, and the desired-outcome statements that anchor product strategy. The workshop synthesizes four JTBD schools: Christensen's milkshake hiring frame, Ulwick's Outcome-Driven Innovation (ODI) with importance/satisfaction scoring, Klement's situation-motivation-outcome canvas (the job story format), and Moesta's switch interview method surfacing the four forces of progress (push, pull, anxiety, habit). A well-run workshop produces three artifacts: a ranked job hierarchy with measurable outcome statements, a forces-of-progress map, and a prioritized opportunity list ready to feed PRDs, OKRs, or roadmap themes. Core Capabilities Workshop facilitation -- 2hr / 4hr / 8hr agendas with time-blocked outcomes Switch interviews -- four-anchor timeline script (First Thought -> Passive -> Active -> Deciding -> First Use) Forces-of-progress mapping -- push, pull, anxiety, habit canvas and the switch equation ODI outcome scoring -- Ulwick outcome statements with Importance x Satisfaction opportunity scores Handoff -- opportunity statements into assumptions, experiments, PRDs, and roadmap themes When to Use New product or new segment. Understand the underlying progress customers are trying to make before building. Pivot or strategy reset. Team is stuck debating features; re-ground in the customer's job. Pre-roadmap. Define the job hierarchy before committing to a quarterly or annual roadmap. Stalled adoption. Customers signed up but did not retain; switch interviews reveal which forces went wrong. Onboarding a new product team. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/jtbd-workshop