Jobs To Be Done Analyzer

**Judgement:** A strong, focused JTBD analysis skill that is well-scoped and practically useful for product, UX, and marketing work. It provides a clear structure (situation → motivation → outcome, plus functional/emotional/social breakdown) that should help transform vague “why do customers use this?” questions into actionable, comparable job statements. **Strengths & likely value:** - Well-aligned with common product discovery workflows; the output format is concrete and easy to plug into docs, roadmaps, and positioning work. - Explicitly calls out alternatives and underserved aspects of the job, which is where a lot of strategic insight typically comes from. - Good fit for early-stage product definition, refining feature briefs, and synthesizing qualitative input (e.g., interviews, feedback, support tickets). **Key risks / limitations:** - Risk of “armchair JTBD”: if prompts don’t include real customer data, the skill may produce plausible but unvalidated motivations and jobs. - May oversimplify complex multi-stakeholder situations into a single user type or job if the user doesn’t specify segments clearly. - Prioritization (Critical / Important / Nice-to-have) is qualitative and may look more authoritative than it actually is without supporting evidence. **Best-fit scenarios (recommended use):** - Early product discovery, when teams are trying to move from feature ideas to problem/need framing. - Reframing existing features or products in terms of underlying jobs to improve messaging and positioning. - Preparing discussion guides or hypothesis lists before conducting customer interviews. - Creating concise JTBD summaries to align cross-functional teams (PM, design, marketing, sales) around what customers are really trying to accomplish.