foundations-problem-solution-fit

What this skill does

# Problem-Solution Fit Agent

## Overview

The Problem-Solution Fit Agent validates that you're solving a real, valuable problem with the right solution approach. This agent merges Problem Framing, Alternative Analysis, Solution Building, and Innovation Strategy to ensure strong problem-solution alignment before significant investment.

**Primary Use Cases**: Problem discovery, solution validation, MVP definition, innovation strategy, pivot assessment.

**Lifecycle Phases**: Discovery (primary), Definition, major pivots, product expansion.

## Core Functions

### 1. Problem Discovery

Identify, validate, and prioritize customer problems to ensure solving high-value pain points.

**Workflow**:

1. **Identify Problems Using Jobs-to-be-Done Framework**
   - **Functional Jobs**: What tasks are customers trying to complete?
   - **Emotional Jobs**: How do customers want to feel? What anxieties to avoid?
   - **Social Jobs**: How do customers want to be perceived by others?
   - Map current workflow and identify friction points

2. **Measure Pain Frequency**
   - **Daily**: Problem occurs every day
   - **Weekly**: Problem occurs 1-4 times per week
   - **Monthly**: Problem occurs 1-4 times per month
   - **Quarterly**: Problem occurs occasionally
   - Higher frequency = higher awareness and urgency

3. **Assess Pain Intensity**
   - **1 - Minor annoyance**: Tolerable, low willingness to pay
   - **2 - Noticeable frustration**: Aware but not urgent
   - **3 - Significant problem**: Actively seeking solutions
   - **4 - Major pain point**: High urgency, budget allocated
   - **5 - Critical/existential**: Business-critical, will pay premium

4. **Validate Through Research**
   - **User Interviews**: Minimum 10-15 interviews in target segment
     - Ask: "Tell me about the last time you experienced [problem]"
     - Probe: "How did you handle it? What did it cost you?"
     - Avoid: "Would you use a solution that does X?" (leading question)
   - **Observational Studies**: Shadow users in their natural environment
   - **Data Analysis**: Support tickets, review mining, search query data

5. **Prioritize Problems**
   - **Severity Score**: Frequency × Intensity
   - **Solvability Assessment**: Technical feasibility, cost to solve, time to market
   - **Strategic Fit**: Aligns with company vision, capabilities, market position
   - **Problem Stack Rank**: Top 3-5 problems to pursue

**Output Template**:
```
Validated Problem Stack Rank

1. [Problem Statement]
   ├── Job-to-be-Done: [functional/emotional/social job]
   ├── Frequency: [daily/weekly/monthly/quarterly]
   ├── Intensity: X/5
   ├── Severity Score: XX (frequency × intensity)
   ├── Current Cost: $X per [time period] or X hours per [time period]
   ├── Evidence: [interview quotes, data points, observations]
   ├── Solvability: [high/medium/low] (rationale)
   └── Priority: 1 (recommended focus)

2. [Problem Statement]...
3. [Problem Statement]...

Problem Selection Rationale:
[1-2 sentences explaining why problem #1 is the right focus]

Red Flags Identified:
- [Any problems that seem low-value or unsolvable]
- [Customer segments where problem doesn't exist]
```

### 2. Solution Hypothesis

Generate and evaluate multiple solution approaches to find optimal problem-solution fit.

**Workflow**:

1. **Generate Multiple Solution Approaches**
   - **Divergent Thinking**: Generate 5-10 different solution concepts
   - **Constraint Relaxation**: What if budget/time/tech weren't constraints?
   - **Analogy Mining**: How do other industries solve similar problems?
   - **User Co-Creation**: Involve customers in solution ideation

2. **Evaluate Technical Feasibility**
   - **Existing Technology**: Can be built with current tech stack
   - **Emerging Technology**: Requires new but available technology
   - **Research Required**: Needs R&D or breakthroughs
   - **Impossible Today**: Not feasible with current technology

3. **Assess Effort vs Impact**
   - **Effort**: S (small - days), M (medium - weeks), L (large - months)
   - **Impact**: Low (nice-to-have), Medium (meaningful improvement), High (10x better)
   - **Prioritization Matrix**: High impact + Low effort = Quick wins

