Product backlogs are much too often flooded with user stories, thwarting the basic agile tenet “Build – Measure – Learn”. Diligent adherence to agile rituals and short iterative cycles will not help if this driving factor is missing. This often leads to efficient teams building the wrong product, or, even worse, just investing into iterative delivery without reaping any of its benefits.
Impact mapping is a method that can spark this drive: it supports an iterative approach to product design that is often neglected when user story lists are simply prioritised in the product backlog. The method is highly visual and supports the entire project team throughout the process of discovering, prioritising and detailing customers’ requirements together.