codymaster 4.4.4 → 4.5.1

package/skills/jobs-to-be-done/references/innovation-process.md

@@ -1,392 +0,0 @@
-# JTBD Innovation Process
-
-Systematic methodology for discovering jobs and translating them into successful innovations.
-
-## Job Hunting: Finding Undiscovered Jobs
-
-### Where Jobs Hide
-
-Jobs worth pursuing are often invisible because:
-- Customers don't articulate them (they've adapted)
-- Existing categories obscure them (you see products, not jobs)
-- Data shows behavior, not motivation
-
-### Five Sources of Job Discovery
-
-#### 1. Workarounds and Compensating Behaviors
-
-**Signal:** People combine products, modify them, or create DIY solutions.
-
-**What to look for:**
-- Products used in unintended ways
-- Multiple products combined to complete one job
-- Time-consuming manual processes
-- Spreadsheets and duct-tape solutions
-
-**Interview questions:**
-- "Walk me through how you handle [situation] today"
-- "What's frustrating about your current approach?"
-- "What have you tried that didn't work?"
-- "If you could wave a magic wand, what would change?"
-
-**Example:** Milkshake study discovered people "hiring" milkshakes for morning commutes—a workaround for boredom and hunger that bananas and bagels couldn't solve.
-
-#### 2. Non-Consumption
-
-**Signal:** People who should be using a solution but aren't.
-
-**Why people don't consume:**
-| Barrier | Example |
-|---------|---------|
-| Too expensive | Can't afford financial advisor |
-| Too complicated | Can't figure out video editing |
-| Too time-consuming | Can't commit to full course |
-| Requires expertise | Can't navigate tax code |
-| Socially unacceptable | Embarrassed to seek help |
-
-**What to look for:**
-- Markets that seem "maxed out" but have huge populations not participating
-- People who have "given up" on a category
-- Simpler alternatives that attract non-users
-
-**Interview approach:**
-- "Have you ever considered [category]? Why or why not?"
-- "What would make you try something in this area?"
-- "What have you heard about [category] that put you off?"
-
-**Example:** Southern New Hampshire University found millions of adults who wanted degrees but couldn't attend traditional college—a massive non-consumption opportunity.
-
-#### 3. Negative Emotions
-
-**Signal:** Frustration, anxiety, fear, or embarrassment around a situation.
-
-**Emotions that signal jobs:**
-- Frustration → Job not being done well
-- Anxiety → Risk of job failure
-- Embarrassment → Social dimension unmet
-- Overwhelm → Job too complex
-
-**Interview questions:**
-- "What's the hardest part about [situation]?"
-- "When do you feel frustrated with [current solution]?"
-- "Is there anything you avoid or dread?"
-- "What keeps you up at night about [area]?"
-
-**Example:** SNHU discovered adult students' real struggle wasn't academics—it was fear of failure and embarrassment about going back to school.
-
-#### 4. Unusual Uses and Surprising Customers
-
-**Signal:** Customers using your product in unexpected ways, or unexpected customer segments.
-
-**What to investigate:**
-- Customer segments you didn't target who are buying
-- Features used differently than intended
-- Complaints that reveal hidden jobs
-- Support tickets that reveal actual use cases
-
-**Questions to ask:**
-- "What made you choose us over [expected alternative]?"
-- "What were you using before? What was wrong with it?"
-- "What job are you really hiring us to do?"
-
-**Example:** Arm & Hammer discovered baking soda was being "hired" for odor absorption, carpet cleaning, and toothpaste—jobs far beyond baking.
-
-#### 5. Moments of Struggle
-
-**Signal:** Specific circumstances where existing solutions fail.
-
-**The Timeline Interview:**
-
-```
-First thought → Passive looking → Active search → Decision → Purchase → Experience
-```
-
-**Questions for each stage:**
-
-| Stage | Questions |
-|-------|-----------|
-| First thought | "When did you first realize you needed something? What was happening?" |
-| Passive looking | "What alternatives did you notice? Why did you dismiss them?" |
-| Active search | "What made you start actively looking? What criteria mattered?" |
-| Decision | "What tipped you over the edge to decide? What almost stopped you?" |
-| Experience | "Is it doing what you expected? What surprised you?" |
-
----
-
-## Passive vs. Active Job Seeking
-
-### Passive Seeking
-
-Customer is vaguely aware of a problem but not actively looking for solutions.
-
-**Characteristics:**
-- Haven't allocated budget
-- Haven't carved out time
-- Open to being educated
-- Easier to influence (no preconceptions)
-
-**Marketing implications:**
-- Content marketing to raise awareness
-- Focus on problem articulation
-- Lower competition for attention
-
-### Active Seeking
-
-Customer is actively shopping for a solution.
-
-**Characteristics:**
-- Researching options
-- Set budget (often)
-- Clear criteria
-- Comparing alternatives
-
-**Marketing implications:**
-- More competitive
-- Focus on differentiation
-- Demonstrate superior job completion
-
-**Key insight:** The best customers are often passive seekers whose jobs you've awakened. They're not shopping—they're discovering they have a need.
-
----
-
-## The Job Atlas
-
-A comprehensive map of a customer's job ecosystem.
-
-### Elements of the Atlas
-
-**1. Main Job**
-The primary progress the customer wants to make.
-
-**2. Related Jobs**
-Adjacent jobs that cluster with the main job.
-
-Example (financial planning):
-- Main job: Retire comfortably
-- Related: Protect family if I die, fund kids' education, manage taxes
-
-**3. Emotional Jobs**
-How they want to feel during and after.
-
-**4. Social Jobs**
-How they want to be perceived by others.
-
-**5. Consumption Chain Jobs**
-Jobs at each stage of using your product:
-
-| Stage | Jobs |
-|-------|------|
-| Purchase | Find trusted option, feel confident in choice |
-| Setup | Get started quickly, not feel stupid |
-| Use | Accomplish task, save time |
-| Maintain | Keep it working, not waste money |
-| Upgrade | Stay current, not fall behind |
-| Dispose | Get rid of easily, recoup value |
-
-### Building Your Atlas
-
-1. Interview 10-20 customers using timeline methodology
-2. Map all jobs mentioned across interviews
-3. Cluster related jobs
-4. Identify which jobs are served/underserved
-5. Prioritize based on importance and satisfaction gap
-
----
-
-## Prototype Testing Through the JTBD Lens
-
-### Testing for Job Completion, Not Features
-
-**Wrong question:** "Do you like this feature?"
-**Right question:** "Does this help you accomplish [job]?"
-
-### Prototype Testing Framework
-
-**1. Simulate the circumstances**
-
-Don't test in a vacuum. Recreate the context where the job arises.
-
-- Wrong: "Here's a new budgeting app. What do you think?"
-- Right: "Imagine it's the end of the month and you're worried about overspending. Here's what you'd see..."
-
-**2. Measure job completion**
-
-| Metric | What It Shows |
-|--------|---------------|
-| Can they complete the job? | Functional adequacy |
-| How long does it take? | Efficiency |
-| How do they feel during? | Emotional dimension |
-| Would they show others? | Social dimension |
-| Would they do it again? | Repeat hire likelihood |
-
-**3. Test the full experience**
-
-Not just the core product—test the entire "hiring" and "using" experience:
-- Finding and understanding the product
-- Purchasing/signing up
-- First use
-- Ongoing use
-- Moments of difficulty
-
-**4. Compare to current "hires"**
-
-"Would you fire your current solution for this?"
-
----
-
-## Job Statements: The Right Level of Abstraction
-
-### Too Narrow
-
-"I want to create a to-do list"
-
-**Problem:** Focuses on solution, not job. Misses why they want a list.
-
-### Too Broad
-
-"I want to feel productive"
-
-**Problem:** Too vague to build for. Hundreds of solutions could apply.
-
-### Just Right
-
-"When I'm overwhelmed with tasks and don't know where to start, I want to see my priorities clearly so I can focus on what matters and feel in control of my day."
-
-### The Litmus Test
-
-A good job statement should:
-1. Be solution-agnostic (no product names)
-2. Include circumstances
-3. Include functional, emotional, and social dimensions
-4. Be specific enough to build for
-5. Be abstract enough to allow innovation
-
----
-
-## From Job to Innovation
-
-### Step 1: Define the Job Clearly
-
-Use the job statement format:
-```
-When _____________ [circumstances]
-I want to _____________ [progress]
-So I can _____________ [outcome]
-```
-
-### Step 2: Map Current "Employees"
-
-What do people currently hire to do this job?
-- Direct competitors (same category)
-- Indirect competitors (different category, same job)
-- Non-consumption (doing nothing)
-- DIY/workarounds
-
-### Step 3: Identify Performance Gaps
-
-Where do current solutions fall short?
-
-| Dimension | Current Solution | Gap |
-|-----------|------------------|-----|
-| Functional | Mostly works | Takes too long |
-| Emotional | Creates anxiety | Want to feel confident |
-| Social | Embarrassing | Want to look smart |
-
-### Step 4: Design for the Gap
-
-Build experiences that address unmet dimensions.
-
-**Questions:**
-- How can we do the functional job faster/better/cheaper?
-- How can we make the emotional experience better?
-- How can we help with the social dimension?
-
-### Step 5: Test Against the Job
-
-Return to customers:
-- "Does this help you make the progress you wanted?"
-- "Would you fire your current solution for this?"
-- "What's still missing?"
-
----
-
-## Common Innovation Traps
-
-### The Feature Factory Trap
-
-**Symptom:** Shipping features without connecting them to jobs.
-
-**Fix:** Every feature must answer: "What job does this help complete?"
-
-### The Correlation Trap
-
-**Symptom:** "Our best customers are women 25-34, so let's target them."
-
-**Problem:** Demographics correlate with jobs but don't explain them.
-
-**Fix:** Find the job that women 25-34 happen to have, then target anyone with that job.
-
-### The Technology-First Trap
-
-**Symptom:** "We built this cool AI—let's find a use case."
-
-**Fix:** Start with jobs, then ask if your technology serves them better.
-
-### The Competitor-Copying Trap
-
-**Symptom:** "Competitor added X, so we should too."
-
-**Fix:** Ask what job X serves. If that's not your customers' priority job, don't copy.
-
----
-
-## Job Discovery Interview Guide
-
-### Preparation
-
-- Recruit recent purchasers (within 1-2 weeks)
-- 45-60 minutes per interview
-- Record with permission
-- Prepare timeline visualization
-
-### Opening (5 min)
-
-"I'd love to understand how you came to use [product]. Not to sell you anything—just to learn about your experience."
-
-### First Thought (10 min)
-
-- "When did you first realize you might need something like this?"
-- "What was going on in your life at that time?"
-- "What triggered that thought?"
-
-### Passive Looking (10 min)
-
-- "What did you do after that first thought?"
-- "What alternatives did you consider?"
-- "Why didn't you act on it right away?"
-
-### Active Search (10 min)
-
-- "What made you start seriously looking?"
-- "What changed?"
-- "What were you comparing?"
-- "What criteria mattered most?"
-
-### Purchase Moment (10 min)
-
-- "Walk me through the moment you decided to buy."
-- "Where were you? Who were you with?"
-- "What finally convinced you?"
-- "What almost stopped you?"
-
-### Experience (10 min)
-
-- "Is it doing what you expected?"
-- "What surprised you?"
-- "What's still frustrating?"
-- "Would you hire it again?"
-
-### Closing
-
-- "If you could change one thing, what would it be?"
-- "What would make this perfect for your situation?"

