{"id":15177,"date":"2022-10-26T16:48:44","date_gmt":"2022-10-26T16:48:44","guid":{"rendered":"https:\/\/userpilot.com\/blog\/impact-mapping\/"},"modified":"2025-05-22T16:06:18","modified_gmt":"2025-05-22T16:06:18","slug":"impact-mapping","status":"publish","type":"post","link":"https:\/\/userpilot.com\/blog\/impact-mapping\/","title":{"rendered":"Impact Mapping: Does it Make a Difference in Building Better Products?"},"content":{"rendered":"

What’s impact mapping? When do you need it and how does it help product managers<\/a> build better products?<\/p>\n

If you’re after the answers to these questions, we’ve got you covered!<\/p>\n

Ready to dive in? Let’s get to it!<\/p>\n

What is impact mapping?<\/h2>\n

Impact mapping is a technique for collaborative strategy planning<\/a> and product management.<\/p>\n

The tool was initially used in Agile software delivery to set key business objectives and plan how to achieve them.<\/p>\n

It became popular thanks to the 2012 Gojko Adzic book<\/a>.<\/p>\n

\"Impact<\/picture>
Impact Mapping by Gojko Adzic.<\/figcaption><\/figure>\n

Software delivery teams liked the technique because it enabled them to assess the impact of features once they released them. Like other lean software methods, it allowed them to save time and money that otherwise would’ve been wasted on developing random functionality.<\/p>\n

These days, it is a widely-recognized technique used not only in software product management.<\/p>\n

What is impact mapping in agile?<\/h2>\n

Impact mapping is a technique that allows Agile teams to visualize the connections between business goals, their users, and the functionality they develop.<\/p>\n

Consequently, it makes it easier for them to see how their backlogs <\/a>are aligned with business objectives and stay focused on the key priorities.<\/p>\n

What is an impact map?<\/h2>\n

Simply speaking, an impact map is a tree diagram presenting the hierarchy of goals and features.<\/p>\n

What are the different levels? Bear with us! We\u2019re dealing with it in one of the sections below<\/a>!<\/p>\n

Impact mapping vs customer journey maps<\/h2>\n

Impact maps and customer journey maps<\/a> are two very different tools.<\/p>\n

As mentioned, the purpose of the impact maps is to highlight the dependencies between the business goals, the users, and the functionality you’re developing.<\/p>\n

A customer journey map<\/a>, on the other hand, is a visual representation of the stages and tasks that your customer needs to complete to achieve their goals and experience product value<\/a>.<\/p>\n

\"User<\/picture>
User Journey Map<\/a> Template.<\/figcaption><\/figure>\n

The purpose of an impact mapping process in software development<\/h2>\n

Impact mapping enhances strategic planning, helps define quality improvements<\/a> that will have the best impact on the overall goal, and manage roadmaps<\/a>.<\/p>\n

Strategic planning<\/h3>\n

Impact mapping helps organizations develop product strategy<\/a> and ensure its alignment with the business goals<\/a>.<\/p>\n

The senior leadership is mainly interested in long-term plans to deliver on the business objectives. However, such plans don’t allow for changes in market trends or customer needs.<\/p>\n

Impact mapping allows more flexibility. It focuses on the general scope of the product which is enough to show the direction without restricting the options of the development team.<\/p>\n

Defining quality improvements<\/h3>\n

Impact mapping also illustrates the impact each of the technical deliverables should have on different user personas<\/a>.<\/p>\n

It also illustrates how individual deliverable contributes to the overall objective and enables teams to measure progress.<\/p>\n

Roadmap management<\/h3>\n

Finally, impact mapping improves roadmap management<\/a> and helps teams avoid scope creep.<\/p>\n

By clearly communicating the goals, it helps teams prioritize <\/a>deliverables that have the biggest impact. More importantly, it allows them to weed out those initiatives that will have no impact.<\/p>\n

This makes sprint planning easier and quicker and enhances the team’s ability to realize product goals.<\/a><\/p>\n

Why are impact maps important for product managers?<\/h2>\n

Product managers can use impact mapping at all stages of the product management process<\/a>.<\/p>\n

To start with, impact mapping is a solid product discovery<\/a> technique. It gives the team a structure to explore which user persona may have the biggest impact on the business goals and what their needs are and how to best satisfy them.<\/p>\n

Once they start working on the product, impact maps help teams keep their eyes on the goals and avoid falling into the build trap<\/a>. As new feature ideas come up, it’s super important to stay true to the overall product vision <\/a>and choose only those that will help you realize it.<\/p>\n

Finally, as mentioned above, impact mapping helps senior stakeholders, product, and development teams stay on the same page.<\/p>\n

As a result, the developers, marketers, and salespeople understand where the product is heading, while the senior stakeholders understand why you prioritize certain features over others.<\/p>\n

When do you need an impact map?<\/h2>\n

Impact mapping comes particularly handy when you\u2019re dealing with highly complex problems and with very uncertain outcomes.<\/p>\n

In what situations should you use impact mapping?<\/p>\n

To start with, you should create an impact map when you have a number of different projects in place but no clear overarching goal. The map will help you set the high-level vision.<\/p>\n

Very often, your organization may have goals but they are not clear, and the stakeholders may understand them differently. Even worse, they may have different goals. Impact mapping can help you redefine the problem and ensure high-level alignment.<\/p>\n

Finally, use impact mapping when you have problems prioritizing <\/a>different initiatives, especially when you\u2019re building a complex product. Impact maps can help you identify the ones that have the biggest impact and help you achieve the product goals<\/a>.<\/p>\n

How to structure an impact map<\/h2>\n

By now, you already know about the tree structure of the impact map. But what exactly goes into the product map and how to structure it?<\/p>\n

Goal: WHY?<\/h3>\n

Impact mapping starts with goal setting<\/a>.<\/p>\n

Product managers along with the senior stakeholders need to decide what they want to achieve and why. This will explain why you are doing<\/em> all the things.<\/p>\n

\"Goal<\/picture>
Goal Setting Framework.<\/figcaption><\/figure>\n

The goals could originate at different levels. They come from the business strategy or the product strategy<\/a>.<\/p>\n

What are examples of goals?<\/p>\n

Improving customer satisfaction <\/a>or increasing product adoption<\/a> are two common product manager goals<\/a>.<\/p>\n

Apart from choosing the goals, you also need to choose the right metrics<\/a> to ensure you have a reliable way to measure progress.<\/p>\n

Actors: WHO?<\/h3>\n

Actors <\/em>in the context of SaaS are the users.<\/p>\n

Every product is likely to have more than one user type, which we sometimes call a user persona<\/a>. Each of them has different needs, a different idea of value, and uses the product differently.<\/p>\n

Some of the actors, the on-stage ones, are easy to identify. For Jira, the well-known project management tool, these could include the scrum master, the product owner, the product manager<\/a>, or the developer.<\/p>\n

Others, like the administrators, work off-stage, so they\u2019re more difficult to find. However, they are often equally if not more important.<\/p>\n

Some of the actors have the potential to create a greater impact than others, so this is often where the first stage of prioritization takes place.<\/p>\n

\"User<\/picture>
User Persona Template.<\/figcaption><\/figure>\n

To improve the product for each of the groups, you need to know their jobs to be done<\/a>, their company background, and their pain points.<\/p>\n

Impacts: HOW?<\/h3>\n

Impact <\/em>is how you achieve the overall goal by influencing the user personas.<\/p>\n

For example, if you want to improve product adoption, you could do it by improving user onboarding<\/a>. However, the onboarding experience needs to be personalized for each of the user personas to make sure that they experience product value<\/a> in the quickest and most direct way.<\/p>\n

Deliverables: WHAT?<\/h3>\n

Deliverables are the actual features and functionality that you develop to make the desired impact on your actors. If the goals are the outcome, the deliverables are the output of your work.<\/p>\n

If you want to build on the onboarding <\/a>example above, these could be an interactive walkthrough<\/a> or a checklist <\/a>built in Userpilot <\/a>and customized for each of the users.<\/p>\n

To make sure your users get relevant guidance, you would need to segment them and trigger the relevant in-app guidance<\/a> for each of the segments independently.<\/p>\n

With Userpilot’s mobile SDK<\/a>, you can create targeted onboarding flows using slideouts, carousels, and push notifications without writing extra code.<\/span><\/p>\n

Bonus: User stories<\/h3>\n

Some teams like to enhance their impact maps with user stories<\/a>.<\/p>\n

This is when you combine the information about the actor, the impact, and the deliverable in one package that is easy to interpret for the developers.<\/p>\n

\"User<\/picture>
User story<\/a> template. Source: Powerslides.<\/figcaption><\/figure>\n

Want a specific example?<\/p>\n

As a<\/strong> scrum master, I want<\/strong> easy in-app access to the self-service resource center<\/a> so that I<\/strong> can solve my problem without leaving the app or contacting the support team.<\/p>\n

Bonus: Extended impact mapping<\/h3>\n

Another way to beef up your impact map is by adding information about the customer outcome. That’s how you create the extended impact map.<\/p>\n

The extended impact map below uses Scrum terminology. That’s why you see persona instead of actor and PBIs (Product Backlog Items) instead of deliverables. Impact has also been renamed – as Business impact – to reflect its true nature.<\/p>\n

However, the main difference is the customer outcome. This is what the customer persona benefits from the initiative. So the customer outcome from improved onboarding<\/a> is being able to start using the product more quickly to get their jobs done.<\/p>\n

\"Extended<\/picture>
Extended Impact Mapping. Source: Scrum.org.<\/figcaption><\/figure>\n

Some teams extend their impact maps by adding the experiments <\/a>as the last level.<\/p>\n

These are the ways to validate their ideas and assumptions, like prototyping <\/a>or fake door testing<\/a>. If you add this level to your impact map, it\u2019s going to look very much like an opportunity solution tree<\/a>, a product discovery tool<\/a> developed by Teresa Torres.<\/p>\n

\"Opportunity<\/picture>
Opportunity Solution Tree. Source: Product Talk.<\/figcaption><\/figure>\n

Impact mapping template tools<\/h2>\n

Now that you know the benefits of impact maps and what they’re made up of, let’s check out some tools that you can use to create them.<\/p>\n

UXPressia – user persona and journey mapping tool<\/h3>\n

UXPressia is a dedicated tool for creating user personas, customer journey maps<\/a>, and impact maps.<\/p>\n

The tool is very intuitive and easy to use and the impact maps are easy to read. The key advantage of the application is that your whole team can collaborate remotely and take part in multiple impact mapping exercises.<\/p>\n

UXPressia also allows you to integrate the user persona you’ve created before. Once your impact map is ready, you can easily export it into different formats like pdf or png for easy sharing.<\/p>\n

\"Impact<\/picture>
Impact Map in UXPressia.<\/figcaption><\/figure>\n

The main downside of UXPressia is the cost, especially for larger teams. Smaller teams working on up to 3 projects can get away with the Starter plan which comes at $160 per user per year.<\/p>\n

However, if you need more than that, you will have to pay $360 per team member for the Pro plan.<\/p>\n

\"UXPressia<\/picture>
UXPressia Pricing.<\/figcaption><\/figure>\n

Miro – whiteboard collaborative strategic planning tool<\/h3>\n

If you’re strapped for cash and still want to use a quality impact mapping tool, Miro could be the answer.<\/p>\n

The free plan comes with 3 editable boards. It may not seem much, but there’s no limit on how many frames you have in each of them. If you organize it properly, you can easily use it to create multiple maps.<\/p>\n

If not, the Starter plan comes at $96 per person per year and gives you unlimited boards.<\/p>\n

And that’s not the only advantage of Miro. While it is not a dedicated impact mapping tool, its diagramming functionality allows you to create great maps. And once you learn how to use it, there’s so much more you can do with Miro.<\/p>\n

Like UXPressia, Miro allows remote teams to collaborate in real-time on their projects. This is enhanced by integrations with popular video conferencing apps and project management tools like Jira and Confluence.<\/p>\n

Impact maps created in Miro are also easy to export, especially if you have any of the paid plans.<\/p>\n

\n
\n