Lean UX: Designing Great Products with Agile Teams

by Jeff Gothelf

Building a pixel-perfect specification might be a route to rake in six-figure consulting fees, but it’s not a way to make a meaningful difference to a real product that is crucial to real users.

the sooner we get our ideas out, the sooner we can figure out what those revisions should be.

It’s not iteration if you do it only once. — Jeff Patton

Teams must be able to interact with customers directly in order to get the feedback they need to create effective solutions.

We believe [this statement is true]. We will know we’re [right/wrong] when we see the following feedback from the market: [qualitative feedback] and/or [quantitative feedback] and/or [key performance indicator change].

If the feature is just a cool idea, but not in service of a user outcome, it’s unlikely to create value.

Lean UX begins with the idea that user experience design should be a collaborative process.

collaboration yields better results than hero-based design (the practice of calling in a designer or design team to drop in, come up with something beautiful, and take off to rescue the next project).