4. **Evaluate Build vs Buy vs Partner**
   - **Build**: Core differentiation, IP ownership, full control
   - **Buy**: Commodity feature, faster time-to-market, proven solution
   - **Partner**: Complementary capabilities, shared risk, ecosystem play

5. **Prototype and Test**
   - **Low-Fidelity Mockups**: Sketches, wireframes, storyboards
   - **Concept Testing**: Present concepts to users, gather feedback
   - **Wizard of Oz**: Manual process behind automated facade
   - **Concierge MVP**: High-touch service to validate value before automation

**Output Template**:
```
Solution Hypothesis Evaluation

Problem Being Solved: [Problem #1 from stack rank]

Solution Concepts (Top 3):

Concept A: [Solution Name]
├── Description: [1-2 sentences]
├── Technical Feasibility: [existing/emerging/research/impossible]
├── Effort: [S/M/L] - [X weeks/months]
├── Impact: [Low/Medium/High] - [expected improvement]
├── Build/Buy/Partner: [decision + rationale]
├── Differentiation Potential: [low/medium/high]
├── Prototype Approach: [mockup/concept test/wizard of oz/concierge]
└── Validation Criteria: [What must be true for this to work?]

Concept B: [Solution Name]...
Concept C: [Solution Name]...

Recommended Solution: Concept [A/B/C]
Rationale: [Why this concept beats alternatives]

Next Steps:
1. [First validation experiment]
2. [Second validation experiment]
3. [MVP scoping if validation succeeds]
```

### 3. Alternative Analysis

Catalog and analyze existing solutions to identify competitive advantage opportunities.

**Workflow**:

1. **Catalog Current Solutions**
   - **Direct Competitors**: Same problem, similar solution
   - **Indirect Competitors**: Same problem, different solution
   - **Workarounds**: Manual processes, hacks, duct-tape solutions
   - **Non-Consumption**: People who have problem but don't solve it

2. **Assess Customer Satisfaction**
   - **Satisfaction Score**: 1 (very dissatisfied) to 5 (very satisfied)
   - **Net Promoter Score**: Likelihood to recommend current solution
   - **Review Mining**: Extract common complaints and praises
   - **Churn/Retention Data**: Why do users leave or stay?

3. **Identify Switching Barriers**
   - **Financial**: Sunk costs, contracts, switching fees
   - **Technical**: Data migration, integration complexity, learning curve
   - **Organizational**: Process changes, stakeholder buy-in, training
   - **Psychological**: Loss aversion, status quo bias, risk perception

4. **Map Unmet Needs**
   - **Feature Gaps**: What do users wish existed?
   - **Performance Gaps**: What's too slow, expensive, or complex?
   - **Experience Gaps**: Where is UX frustrating or confusing?
   - **Integration Gaps**: What doesn't connect that should?

5. **Determine Adoption Triggers**
   - **What event would make someone switch?**: New role, company growth, regulation change
   - **Migration Paths**: How to move users from alternative to your solution
   - **Value Gaps**: How much better must you be to justify switching? (10x rule)

**Output Template**:
```
Alternative Analysis

Existing Alternatives (Top 5):

1. [Alternative Name/Category]
   ├── Type: [direct competitor/indirect/workaround/non-consumption]
   ├── Satisfaction: X/5 (evidence: [reviews/NPS/churn])
   ├── Strengths: [What they do well]
   ├── Weaknesses: [Where they fall short]
   ├── Switching Barriers: [financial/technical/organizational/psychological]
   ├── Market Share: X% or [dominant/emerging/niche]
   └── Unmet Needs: [What users still complain about]

2. [Alternative Name/Category]...

Competitive Advantage Opportunities:

1. [Opportunity]: [Description]
   - Why Alternative Fails Here: [reason]
   - Our Advantage: [capability/insight/approach]
   - Barrier to Replicate: [why hard for competitors to copy]

2. [Opportunity]...
3. [Opportunity]