Book Sips #9 — ‘Outcomes over output’ by Joshua Seiden
When it comes to product and services, the same story is repeated over and over: solution-mode kicks in before understanding the problem, teams top their backlogs up with features and time-to-market is shortened by sacrificing the impact of what it’s been built. Enough! do read this book!
Josh Seiden exposes the importance of adopting an outcome-based design approach when it comes to delivering best in class products/services, but also to organize orgs accordingly. Asking ‘the magic questions’, conducting low-risk experiments and creating a common vocabulary (for example, mapping the customer journey experiences) in order to address the right challenges are all key parts of the agile equation. A sip:
‘In outcome-based work, teams need to be really clear about the value they’re trying to create, and they do this by specifying two critical outcomes of the work: the outcome they’re seeking for the customer or user, and the outcome they are seeking for the business. These two outcomes must be linked. In other words, you have to have theory that if you create a certain outcome for the customer, this will result in a specific outcome for the business: If we create “this” outcome for the user, it will deliver “this” outcome for the business’
Always keep your design alive as a ‘Work In Progress’ by embracing customer behavior to inform features’ iterations.
#joshdixit
Outcomes over output
by Joshua Seiden
Why read?
To take a software-based approach in business. To really apply agile methodologies in your teams. To realize the actual impact of building to learn in potentially infinite iterations.
40 minutes read, Sense&Respond Press
