skills/jtbd-analysis/SKILL.md
Analyze customer motivations using Jobs-to-be-Done and Forces of Progress. Use when asked about jobs-to-be-done, why customers switch products, what job a product is hired for, or when analyzing the forces that drive or resist product adoption.
npx skillsauth add assimovt/productskills jtbd-analysisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Understand why customers "hire" and "fire" products. JTBD (Christensen/Moesta) reframes competition: you're not competing against similar products, you're competing against whatever the customer currently uses to get the job done — including doing nothing.
Structure every job as: "When [situation], I want to [motivation], so I can [expected outcome]."
The situation is critical — the same person has different jobs in different contexts.
Four forces determine whether someone switches to your product. Map all four:
DRIVING ADOPTION RESISTING ADOPTION
================ ==================
Push: Pain with current solution Anxiety: Fear of the new solution
Pull: Attraction of new solution Habit: Comfort with current way
What's broken or frustrating about how they do it today? Stronger push = more urgency.
What's attractive about the new way? This is your value proposition.
What are they afraid of? Switching costs, learning curves, data migration, reliability.
What keeps them doing it the old way? Muscle memory, sunk costs, "good enough."
To win: Push + Pull must be stronger than Anxiety + Habit.
If anxiety is high, reduce it (free trials, migration tools, guarantees). If habit is strong, find the trigger moment when the current solution fails hard enough to break inertia.
Built on Jobs-to-be-Done (Clayton Christensen) and the Forces of Progress (Bob Moesta). Skills from productskills.
development
Prepare and conduct user interviews that extract truth, not validation. Use when asked to create an interview guide, prepare for user interviews, plan customer discovery, or talk to users. Built on The Mom Test and YC's Five Questions framework for startup customer development.
documentation
Write product strategy documents with real tradeoffs and clear choices. Use when asked to write a product strategy, define strategic direction, create a strategy doc, or articulate where to play and how to win. Built on Playing to Win and Rumelt's Strategy Kernel.
tools
Cut scope ruthlessly using Shape Up's appetite-first approach. Use when asked to reduce scope, find the MVP, trim features, ship faster, or figure out what to cut. Applies fixed time variable scope thinking and scope hammering techniques.
development
Create outcome-based roadmaps using Now/Next/Later instead of Gantt charts. Use when asked to create a roadmap, plan quarterly, organize milestones, or figure out what to build over the next few months. Anti-date, anti-feature-list, pro-outcome.