Most teams don’t suffer from a lack of effort — they suffer from a lack of alignment. Misaligned goals, unclear boundaries, and a focus on internal priorities over real user needs leads to frustration, delays, and wasted potential.
User Needs Mapping offers a practical, visual method for reconnecting your organisation to the people it’s meant to serve. Whether you're leading a digital transformation, evolving your team structures, or simply trying to reduce friction and focus on what matters most, this book gives you the tools
Expose hidden dependencies and misaligned responsibilities
Identify and articulate genuine user needs — internal or external
Make better decisions about team design, capabilities, and services
Navigate tension between competing wants, needs, and feasibility
Create clarity and purpose for everyone involved
Through real-world case studies and straightforward guidance, User Needs Mapping shows facilitators, leaders, and change agents how to put these ideas into practice. You’ll learn how to make alignment visible, turn complexity into clarity, and enable teams to deliver meaningful outcomes.
If you’re ready to align your teams around what truly matters — and unlock faster, more meaningful flow of value — this book will show you how.
🌟 What the experts “User Needs Mapping is a vital approach for any leader who wants to empower teams to be good stewards of meaningful outcomes...I am confident it will help you and your teams deliver value with less friction and more meaning.”
— Matthew Skelton, Co-author, Team Topologies
“If a Wardley Map gives you the landscape, UNM shows you what has been sitting at the end of your street all along.”
— Simon Wardley, Researcher, explorer of maps, recovering CEO
This book is super-practical. It builds on and combines various ideas into this thing called User Needs Mapping. You don't have to get deep into the academic side to get value from this, you can just do it. I really like the practical examples of how to define needs badly and well as they make it super clear what you're trying to capture. There's lots of ways to apply the different mapping techniques and then make adjustments to your set up to get closer to autonomous cross-functional teams working with high alignment.
We spend a ridiculous amount of time debating solutions without ever agreeing on the actual user need. Just finished reading the book and it’s shifted how I think about this. The book pushes you to flip that pattern: stay with the problem longer, write outcomes that are agnostic to any solution, and only then talk about how you might solve it. That mindset shift alone feels worth the read!