User Story Mapping: Discover the Whole Story, Build the Right Product

by Jeff Patton

At the end of the day, your job is to minimize output, and maximize outcome and impact.

[2] The clean language and distinction between output and outcome was first made clear to me in a talk by Robert Fabricant called “Behavior Is Our Medium”. Prior to that, I’d struggled with language that was clear in my head—and everyone else’s too. Happily, it was clear in Robert’s head. [3] Because I strongly agree

I first heard this definition of a pattern from my friend Linda Rising: when you tell someone about a great idea and he says, “Yeah, we do something like that, too.” It’s not an invention, it’s a pattern.

The minimum viable product is the smallest product release that successfully achieves its desired outcomes.

minimal viable product is also the smallest thing you could create or do to prove or disprove an assumption.

But he’s one of its creators, so he should know. He revised the value about working software to read: Validated learning over working software (or comprehensive documentation)