What comes first: the outcome or the output? Today I'm chatting to Josh Seiden about one of my favorite topics: outcomes over outputs. Josh is actually the author of a book with that exact title, Outcomes over Output: Why customer behavior is the key metric for business success. Josh is also the co-author of Lean UX: Designing Great Products with Agile Teams, and Sense and Respond: How Successful Organizations Listen to Customers and Create New Products Continuously.
For Josh, the answer is clear: if we can define an outcome as a change in human behavior that creates value, then it's worth putting that ahead of the output or 'thing' we are creating.
This is a fascinating approach to redefining the way we work, the way we set OKRs, and the way we measure success. When the name of the game is efficient growth, defining your outcomes is crucial.
How do we make sure we are committing to the right work, though? And how do we articulate that to the teams that we build? Let's find out!
"Let's really think about what are the things that people value, what are the outcomes that we're trying to get, and then work backwards to get to the output we need to make." - Josh Seiden
In This Episode:
- Why outputs follow outcome
- Understanding how outcome is a change in human behavior (that creates value)
- What do we mean when we say "outcome"?
- What do we need to do to deliver an outcome?
- What are AGILE teams committing to stakeholders?
- How do we think about the way we organize our teams?