Impact mapping is a planning process that gives you a framework to generate and visualise the connections between goals and deliverables and the impact you expect to make by putting those deliverables in place.
Problem to solution impact mapping is just a particular version we use at duckworth.design. It uses specific groups and process to connect together a problem statement with the outcomes you want to influence and the things you can do about it.
We typically use this technique when we’re trying to plot out how to get from insights and research to a strategy or a backlog of improvements we want to make.
This can be from looking at a full service, or a small feature.
We use it in projects where we’re:
The tool is also useful when you need to align different perspectives and make sure that everyone is on the same page about the goals, outcomes, and initiatives of a project or product.
You can use this technique at the start of a project to align the team, or at any point during the project when the team needs to refocus or realign.
However, you may find there are simpler approaches to small problems. Or where the solution space is obvious and simple. But if you have multiple insights, users or things you can do. This is a great technique to visualise and structure your thinking.
The process to create the problem to solution map can be collaboratively or individually. If you’re doing it in a workshop, you may want to consider collaborate structures like a 1-group-room loop. This way, you’ve asking people to individually respond before sharing with a wider group or room.
The process you should follow to create the map is:
Once you’ve gone through those steps you should have the beginnings of your map. Keep working through the users and their issues.
Once you’ve done that your next phase is to:
If any of these phases feel difficult to complete it might mean you need more information. When we first started using impact mapping we found it difficult for projects where our insights weren’t as deep as others. The answer was to gather more insights. From users and stakeholders.