jtbd-analyzer
Uncover the real "job" customers hire your product to do. Goes beyond features to understand functional, emotional, and social motivations. Use when user says "jobs to be done", "jtbd", "why do customers", "what job", "customer motivation", "what problem", "user needs", "why do people buy".
What this skill does
# Jobs-To-Be-Done Analyzer ## The Core Concept Customers don't buy products. They HIRE products to do a job. "People don't want a quarter-inch drill. They want a quarter-inch hole." Actually: They want a shelf → to display photos → to feel proud of family. ## The Three Job Dimensions | Dimension | Question | Format | |-----------|----------|--------| | **Functional** | What task needs doing? | "Help me [verb] [object]" | | **Emotional** | How do I want to feel? | "Make me feel [emotion]" | | **Social** | How do I want to be seen? | "Help me be seen as [quality]" | ## The Process 1. **Job Statement:** "When [situation], I want to [motivation], so I can [outcome]" 2. **Map all 3 dimensions** for each user type 3. **Find real competition:** What ELSE could do this job? 4. **Prioritize:** Which jobs are most critical and underserved? ## Output Format ``` PRODUCT: [What you're analyzing] For [User Type]: JOB: "When [situation], I want [motivation], so I can [outcome]" 📋 FUNCTIONAL: [Task to accomplish] 💜 EMOTIONAL: [Feeling desired] 👥 SOCIAL: [Perception desired] ALTERNATIVES: [What else could do this job?] UNDERSERVED: [What part isn't done well?] PRIORITY: Critical / Important / Nice-to-have ``` ## Key Questions 1. "What were you trying to accomplish when you [action]?" 2. "Walk me through the last time you needed to [job]" 3. "What would you do if [product] didn't exist?" 4. "What's frustrating about how you currently [job]?" ## Integration Compounds with: - **first-principles-decomposer** → Decompose job to atomic need - **cross-pollination-engine** → Find how others solve similar jobs - **app-planning-skill** → Use JTBD to inform features --- See references/examples.md for Artem-specific JTBD analyses
Related in Sales & CRM
process-mapper
IncludedUse when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work — this is tactical process documentation for internal operations.
payment-integration
IncludedIntegrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.