jtbd

To identify Jobs to be Done for different customer segments, you formulate JTBD statements in the "When I..., I want to..., So I can..." format for each target segment to clarify user needs and desired outcomes.

Yes, you can run simulated customer interviews that emulate both interviewer and persona roles to surface real-world context, pain points, and buying triggers for each segment without needing real respondents.

The best way to document JTBD insights for downstream product discovery is to produce structured outputs like context.yaml files and interview summaries that capture segment pains and triggers for product decisions.

Segment analysis for JTBD statements works by evaluating each target segment individually, simulating end-to-end customer interviews to surface specific context and insights, and documenting unique jobs for each segment.

No, you do not need real customer data to generate context.yaml files for JTBD analysis because the Skill simulates complete customer interviews with personas to produce structured outputs independently.

You should use simulated customer interviews when you need to rapidly surface segment pains, triggers, and insights to feed downstream product discovery before investing resources in real customer interviews.