hermes-agent/optional-skills/creative/creative-ideation/references/methods/jobs-to-be-done.md
SHL0MS d799284b15
feat(optional-skills/creative-ideation): expand to v2.1.0 method library (#42402)
The optional-skills copy was still the v1.0.0 constraint-dispatch skill
(SKILL.md + full-prompt-library.md only). This brings it up to the current
tool: a situation-routed library of 22 named ideation methods drawn from
working artists, scientists, designers, and writers.

SKILL.md becomes a 4-step router (extract PHASE/DOMAIN/SPECIFICITY signals
→ apply overrides → route phase-then-domain → resolve ambiguity), with
anti-slop operating rules and an anti-default check.

Adds:
- 22 method files under references/methods/ — oblique-strategies (Eno/Schmidt),
  oulipo, scamper, lateral-provocations (de Bono), triz (Altshuller),
  leverage-points (Meadows), pattern-languages (Alexander), compression-progress
  (Schmidhuber), analogy-and-blending, pataphysics, first-principles, polya,
  biomimicry, volume-generation, creative-discipline, premortem-and-inversion,
  defamiliarization, derive-and-mapping, affinity-diagrams, jobs-to-be-done,
  story-skeletons, chance-and-remix. Each: when/when-not, the actual
  cards/principles/operators, a procedure, a worked example, anti-slop notes.
- references/method-catalog.md (index + when-to-use), heuristics.md (extended
  decision tree), anti-slop.md (rules applied to every output), exercises.md
  (time-boxed exercises).
- full-prompt-library.md restructured into domain-affinity sections (general /
  software / physical / social / lists) so the no-direction default isn't
  developer-biased.

Frontmatter: name aligned to directory slug (creative-ideation, folding in
the fix from #18084); version 2.0.0→2.1.0; platforms field preserved.

Original wttdotm-derived constraint dispatch is kept as the default path.
Supersedes #19295 (which targeted the pre-move skills/ path).

Co-authored-by: SHL0MS <[email protected]>
2026-06-19 15:40:02 -07:00

73 lines
3.9 KiB
Markdown

# Jobs to Be Done
Clayton Christensen et al., *Competing Against Luck* (HarperBusiness, 2016). Customers don't buy products based on demographics — they "hire" products to do specific jobs in specific situations.
## When to use
- Product / service / business design
- Differentiation from competitors (the real competitor is whatever currently does the job — often non-obvious)
- Failure analysis (a product that "should have worked" often was designed for a job customers don't have)
- Pricing (price in the unit of the job, not the cost of the product)
- Marketing copy (speak to the job, not the features)
## Don't use when
- Artistic or expressive work — "what job is this novel hired to do?" collapses what makes it specific
- Civic / social design — imports market logic that's wrong here
- Pure-research questions (no customer, no hire — use compression-progress)
- You don't have access to actual customers
## Core form
State the job as: **"When [situation/trigger], I want to [motivation], so I can [expected outcome]."**
The form forces specificity. Generic jobs ("when I want to be productive") are slop. Specific situations ("when I'm finishing a paper at 11pm and need a citation") are real.
## The four forces of switching (Bob Moesta)
A customer changes from one solution to another when **(push + pull) > (anxiety + habit)**:
1. **Push** of the situation — pain of current.
2. **Pull** of the new solution — appeal of where they're moving.
3. **Anxiety** about the new solution — fears it'll let them down.
4. **Habit** of the present — inertia.
Most failed product launches don't lose on (2). They have an excellent product. They lose on (3) and (4): unaddressed anxieties + inertia. **Design for forces 3 and 4, not just 2.**
## Switch-interview procedure
Talk to someone who recently switched to your category, or recently bought it for the first time. Recency matters; memory degrades.
Walk the timeline:
- When did you first realize you needed something different? (Be specific: time of day, where, what had just happened.)
- What did you try first? Why didn't it work?
- What were the alternatives?
- When did you decide on this product?
- What were you afraid would go wrong?
- What was the moment of "I'm going to buy this"?
Then identify the job ("When... I want to... so I can...") and the four forces.
## Worked example
*Switch from Mendeley to Zotero* (academic citation manager):
- Push: Mendeley sync failed for 6 months; lost references.
- Pull: Zotero free, open source, recommended by colleague.
- Anxiety: losing 6 years of notes.
- Habit: comfort with Mendeley UI.
- Buying moment: colleague's library imported cleanly with notes preserved.
**Job**: "When my reference manager fails me and I have years of accumulated work in it, I want to migrate to a new tool without losing my notes, so I can stay productive on my research."
**Design implication**: a citation manager whose strongest pitch is *migration*, not features. Killer feature: "import from anywhere with notes preserved." Verified import quality from each major competitor. Reverse-migration tool. All addresses force 3 (anxiety) and force 4 (habit) — what most competitors neglect. The *features* (citation management) are barely differentiating. The *migration* is the product.
## Anti-slop notes
- Generic jobs ("customers want to feel valued") are not jobs; they're platitudes. Real jobs tie to specific situations and outcomes.
- Don't fabricate switch-interview data. If you don't have customers, acknowledge the limit and recommend running real interviews.
- Don't apply JTBD to artistic, research, or civic work. It's a market-logic tool.
- Don't reduce humans to job-doers. JTBD is useful for purchase decisions; not all human behavior.
- The "hired to do a job" can become catechism. Use where it fits; don't import where it doesn't.
Source: Christensen et al., *Competing Against Luck* (HarperBusiness, 2016); Moesta, *Demand-Side Sales 101* (Lioncrest, 2020).