foundations-problem-solution-fit

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
2. Functional Jobs: What tasks are customers trying to complete?
3. Emotional Jobs: How do customers want to feel? What anxieties to avoid?
4. Social Jobs: How do customers want to be perceived by others?
5. Map current workflow and identify friction points

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

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

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

1. Prioritize Problems
2. Severity Score: Frequency × Intensity
3. Solvability Assessment: Technical feasibility, cost to solve, time to market
4. Strategic Fit: Aligns with company vision, capabilities, market position
5. 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
2. Divergent Thinking: Generate 5-10 different solution concepts
3. Constraint Relaxation: What if budget/time/tech weren't constraints?
4. Analogy Mining: How do other industries solve similar problems?
5. User Co-Creation: Involve customers in solution ideation

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

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

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

1. Prototype and Test
2. Low-Fidelity Mockups: Sketches, wireframes, storyboards
3. Concept Testing: Present concepts to users, gather feedback
4. Wizard of Oz: Manual process behind automated facade
5. 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
2. Direct Competitors: Same problem, similar solution
3. Indirect Competitors: Same problem, different solution
4. Workarounds: Manual processes, hacks, duct-tape solutions
5. Non-Consumption: People who have problem but don't solve it

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

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

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

1. Determine Adoption Triggers
2. What event would make someone switch?: New role, company growth, regulation change
3. Migration Paths: How to move users from alternative to your solution
4. 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].