nw-jtbd-core

Explain JTBD theory and templates for structuring product discovery.

Updated Mar 18, 2024
One-click install
npx skills add https://github.com/v1bh0r/precise-ledger-pro --skill nw-jtbd-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nw-jtbd-core
Source: https://github.com/v1bh0r/precise-ledger-pro/tree/main/nWave/skills/nw-jtbd-core
Command: npx skills add https://github.com/v1bh0r/precise-ledger-pro --skill nw-jtbd-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Jobs-to-be-Done reframes product development around the progress customers seek rather than the products they buy. Customers "hire" products to accomplish specific jobs, and the job exists independently of any solution.

Core Features & Use Cases

  • Three Job Dimensions: Functional, Emotional, and Social jobs surface during discovery.
  • Job Story Format & Translation Pipeline: Move from situation-driven prompts to implementable user stories and acceptance criteria.
  • The 8-Step Universal Job Map: Guides teams through Define, Locate, Prepare, Confirm, Execute, Monitor, Modify, and Conclude stages.
  • Outcome Statements & Forces of Progress: Define measurable outcomes and the push/pull forces that drive decisions.
  • Cross-References & Workflow Integration: Connect JTBD analysis to interview techniques, opportunity scoring, BD/BDD integration, and persona work.

Quick Start

Outline the three job dimensions for a target user and draft a concrete Job Story using the 8-step universal job map to structure your discovery.

Frequently Asked Questions about nw-jtbd-core

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is Jobs-to-be-Done theory in product management?

Jobs-to-be-Done theory reframes product discovery around the progress customers seek rather than the products they buy, classifying customer needs into functional, emotional, and social job dimensions.

How do I write a job story for product discovery?

To write a job story, use the situation-driven translation pipeline to move from customer prompts into implementable user stories and acceptance criteria, defining the specific progress the user seeks.

How do I use a universal job map to structure opportunity scoring?

Use the 8-step universal job map to guide opportunity scoring through Define, Locate, Prepare, Confirm, Execute, Monitor, Modify, and Conclude stages, mapping customer progress across the entire workflow.

What are forces of progress in JTBD analysis?

Forces of progress in JTBD analysis define the push and pull forces driving customer decisions, helping product managers understand the underlying dynamics of adopting a new solution.

When should I use outcome statements instead of user stories?

Use outcome statements during opportunity scoring to define measurable outcomes, then use the translation pipeline to convert situation-driven job stories into actionable user stories and acceptance criteria.

Does JTBD framework work with existing persona work and interview techniques?

Yes, JTBD analysis integrates with existing persona work and interview techniques, providing cross-references to connect customer progress insights directly into your current product strategy workflow.