When we develop products, we're responsible for maximizing the value we deliver to the customer. In order to do this, we have to understand who we're actually building the products for. We need to know who the customer is, what problem(s) we're trying to solve for them, and any additional information we can gather that will give us more insight into their needs and how we can address them. We also need to have an awareness of where our assumptions about the customer may be introducing risk. Unfortunately, we often get so focused on creating and delivering that this area of focus doesn't receive the level of attention that's needed to ensure that we're solving the right problem(s) in the best way possible.
In this episode of SoundNotes, LeadingAgile SVP and Executive Consultant, Scott Sehlhorst makes the case for why this work is so important and why empathy maps are such a critical (and often ignored) aspect of this work. Scott and Dave talk through a step-by-step approach you can use