jtbd-interviewer

Conduct structured Jobs-to-be-Done interviews using the Four Forces framework.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/zivtech/joyus-desktop --skill jtbd-interviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jtbd-interviewer
Source: https://github.com/zivtech/joyus-desktop/tree/main/.claude/skills/jtbd-interviewer
Command: npx skills add https://github.com/zivtech/joyus-desktop --skill jtbd-interviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the common product discovery failure where teams prioritize features without understanding the causal narrative behind why customers switch to or from a solution.

Core Features & Use Cases

  • Four Forces Framework: Systematically tracks Push, Pull, Anxiety, and Habit to uncover the true drivers of user behavior.
  • Timeline Reconstruction: Guides the conversation to map the purchase story from the first moment of struggle to the final decision.
  • Use Case: Use this skill when you need to conduct a live qualitative interview with a customer who recently switched to your product to identify their specific struggling moments and desired outcomes.

Quick Start

Initiate a JTBD switching interview with the participant by asking them to describe the timeline of events leading up to their decision to switch solutions.

Frequently Asked Questions about jtbd-interviewer

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

FAQPage Schema
What is a Jobs-to-be-Done switching interview?

A Jobs-to-be-Done switching interview uncovers the causal narrative behind why customers switch solutions, systematically tracking push, pull, anxiety, and habit factors to reveal true behavioral drivers.

How do I conduct a JTBD interview to understand user switching behavior?

To conduct a JTBD interview, guide the participant through timeline reconstruction from their first moment of struggle to the final decision, applying the Four Forces framework to identify push, pull, anxiety, and habit factors.

When should I use the Four Forces framework for product discovery?

Use the Four Forces framework during qualitative product discovery when you need to conduct a live interview with a customer who recently switched solutions to identify their specific struggling moments and desired outcomes.

Can I use this approach for customer development and qualitative user research?

Yes, you can apply this structured interview approach to qualitative user research and customer development workflows to move beyond feature requests and understand the underlying causal narrative of user decisions.

How do I start a JTBD switching interview with a participant?

Initiate the interview by asking the participant to describe the timeline of events leading up to their decision to switch solutions, which begins mapping their purchase story and struggling moments.

What are the limitations of the Four Forces framework in user research?

The Four Forces framework is limited to qualitative discovery and requires a live interview with a participant who recently switched solutions, making it unsuitable for quantitative validation or users without direct switching experience.