AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

interview-mapper

Use when coding or making sense of one interview transcript (customer, JTBD, expert, usability, exit). Extracts verbatim-grounded nuggets with extract_nuggets.py, verifies quotes with verify_quotes.py and checks conclusions hold across reruns with consensus.py.

Original source
alirezarezvani
License
MIT
Pinned revision
e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read alirezarezvani--interview-mapper at revision e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 63

templates/jtbd.md

Lens: Jobs-to-be-Done (JTBD)

When: customer/user interview to understand the "job" the person "hires" the product for, and the context of the choice. Not for an employee interview about org structure. Coding unit: a statement about situation/motivation/outcome, backed by a direct quote about PAST behavior (not a hypothesis). Collection discipline: facts about the past are valuable, not opinions about the future (see The Mom Test).

Layer 1 — operational (facts + quote + line)

  • J1 Main job (job statement) — "when [situation], I want [motivation], so that [outcome]". Verb + object + context.
  • J2 Trigger / struggling moment — what made them look for a solution right then (event, deadline, breakdown).
  • J3 Job map — step by step: define/plan → locate → prepare → confirm → execute → monitor → adjust → conclude. Where it stalls.
  • J4 Current solution and workarounds — what they use now, what they "hired" before, what they dropped and why (specifically).
  • J5 Desired outcomes — measurable success criteria in the customer's words ("do X faster", "fewer errors in Y").
  • J6 Related and emotional jobs — what else gets solved along the way; the social/emotional layer ("so I don't look incompetent").

Layer 2 — analytical (conclusion + quote; CAPS keyword) — to council

  • A1 Forces of progress — PUSH (pain of the current) / PULL (draw of the new) / HABIT / ANXIETY. For each — a quote. (unstable)
  • A2 Key unmet outcome — where the gap between importance and satisfaction is greatest.
  • A3 "Hiring/firing" criterion — what actually decided the choice (not what the customer declares).
  • A4 Job-based segment — which job-segment they belong to (not demographics, but job + context).
  • A5 Adoption barrier — what prevents switching right now.
  • A6 Key insight — 1 sentence: the customer "hires" X for [job], but [force/barrier], therefore [implication for the product].

Forcing questions

Tell me about the last time you ran into this — what exactly did you do? What did you try before that? What happened on the day you decided to look for a solution? How much time/money have you already spent? Who else does this bother?