The question isn't 'what should we design?' It's 'what do we need to learn?' Lean UX trades 40-page specs for hypotheses you can actually test.
About the book
Gothelf and Seiden replace the traditional design waterfall -- requirements to wireframes to specs to code, losing context at every handoff -- with a tighter loop: declare your assumptions, write a testable hypothesis, run the lowest-fidelity experiment that can answer it, and design collaboratively with the whole team instead of handing off polished mockups. The core shift is outcomes over outputs: a design's value is measured by the behavior change it produces, not the fidelity of the deliverable, and that runs on a weekly research cadence integrated into Agile's dual tracks.
Best used for
—Writing a hypothesis statement (persona, action, outcome, signal) before wireframing a feature
—Running a Design Studio session to get engineers and PMs sketching alongside designers
—Choosing the lowest-fidelity experiment -- paper prototype, smoke test, Wizard of Oz -- that can validate an assumption
“The best UX book I've read. Very practical, gives actual exercises and templates. Lots of examples and organized well.”
— Haley, Goodreads
Install this skill
Run this command in your terminal. The skill will be available in all your Claude Code projects.