How to make an impact with your software product

rightquestions

In this blog post I would like to raise awareness about Impact Mapping –  a game-changing method I learned last week on a training with Jef Cumps. This method can significantly improve the way many teams and organisations build products. This blog post describes the way how to use this technique.

What is Impact Mapping?

Impact mapping is a planning technique that helps companies from getting lost while building their products by clearly communicating assumptions and business objectives in order to make better roadmap decisions. This tool is useful for all people involved in building software products like Product Owners, Product Managers, Scrum Masters etc.

What you can expect:

This method will bring you usability and speed to proven product- and project management strategies. It helps you to reduce waste and to enhance collaboration by creating a big-picture of your business that teams can use to prioritize their product backlog by business value. Finally, it helps you that the right business goals will be achieved and that unrealistic features will be kicked out of your backlog before they cost too much money.

How to do it:


Why do you do this?

In the first step you have to answer one “simple” question: Why do you want this product?

As a feature should have a direct impact to your business model, it’s important to know the main objectives for the product. So you should clearly agree on measurable goals by gathering the why-items. For example you want to drive more sales in your online shop or you want to increase the number of reviews on your platform.

Understanding your business is the most essential thing! Assumptions are just worthless without understanding the Business Model because they are out of context. You might be able to generate more money without understanding the business – but only one time and that’s it. Customer might not come back! Therefore you need to be able to measure if the feature has a long-term impact on your product.

Who can help or obstruct us?

Next, you list the user roles who will be impacted by the objective. This allows you to discover and formulate the desired changes in behavior for reaching it (Persona’s are often used to create such tangible ‘example users’ in order to facilitate communication and requirements understanding). Keep in mind that there might be several personas such as coordinators, marketing guys, accounting staff or the end-customer. That depends strongly on your product. Identify those people that can help you reach your objective, obstruct you in reaching it, or that will be impacted by the new product.

How will they be impacted?

Once you have defined the user roles you need to find out how they will be impacted and how their behavior will change by your goals.

Let’s say your goal is to generate more reviews for your articles in your online shop. How would your daily visitors be impacted if they would see more reviews on your listed products? How would your call center be impacted by more reviews? An assumption would be that call center would receive less phone calls because the new reviews already answered the customer´s question.

why-who-how

What will the feature do to support the desired impact?

Now you start to write vague product features (what) that are needed to support the desired impact. Don’t write any solution on this story as this is still a big and vague story. Once you collected these items on your product backlog you can decide and prioritize what is the most important valuable piece of software you want to ship! Next, you can start splitting (the most important of) these big product features into user stories to create a healthy Product Backlog.

From now on you can and should regularly cross-check all your stories with your goals – even the existing ones:

impact-mapping

Don’t implement the whole map. Find the shortest way to your objective!

Don’t hesitate to kick Items out of your product backlog if there is no fit to none of your goals. I would even say kick the ones with the lowest value as there might be other stories with much more value pointing to another goal.

In the end you will always have a Product Backlog prioritized by business value. Don’t put too much in it. There is nothing worse to have a backlog for the next 6 month. Just concentrate on the next logical step by pulling the item with the highest business value.

product-backlog


 

impact-mapping-questions

The Impact Mapping tool is the right tool to evaluate your assumptions as this map will trigger the right discussions within your organisation. Make it visually and beautiful in your office to get more benefit out of it.

If you want to learn more read this book about Impact Mapping!

Did you like the post? Send me a feedback. I would love to hear from you!

Leave a star rating for Impact Mapping:
1 Star2 Stars3 Stars4 Stars5 Stars (10 votes, average: 4.90 out of 5)

Loading...

 

14 comments

  1. Pingback: In the News: 2014-11-21 | Klaus' Korner

  2. Pingback: Customer Journey Mapping - Agile Breakfast Nr. 18 - Sybit Blog

  3. Pingback: How to power up your user story

  4. Pingback: Story Mapping - Discover the whole story of your productDominic Krimmer

  5. Pingback: Story Mapping - Discover the whole story of your product

  6. Thank you for your very interesting post, Dominic. I’m very interested in IM as an approach since I had an idea on writing user stories that can benefit greatly from IM, since it’s taking the real user intent into the focus. I call this approach “Intentional Epics & Functional User Stories”. If you like, you can read about it in my blog post: romanbrendel.com/a-different-approach-to-writing-user-stories

    Maybe this is something that you find useful. I’d really like to get your feedback on it.

  7. Pingback: Customer Journey Mapping - Agile Breakfast Nr. 18 - Sybit Agile

  8. Hello

    Wonderful, Thank you for your very knowledgeable post. If possible please explain that what is the connectivity IM with BDD

  9. Pingback: 5 Dinge an denen man erfolgreiche Scrum Teams erkennt | Marc Löffler

  10. Pingback: 5 success factors of incredible good Scrum teams | Marc Löffler

Leave a Reply

Required fields are marked *.


Read more in Agile, Coaching
The LEGO® – Retrospective

The LEGO® - Retrospective is a quite nice method I tried out with a team in my current company. The...

Close