jobs-to-be-done-extractorlisted

# Jobs-to-be-Done Extractor > Reframes the product around the job the customer is hiring it to do. ## What this skill is A workflow that turns unstructured customer research into Jobs-to-be-Done (JTBD) artifacts: functional, emotional, and social job statements; a job map; force diagrams (push / pull / habit / anxiety); outcome statements; and a hire / fire analysis. Built on the Outcome-Driven Innovation (ODI) school of Anthony Ulwick and the milkshake school of Clayton Christensen, with explicit handling of overserved versus underserved outcomes. ## What it solves - Persona-based segmentation that doesn't predict purchase behavior - Roadmaps driven by feature requests instead of customer outcomes - Marketing copy that lists features but doesn't connect to the job - Switching analysis that ignores the four forces (push, pull, habit, anxiety) - Inconsistent JTBD interpretations across product, marketing, and sales ## When to invoke - Synthesizing customer interviews, switching interviews, or win-loss calls - Re-segmenting the market beyond firmographics - Building positioning or messaging that resonates with the actual job - Prioritizing the roadmap by underserved outcome importance - Aligning product, marketing, sales, and customer success on a shared customer model ## Phase 1: Source the raw material Catalog what you have: - Customer interview transcripts (switching, churn, win-loss, discovery) - Sales call recordings plus notes - Support tickets and Customer Satis