Impact Mapping

Impact mapping is to help the team find the shortest path to the goal. 

4 components

• Outcome

Why are we doing this? This is the goal we are trying to achieve.

• Actor

The people's behavior we want to change, the WHO

Who can produce the desired effect? Who can obstruct it? Who are the consumers or users of our product? Who will be impacted by it? These are the actors who can influence the outcome.

• Impact

The Behavior Change

How should our actors’ behaviour change? How can they help us to achieve the goal? How can they obstruct or prevent us from succeeding?

• Deliverable

The WHAT, which is later turned into our user story maps

Defines the scope -- What can we do, as an organisation or a delivery team, to support the required impacts? 

Scope Based

Hard to understand which implementation made the impact, i.e. resonate with customer

• Focused on predefined list of features
• Success through implementation of all scope regardless of when goal is achieved
• Measurements after the fact and difficult to determine which feature had the most impact

Outcome Based

Do not do everything, do just enough to achieve the goal.

• Focused on desired outcome
• Success is delivery of minimum amount of functionality needed to achieve the outcome
• Incremental measurements to determine viability of solution

Mesuring Outcome

What to measure -- 

1. Metric
2. Benchmark
3. Milestone
4. Minimum Acceptable Value
5. Target Value

 

Metric: what data we need to measure

Benchmark: the value before apply strategy

Milestone: The deadline to examine the effectiveness of the strategy

Minimum Acceptable Value: the value we need to achieve at milestone to determine the effectiveness

Target Value: Keep applying the effective method, and that value is what we eventually will achieve to say we succeeded