Impact Map

Impact Mapping connects a goal → actors → impacts (behaviour changes) → deliverables. It keeps backlog tied to outcomes instead of feature requests.

Teams ship deliverables that do not move the goal. Impact maps make assumptions explicit and testable.

Quarterly planning, OKR kickoff, major initiative scoping. After OKRs or north star defined.

1. State measurable goal.
2. List actors who can help or block.
3. Define impacts — how actors should behave differently.
4. Brainstorm deliverables that might cause impacts.
5. Prioritise deliverables; mark assumptions.
6. Link to experiments or OKRs.

• Goal is measurable.
• Impacts are behaviours, not features.
• Deliverables trace upward cleanly.
• Assumptions flagged.

• Skipping actors — jump to features.
• Impacts unmeasurable.
• Map never revisited after shipping.

Northvale Systems goal: cut audit prep time. Actor: supplier admin. Impact: upload complete dossier first time. Deliverable: guided upload wizard — prioritised over new analytics tiles.

PulseWell goal: raise pilot conversion. Actor: site managers. Impact: log weekly team check-ins. Deliverables: manager mobile nudges, ROI email — prioritised nudges first.

Harbor Consulting goal: more diagnostic bookings. Actor: plant owners. Impact: register for webinar. Deliverables: case-study landing page, partner co-host — tested landing page first.

Clearwater Initiative goal: fewer sick days from waterborne illness. Actor: committee chair. Impact: run weekly test without NGO visit. Deliverable: SMS + pictorial SOP card.

/strategy canvas impact-map, IDs IMP-G-01, IMP-A-01, IMP-I-01, IMP-D-01. Feeds backlog and OKRs.