Lean UX: Applying Lean Principles to Improve User Experience

Assumptions
A high-level declaration of what we believe to be true.
Hypotheses
More granular descriptions of our assumptions that target specific areas of our product or workflow for experimentation.
Outcomes
The signal we seek from the market to help us validate or invalidate our hypotheses. These are often quantitative but can also be qualitative.
Personas
Models of the people for whom we believe we are solving a problem.
Features
The product changes or improvements we believe will drive the outcomes we seek.
Let’s take a look at each one of these elements in further detail.

Our goal is not to create a deliverable, it’s to change something in the world—to create an outcome.

Lean UX is based on the idea that we begin our work with an assumption.

Documents don’t solve customer problems—good products do.

The team’s focus should be on learning which features have the biggest impact on the their customers.

They had spent their semester theorizing about

They had spent the entire semester working as quickly as they could to make pots. Sometimes they succeeded, and sometimes they failed. With each iteration, each experiment, they learned. From that learning, they became better able to achieve the end goal: making high-quality clay pots.

frequent failures lead to increased mastery of skills.

is from those risks that big ideas ultimately come.

untested and unimplemented design ideas