package/skills/jobs-to-be-done/references/organizational-change.md

@@ -1,328 +0,0 @@
-# Organizational Change for JTBD
-
-Overcoming resistance, building jobs-oriented organizations, and avoiding the feature-factory trap.
-
-## Common Objections to JTBD
-
-### "We already know our customers"
-
-**The objection:** "We've been in this business for years. We know what customers want."
-
-**The reality:** You know what customers *say* they want and what they *do*. You may not know *why* they do it.
-
-**Counter:**
-- "Great—let's validate that knowledge. If we're right, research will confirm it quickly."
-- "When was the last time we talked to customers about their struggles, not our product?"
-- "Do we know why customers choose competitors, or why non-customers don't buy?"
-
-### "Jobs theory is too abstract"
-
-**The objection:** "This sounds like academic theory. We need practical action."
-
-**The reality:** JTBD is extremely practical—it tells you what to build and how to market.
-
-**Counter:**
-- "Let me show you a job statement for our product. Does this match how we talk about it?"
-- "Here's how [successful company] used JTBD to [specific outcome]."
-- "What if we ran one customer interview using this method and compared insights?"
-
-### "We don't have time for research"
-
-**The objection:** "We need to ship features, not conduct research."
-
-**The reality:** Shipping the wrong features wastes far more time than research.
-
-**Counter:**
-- "How much time did we spend building [feature that didn't work]?"
-- "Five customer interviews take ~10 hours. What's the cost of a failed launch?"
-- "We can learn the job from 10 interviews. We can't learn it from guessing."
-
-### "Our data tells us what to build"
-
-**The objection:** "We have analytics. We know what users do."
-
-**The reality:** Data shows *what* users do, not *why*. Jobs research explains the why.
-
-**Counter:**
-- "Data shows users drop off at step 3. Do we know why?"
-- "Our most-used feature might not be our most-valued feature. Data can't tell us."
-- "Correlation ≠ causation. We see patterns but don't understand motivations."
-
-### "Our roadmap is set"
-
-**The objection:** "Leadership has already decided what we're building."
-
-**The reality:** JTBD doesn't change what you build—it changes how you build and position it.
-
-**Counter:**
-- "Let's use jobs thinking to make sure we build [planned feature] the right way."
-- "Understanding the job might reveal quick wins within current plans."
-- "We can influence future roadmaps even if this quarter is set."
-
----
-
-## The Feature-Factory Trap
-
-### What It Looks Like
-
-A feature factory is an organization that:
-- Measures success by features shipped, not outcomes achieved
-- Builds what stakeholders request without validating need
-- Competes by feature matching competitors
-- Has roadmaps full of features without hypotheses
-- Celebrates launches, not impacts
-
-### Why It Happens
-
-| Cause | Dynamic |
-|-------|---------|
-| Easier to measure | "Did we ship it?" is binary; "Did it help?" is nuanced |
-| Stakeholder demands | "Important person X wants feature Y" |
-| Competitor pressure | "They have it, we need it" |
-| Customer requests | "Customer asked for X" (but didn't explain job) |
-| Short-term thinking | Features feel like progress |
-
-### The Costs
-
-- **Wasted development:** Features nobody uses
-- **Product bloat:** Complexity without value
-- **Technical debt:** Maintaining unused code
-- **Team demoralization:** Shipping without impact
-- **Customer confusion:** Product does everything, nothing well
-
-### Breaking Free
-
-**Step 1: Change the conversation**
-
-| Instead of | Ask |
-|------------|-----|
-| "What features should we build?" | "What jobs aren't being well-served?" |
-| "What did the customer request?" | "What job is the customer trying to do?" |
-| "What does the competitor have?" | "What job does that feature serve? Do our customers have that job?" |
-| "Did we ship it?" | "Did it help customers make progress?" |
-
-**Step 2: Change the metrics**
-
-| Feature-Factory Metrics | Jobs-Oriented Metrics |
-|------------------------|----------------------|
-| Features shipped | Customer outcomes improved |
-| Velocity | Value delivered |
-| Usage | Job completion rate |
-| NPS | Would you hire us again? |
-
-**Step 3: Change the process**
-
-Before greenlighting any feature:
-1. What job does this serve?
-2. Who has this job? How many?
-3. How well is the job being served today?
-4. How will we measure if this helps?
-
----
-
-## Getting Executive Buy-In
-
-### Speaking Their Language
-
-Executives care about:
-- Revenue growth
-- Market share
-- Competitive advantage
-- Customer acquisition/retention
-- Resource efficiency
-
-**Frame JTBD in these terms:**
-
-| JTBD Concept | Executive Translation |
-|--------------|----------------------|
-| Understanding the job | Reduce failed product launches |
-| Job-based segmentation | Find underserved market opportunities |
-| Competitive analysis | Identify sustainable differentiation |
-| Job-oriented metrics | Improve customer retention |
-
-### Making the Business Case
-
-**Case 1: Failed features**
-"Last year we shipped 12 major features. 3 moved metrics. JTBD research could have identified which 3 before we built all 12."
-
-**Case 2: Churn analysis**
-"Customers leave because we're not doing their job. Exit interviews reveal jobs we didn't know about. What if we knew before they left?"
-
-**Case 3: Competitive loss**
-"We lose deals to [competitor]. Is it features or job understanding? Interviews with lost customers could tell us."
-
-**Case 4: Market expansion**
-"Our market seems saturated. JTBD reveals non-consumers with the same jobs. That's greenfield opportunity."
-
-### The Pilot Proposal
-
-Start small to prove value:
-1. One focused research project (10 interviews, 2 weeks)
-2. One product decision influenced by findings
-3. Measure the outcome
-4. Report back with concrete results
-
----
-
-## Building a Jobs-Oriented Organization
-
-### Team Structure
-
-**Option 1: Embedded researchers**
-- Researchers on each product team
-- Continuous discovery, integrated with development
-- Best for: Large organizations, complex products
-
-**Option 2: Central research team**
-- Shared research capability serving all products
-- Standardized methodology, cross-product insights
-- Best for: Multiple products, resource constraints
-
-**Option 3: Everyone does research**
-- Product managers, designers, engineers all interview
-- Research is a skill, not a role
-- Best for: Small teams, startups
-
-### Cultural Practices
-
-**Regular customer exposure:**
-- Monthly customer interviews for every PM
-- Recordings shared team-wide
-- "Customer of the week" highlights
-
-**Decision-making rituals:**
-- "What job does this serve?" in every roadmap discussion
-- Job canvas for every major initiative
-- Retrospectives include job validation
-
-**Metrics and reviews:**
-- Quarterly job completion metrics
-- OKRs connected to customer progress
-- Celebrate outcomes, not outputs
-
-### Knowledge Management
-
-**Job documentation:**
-- Job atlas maintained and updated
-- Interview insights aggregated
-- Competitive job mapping shared
-
-**Searchable repository:**
-- All interview notes and recordings
-- Tagged by job, circumstance, dimension
-- Accessible to entire organization
-
----
-
-## Change Management Playbook
-
-### Phase 1: Awareness (Weeks 1-4)
-
-**Activities:**
-- Present JTBD concepts to leadership
-- Share case studies relevant to your business
-- Identify internal champions
-- Conduct one pilot research project
-
-**Milestone:** Leadership agrees to pilot, one team engaged
-
-### Phase 2: Pilot (Weeks 5-12)
-
-**Activities:**
-- Train pilot team on JTBD methodology
-- Conduct 10-15 customer interviews
-- Document job findings
-- Apply findings to one product decision
-- Measure results
-
-**Milestone:** Pilot produces actionable insights, one decision improved
-
-### Phase 3: Expansion (Months 4-6)
-
-**Activities:**
-- Share pilot results broadly
-- Train additional teams
-- Establish research operations
-- Build job documentation
-- Connect to roadmap process
-
-**Milestone:** Multiple teams practicing, methodology documented
-
-### Phase 4: Integration (Months 7-12)
-
-**Activities:**
-- Jobs language in all product discussions
-- Metrics shifted to job completion
-- Hiring includes research skills
-- Continuous discovery established
-
-**Milestone:** JTBD is "how we work," not "that initiative"
-
----
-
-## Handling Resistance
-
-### From Engineers
-
-**Concern:** "This is just going to change requirements mid-sprint."
-
-**Response:**
-- JTBD happens before sprint planning, not during
-- Better job understanding = fewer requirement changes later
-- You'll build things people actually use
-
-### From Sales
-
-**Concern:** "Customers tell me what they want. I don't need research."
-
-**Response:**
-- Customer requests are input, not output
-- Understanding why they want it helps you sell better
-- Competitor feature requests aren't always right
-
-### From Marketers
-
-**Concern:** "We already have personas and segments."
-
-**Response:**
-- Jobs complement personas with motivation
-- Circumstance-based targeting often outperforms demographic
-- Job statements make better copy than feature lists
-
-### From Product Managers
-
-**Concern:** "I don't have time for research—I need to ship."
-
-**Response:**
-- Five interviews take less time than one failed feature
-- Research prevents building the wrong thing
-- Good PMs always talk to customers; this just structures it
-
----
-
-## Measuring Adoption
-
-### Leading Indicators
-
-| Indicator | Sign of Progress |
-|-----------|------------------|
-| Customer interviews conducted | Research is happening |
-| Job statements documented | Learning is being captured |
-| Decisions citing job research | Research is influencing work |
-| Job questions in meetings | Language is changing |
-
-### Lagging Indicators
-
-| Indicator | Sign of Impact |
-|-----------|----------------|
-| Feature success rate | Building right things |
-| Customer satisfaction | Serving jobs better |
-| Retention/churn | Jobs being done |
-| Time to value | Onboarding aligned to jobs |
-
-### Anti-Patterns to Watch
-
-- "Job-washing": Using jobs language without doing research
-- "One and done": Research project that doesn't continue
-- "Cherry-picking": Only sharing findings that support existing plans
-- "Performative interviews": Going through motions without learning