What problem does it solve? Tiny teams (1-5 people) often lack the resources for traditional primary user research, leaving them guessing about what users actually want. This sub-skill applies Jobs-to-Be-Done methodology to secondary research sources, producing structured job statements, switch force analyses, and job maps that shift thinking from features to user motivations. ## Core Features & Use Cases - Job Statement Synthesis: Produces canonical job statements in the format "When [situation], I want to [motivation], so I can [expected outcome]" classified as functional, social, or emotional. - Switch Force Analysis: Applies the Moesta/Spiek four forces model (push, pull, anxiety, habit) with 1-5 ratings and net force calculation to explain switching behavior. - Outcome-Driven Innovation Scoring: Uses Ulwick's ODI formula (Importance + max(Importance - Satisfaction, 0)) to identify underserved outcomes and innovation opportunities. - Use Case: A three-person startup wants to understand why users abandon their onboarding flow. The ux-jtbd-analyst synthesizes competitor reviews and domain literature into a JTBD report with job maps, hiring criteria, and opportunity scores, flagging all findings as MEDIUM confidence pending validation. ## Quick Start Ask the /user-experience skill to map the jobs to be done for your product's onboarding flow, and the ux-orchestrator will route the request to ux-jtbd-analyst.
