DDD Europe 2024 - Program

Impact Mapping

Main Conference - Hands-on Lab


Krisztina Hirth

Krisztina Hirth
Thursday 30 from 11:00 until 13:00

(This is a hands-on lab with limited capacity)

"Impact mapping is a lightweight, collaborative planning technique for teams that want to make a big impact with software products. It is based on user interaction design, outcome-driven planning and mind mapping. Impact maps help delivery teams and stakeholders visualise roadmaps, explain how deliverables connect to user needs and communicate how user outcomes relate to higher-level organisational goals." (source: https://www.impactmapping.org/)

Impact Mapping is a unique technique (described in a book by Gojko Adzic) which enables every organisation or team facing a new problem, a new challenge to not only find unexpected ideas but also to make sure that these ideas address those challenges instead of fulfilling other interests. By following the steps, Impact Mapping helps find ways to experiment, innovate, and compare possible ideas by focusing on the outcome rather than the output. It gives the group the means to verify the progress the whole time - to fail fast or stop investing because they have reached their goal.

In this workshop, we will discuss and map a fictional problem. At the end of the workshop, you will know how the technique works and when to use it, how much fun such Impact Mapping can be and how creative people are when the only constraint is time :)


Everything needed as preparation for this workshop is on this pdf: https://drive.google.com/file/d/1YZ17SoEzoytoDkO5LPgG79-E6lc_5c2U/view?usp=sharing

There are no laptops required.

About Krisztina Hirth

Software engineer for more than 20 years, always looking for the right way to deliver reliable, resilient and expandable value through software, knowledge and empathy. Lately, I changed roles to help teams and companies to understand the benefits of domain-driven design, to enjoy discovering models before applying patterns :) I believe that agility is nothing else than feedback-driven development, that DDD and domain modelling reduce the waste of energy, time and future technical debt and that work must be fun.