{
  "id": "page:library-impact-mapping",
  "_kind": "Page",
  "_file": "wiki/library/impact-mapping.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "title": "Impact Mapping Methodology (Library)",
    "displayName": "Impact Mapping Methodology (Library)",
    "slug": "library/impact-mapping",
    "articlePath": "wiki/library/impact-mapping.md",
    "article": "\n# Impact Mapping Methodology\n\n**Creator**: Gojko Adzic\n**Year**: Modern (2012)\n**Category**: Strategic Planning / Requirements / Product Strategy\n**Process ID**: `methodologies/impact-mapping`\n\n## Overview\n\nImpact Mapping is a strategic planning technique that helps organizations avoid getting lost in implementation details by creating a clear visual map connecting business goals to deliverable features. It ensures that every feature decision can be traced back to a business objective and the behavioral changes needed to achieve it.\n\nThis methodology prevents scope creep, enables better prioritization, and helps teams focus on outcomes rather than outputs.\n\n## The Impact Mapping Hierarchy\n\nImpact Mapping uses a four-level hierarchy to connect strategy to execution:\n\n```\n🎯 GOAL (Why?)\n    └─ 👤 ACTOR (Who?)\n        └─ 💫 IMPACT (How?)\n            └─ 📦 DELIVERABLE (What?)\n```\n\n### 1. 🎯 Goal - WHY are we doing this?\n\nThe business objective we want to achieve. Must be:\n- **Specific**: Clear and well-defined\n- **Measurable**: Quantifiable success metrics\n- **Achievable**: Realistic given constraints\n- **Relevant**: Aligned with business strategy\n- **Time-bound**: Has a deadline or timeframe\n\n**Examples**:\n- \"Increase monthly recurring revenue by 30% in Q2 2026\"\n- \"Reduce customer churn from 8% to 4% within 6 months\"\n- \"Achieve 100,000 active users by end of year\"\n\n### 2. 👤 Actor - WHO can create impact?\n\nThe people, systems, or organizations who can help achieve (or hinder) the goal.\n\n**Actor Types**:\n- **Primary Actors**: Direct users who will use the product\n  - End users, customers, key personas\n- **Secondary Actors**: Indirect beneficiaries or influencers\n  - Decision makers, stakeholders, partners, internal teams\n- **Negative Actors**: Opposition or competition\n  - Competitors, detractors, obstacles, systems to replace\n\n**Examples**:\n- \"Existing premium customers\"\n- \"Free trial users\"\n- \"Customer success team\"\n- \"Competitors (negative actor)\"\n\n### 3. 💫 Impact - HOW should their behavior change?\n\nThe desired change in actor behavior that contributes to the goal.\n\n**Impact Types**:\n- **Adoption**: Start using something new\n- **Engagement**: Increase interaction frequency\n- **Efficiency**: Do things faster or better\n- **Advocacy**: Promote to others\n- **Retention**: Continue using, reduce churn\n- **Conversion**: Upgrade or purchase\n- **Reduction**: Stop unwanted behavior\n- **Prevention**: Block negative impacts\n\n**Examples**:\n- \"Free users upgrade to premium tier\"\n- \"Customers renew subscriptions earlier\"\n- \"Support team resolves tickets 50% faster\"\n- \"Competitors lose market share to us\"\n\n### 4. 📦 Deliverable - WHAT can we build?\n\nFeatures, stories, or capabilities that create the desired impact.\n\n**Deliverable Types**:\n- **Feature**: New capability\n- **Enhancement**: Improvement to existing feature\n- **Content**: Documentation, training, marketing\n- **Integration**: Connection to other systems\n- **Automation**: Remove manual work\n- **UI/UX**: Interface improvement\n- **Infrastructure**: Technical enabler\n\n**Examples**:\n- \"Advanced analytics dashboard\"\n- \"Automated onboarding workflow\"\n- \"API integration with Salesforce\"\n- \"Premium support tier\"\n\n## Key Principles\n\n### 1. Outside-In Thinking\nStart with the goal and work outward. Don't start with features.\n\n### 2. Multiple Paths to Goal\nThere are always multiple actors, impacts, and deliverables that could achieve the goal. Map them all, then prioritize.\n\n### 3. Assumption Tracking\nFlag assumptions at every level. These are hypotheses that need validation through experimentation or user research.\n\n### 4. Visual Communication\nThe map is a visual tool for stakeholder alignment. Everyone should be able to understand the strategic connection between features and goals.\n\n### 5. Living Document\nUpdate the map as you learn. When assumptions are validated or invalidated, adjust the map.\n\n## Process Flow\n\n### Phase 1: Goal Definition\n- Define clear, measurable business objective\n- Establish success metrics (KPIs)\n- Document timeline and constraints\n- Identify initial assumptions and risks\n- Ensure goal is SMART\n\n**Output**: Well-defined goal with metrics and constraints\n\n### Phase 2: Actor Identification\n- Brainstorm all actors who can impact the goal\n- Categorize as primary, secondary, or negative\n- Assess each actor's influence and reach\n- Document current vs. desired behaviors\n- Prioritize high-influence actors\n\n**Output**: Comprehensive list of actors with influence assessment\n\n### Phase 3: Impact Analysis\n- For each actor, define desired behavioral changes\n- Connect each impact to goal achievement\n- Define how to measure each impact\n- Identify assumptions for each impact\n- Consider obstacles to creating impact\n\n**Output**: Behavioral impacts for all actors with measurements\n\n### Phase 4: Deliverable Generation\n- Brainstorm deliverables that could create each impact\n- Consider multiple solution options\n- Assess impact potential vs. effort\n- Document dependencies and risks\n- Flag high-assumption deliverables\n\n**Output**: Deliverable options for all impacts\n\n### Phase 5: Prioritization and Roadmap\n- Score deliverables by impact potential, effort, and risk\n- Prioritize into must/should/could/won't have\n- Sequence into implementation milestones\n- Plan assumption validation experiments\n- Balance quick wins with strategic investments\n\n**Output**: Prioritized roadmap with validation plan\n\n### Phase 6: Map Visualization\n- Create visual tree diagram\n- Mark assumptions with flags\n- Highlight prioritized deliverables\n- Use color coding for clarity\n- Share with stakeholders for alignment\n\n**Output**: Visual impact map for communication\n\n## Usage\n\n### Basic Example\n\n```javascript\nimport { process } from './impact-mapping.js';\n\nconst result = await process({\n  goal: \"Increase monthly recurring revenue by 30% in Q2 2026\",\n  timeframe: \"Q2 2026\",\n  successMetrics: [\n    {\n      metric: \"Monthly Recurring Revenue (MRR)\",\n      currentValue: \"$100,000\",\n      targetValue: \"$130,000\",\n      measurement: \"Billing system reports\"\n    }\n  ]\n}, ctx);\n\nconsole.log(`Actors identified: ${result.actorCount}`);\nconsole.log(`Impacts defined: ${result.impactCount}`);\nconsole.log(`Deliverables generated: ${result.deliverableCount}`);\nconsole.log(`Critical assumptions: ${result.criticalAssumptions}`);\nconsole.log(`Roadmap phases: ${result.milestoneCount}`);\n```\n\n### With Constraints and Context\n\n```javascript\nconst result = await process({\n  goal: \"Reduce customer support ticket volume by 40% within 6 months\",\n  timeframe: \"6 months\",\n  successMetrics: [\n    {\n      metric: \"Support tickets per month\",\n      currentValue: \"5000\",\n      targetValue: \"3000\",\n      measurement: \"Zendesk analytics\"\n    },\n    {\n      metric: \"Customer satisfaction (CSAT)\",\n      currentValue: \"75%\",\n      targetValue: \"85%\",\n      measurement: \"Post-interaction surveys\"\n    }\n  ],\n  constraints: {\n    budget: \"$200,000\",\n    team: \"2 engineers, 1 designer\",\n    technical: [\"Must integrate with existing Zendesk\"],\n    regulatory: [\"Must maintain GDPR compliance\"]\n  },\n  context: {\n    existingFeatures: [\"Basic knowledge base\", \"Email support\"],\n    painPoints: [\"Repetitive questions\", \"Slow response times\"],\n    teamCapabilities: [\"React, Node.js, PostgreSQL\"]\n  },\n  knownActors: [\"Customers\", \"Support agents\", \"Product managers\"]\n}, ctx);\n```\n\n### Inputs\n\n| Field | Type | Required | Default | Description |\n|-------|------|----------|---------|-------------|\n| `goal` | string | ✅ Yes | - | Business goal or objective |\n| `timeframe` | string | No | \"6 months\" | Timeline for achieving goal |\n| `successMetrics` | array | No | [] | KPIs to measure goal success |\n| `constraints` | object | No | {} | Budget, team, technical, regulatory |\n| `context` | object | No | null | Existing product/system context |\n| `knownActors` | array | No | [] | Pre-identified actors |\n\n### Outputs\n\n```javascript\n{\n  success: true,\n  sessionDurationMinutes: 45,\n  goal: {\n    goal: \"Increase MRR by 30%\",\n    why: \"Drive business growth and profitability\",\n    successMetrics: [...],\n    timeline: {...},\n    smartScore: { specific: true, measurable: true, ... }\n  },\n  actors: [\n    {\n      id: \"actor-1\",\n      name: \"Free tier users\",\n      type: \"primary\",\n      influence: \"high\",\n      reach: \"10,000 users\",\n      ...\n    }\n  ],\n  actorCount: 6,\n  actorBreakdown: {\n    primary: 3,\n    secondary: 2,\n    negative: 1\n  },\n  impacts: [\n    {\n      id: \"impact-1\",\n      actorId: \"actor-1\",\n      description: \"Upgrade to premium tier\",\n      type: \"conversion\",\n      behavioralChange: \"Users convert from free to paid\",\n      effect: \"Directly increases MRR\",\n      measurement: {...},\n      assumptions: [...]\n    }\n  ],\n  impactCount: 12,\n  deliverables: [\n    {\n      id: \"del-1\",\n      impactId: \"impact-1\",\n      title: \"Advanced analytics dashboard\",\n      type: \"feature\",\n      impactPotential: \"high\",\n      effort: \"medium\",\n      priorityTier: \"must-have\",\n      priorityScore: 87,\n      ...\n    }\n  ],\n  deliverableCount: 24,\n  assumptions: [\n    {\n      assumption: \"Users value analytics enough to pay\",\n      priority: \"critical\",\n      validationMethod: \"User interviews and surveys\",\n      ...\n    }\n  ],\n  assumptionCount: 15,\n  criticalAssumptions: 5,\n  roadmap: {\n    milestones: [\n      {\n        phase: 1,\n        name: \"MVP - Core Value Proposition\",\n        duration: \"6 weeks\",\n        deliverableIds: [\"del-1\", \"del-3\"],\n        validationExperiments: [...]\n      }\n    ],\n    strategy: \"Focus on must-have features first...\",\n    riskMitigation: [...]\n  },\n  milestoneCount: 3,\n  map: {\n    goal: {...},\n    tree: [...]\n  },\n  visualization: {\n    mermaid: \"graph TB\\n...\",\n    format: \"mermaid\"\n  },\n  artifacts: {\n    goal: 'artifacts/impact-mapping/goal.json',\n    actors: 'artifacts/impact-mapping/actors.md',\n    impacts: 'artifacts/impact-mapping/impacts.md',\n    deliverables: 'artifacts/impact-mapping/deliverables.md',\n    assumptions: 'artifacts/impact-mapping/assumptions.json',\n    prioritization: 'artifacts/impact-mapping/prioritization.md',\n    roadmap: 'artifacts/impact-mapping/roadmap.json',\n    visualization: 'artifacts/impact-mapping/impact-map.mmd',\n    completeMap: 'artifacts/impact-mapping/complete-map.json',\n    summary: 'artifacts/impact-mapping/summary.md'\n  }\n}\n```\n\n## Integration Points\n\n### Perfect Input for Other Methodologies\n\n1. **Spec-Driven Development**\n   - Impact Map defines what to build and why\n   - Deliverables become specifications\n   - Assumptions guide specification validation\n   - Goal metrics become acceptance criteria\n\n2. **Example Mapping**\n   - Each deliverable can be mapped with examples\n   - Impacts help define business rules\n   - Actors inform user story personas\n   - Goal provides context for mapping sessions\n\n3. **BDD/Specification by Example**\n   - Impacts define behavioral scenarios\n   - Deliverables become features in Gherkin\n   - Metrics guide scenario design\n   - Actors become personas in scenarios\n\n4. **Domain-Driven Design (DDD)**\n   - Actors map to domain entities and aggregates\n   - Impacts identify domain events\n   - Deliverables suggest bounded contexts\n   - Goal defines core domain\n\n5. **Hypothesis-Driven Development**\n   - Assumptions become hypotheses to test\n   - Impacts are predicted outcomes\n   - Deliverables are experiments\n   - Metrics measure hypothesis validation\n\n6. **Feature-Driven Development (FDD)**\n   - Deliverables become features\n   - Actors drive feature ownership\n   - Impacts guide feature prioritization\n   - Goal aligns with business value\n\n7. **GSD (Getting Stuff Done)**\n   - Roadmap defines phases\n   - Milestones structure execution\n   - Prioritization guides sprint planning\n   - Goal tracks toward business outcome\n\n### Workflow Integration\n\n```\nImpact Mapping (Strategic)\n    ↓\nHypothesis-Driven Development (Assumption Validation)\n    ↓\nSpec-Driven Development (Define Implementation)\n    ↓\nExample Mapping (Elaborate Stories)\n    ↓\nBDD/TDD (Build and Test)\n    ↓\nGSD Execution (Deliver)\n```\n\n## Success Criteria\n\nA successful Impact Mapping session produces:\n\n- ✅ Clear, measurable SMART goal with 3-5 KPIs\n- ✅ Diverse actor types identified (primary, secondary, negative)\n- ✅ Specific, measurable behavioral impacts per actor\n- ✅ Multiple deliverable options per impact\n- ✅ Prioritized roadmap with 2-4 milestones\n- ✅ Critical assumptions flagged for validation\n- ✅ Visual map for stakeholder communication\n- ✅ Team alignment on strategy and priorities\n\n## Warning Signs\n\nIf Impact Mapping reveals these issues, consider refinement:\n\n- ❌ Goal is vague or not measurable\n- ❌ Only 1-2 actors identified (too narrow)\n- ❌ Impacts are features, not behaviors\n- ❌ All deliverables are \"must-have\" (no prioritization)\n- ❌ Dozens of assumptions with no validation plan\n- ❌ Map is too complex (more than 50 deliverables)\n- ❌ Stakeholders can't explain the strategy from the map\n\n→ **Refine the goal**, simplify the scope, or break into multiple maps\n\n## Best Practices\n\n### Do's\n- ✅ Start with a single, clear goal per map\n- ✅ Think broadly about actors (don't forget negative actors)\n- ✅ Focus impacts on behavior, not features\n- ✅ Generate multiple deliverable options (divergent thinking)\n- ✅ Flag assumptions early and often\n- ✅ Validate critical assumptions before building\n- ✅ Update the map as you learn\n- ✅ Use the map for stakeholder communication\n\n### Don'ts\n- ❌ Don't try to map multiple goals at once\n- ❌ Don't skip actors and jump to features\n- ❌ Don't assume one solution per impact\n- ❌ Don't build everything - prioritize ruthlessly\n- ❌ Don't ignore negative actors\n- ❌ Don't create the map alone - collaborate\n- ❌ Don't let the map become stale - keep it updated\n\n## Example: SaaS Revenue Growth\n\n### Goal\n> 🎯 **Increase monthly recurring revenue (MRR) from $100K to $150K by Q3 2026**\n\n**Success Metrics**:\n- MRR: $100K → $150K (50% increase)\n- Customer count: 500 → 700 customers\n- Average revenue per customer: $200 → $214\n- Churn rate: 8% → 5%\n\n### Actors and Impacts\n\n**👤 Actor: Free Tier Users** (Primary)\n- 💫 Impact: Convert to paid plans\n  - 📦 Advanced analytics dashboard (must-have) ⚡\n  - 📦 Customizable reports (should-have)\n  - 📦 Data export API (could-have)\n\n- 💫 Impact: Increase engagement before conversion\n  - 📦 Interactive product tour (must-have)\n  - 📦 Onboarding email sequence (must-have)\n  - 📦 Usage milestone notifications (should-have)\n\n**👥 Actor: Existing Paid Customers** (Primary)\n- 💫 Impact: Upgrade to higher tiers\n  - 📦 Team collaboration features (must-have) ⚡\n  - 📦 Advanced permissions system (should-have)\n  - 📦 Priority support tier (should-have)\n\n- 💫 Impact: Reduce churn by increasing value\n  - 📦 Customer success program (must-have)\n  - 📦 Regular feature adoption webinars (should-have)\n  - 📦 In-app usage recommendations (could-have)\n\n**👥 Actor: Customer Success Team** (Secondary)\n- 💫 Impact: Proactively prevent churn\n  - 📦 Churn risk dashboard (must-have)\n  - 📦 Automated health score alerts (must-have)\n  - 📦 Customer journey playbooks (should-have)\n\n**⚠️ Actor: Competitors** (Negative)\n- 💫 Impact: Prevent customer loss to competitors\n  - 📦 Competitive feature parity analysis (must-have)\n  - 📦 Unique differentiating feature (must-have) ⚡\n  - 📦 Price comparison tool for prospects (could-have)\n\n### Assumptions (⚡ = Critical)\n1. ⚡ Free users will pay for advanced analytics (Validation: User interviews + pricing survey)\n2. ⚡ Team features justify higher price tiers (Validation: Beta testing with 10 customers)\n3. Customer success can reduce churn by 3% (Validation: 3-month pilot program)\n4. Competitors are not planning major feature releases (Validation: Market monitoring)\n\n### Roadmap\n\n**Milestone 1: MVP (Weeks 1-8)**\n- Goal: Validate core upgrade value proposition\n- Deliverables: Advanced analytics, interactive tour, churn dashboard\n- Experiments: Test pricing tiers, measure conversion rate\n- Target: $10K MRR increase from conversions\n\n**Milestone 2: Retention (Weeks 9-16)**\n- Goal: Reduce churn and increase customer lifetime value\n- Deliverables: Customer success program, team features, onboarding sequence\n- Experiments: A/B test onboarding flows, measure retention impact\n- Target: Churn from 8% → 6%\n\n**Milestone 3: Expansion (Weeks 17-24)**\n- Goal: Drive upgrades and market differentiation\n- Deliverables: Advanced permissions, priority support, unique feature\n- Experiments: Test upgrade paths, measure competitive win rates\n- Target: Reach $150K MRR\n\n## References\n\n### Original Sources\n- [Impact Mapping Official Website](https://www.impactmapping.org/) - Free online book by Gojko Adzic\n- [Impact Mapping: Making a Big Impact with Software Products](https://www.impactmapping.org/book.html) - Complete book\n- [Drawing Impact Maps](https://www.impactmapping.org/drawing.html) - Workshop guide\n- [Example Impact Maps](https://www.impactmapping.org/example.html) - Real-world examples\n\n### Related Reading\n- [Specification by Example](https://gojko.net/books/specification-by-example/) - Gojko Adzic\n- [Fifty Quick Ideas to Improve Your User Stories](https://fiftyquickideas.com/fifty-quick-ideas-to-improve-your-user-stories/) - Gojko Adzic & David Evans\n- [User Story Mapping](https://www.jpattonassociates.com/user-story-mapping/) - Jeff Patton\n\n### Video Tutorials\n- [Gojko Adzic: Impact Mapping](https://www.youtube.com/watch?v=y4Rj05YVg_E) - Overview presentation\n- [Impact Mapping Workshop](https://www.youtube.com/results?search_query=impact+mapping+workshop) - Various workshop recordings\n\n### Community Resources\n- [Impact Mapping Templates](https://miro.com/templates/impact-mapping/) - Miro templates\n- [Impact Mapping Guide](https://www.thoughtworks.com/insights/blog/impact-mapping-scaling-agile-practices-impact) - ThoughtWorks\n- [Product Management Resources](https://www.productplan.com/glossary/impact-mapping/) - Product planning context\n\n## License\n\nThis methodology implementation is part of the Babysitter SDK orchestration framework.\n\nCreator credit: Gojko Adzic for the Impact Mapping technique.\n",
    "documents": [
      "specialization:impact-mapping"
    ]
  },
  "outgoingEdges": [
    {
      "from": "page:library-impact-mapping",
      "to": "specialization:impact-mapping",
      "kind": "documents"
    }
  ],
  "incomingEdges": [
    {
      "from": "page:index",
      "to": "page:library-impact-mapping",
      "kind": "contains_page"
    }
  ]
}