ZeroBlockers vs Lean UX
A failed test should be able to stop the feature.
What it is
Agree the outcome, test cheaply, follow the evidence
Lean UX links business outcomes, user needs, assumptions, and experiments. The whole team learns together, and design documents come second.
Where it breaks
Discovery is covered, and delivery and scale are left open
Lean UX covers discovery in depth and asks for empowered, cross-functional teams. It says much less about how those teams build, release, and run what they learn, and it leaves open how they are funded, who decides when a test goes against the plan, and how many teams stay aligned. So organizations use what they already have: a roadmap of committed features.
When a test shows one of those features is wrong, the team is often told to build it anyway.
You will often see
- Hypotheses sit under a fixed roadmap.
- A test fails, and the feature ships anyway.
- Designers have nobody developing their craft.
How ZeroBlockers fixes it
The same learning loop, with the authority to act on it
Who carries the work from idea to satisfied customer
| Strategy and funding | Discover the problem | Test solutions | Build | Release | Run and measure | |
|---|---|---|---|---|---|---|
| Lean UX | Left to the organization | Cross-functional team | The same team, though the book says much less about how | |||
| ZeroBlockers | Product Team | Stream Team | ||||
Lean UX
- Strategy and fundingLeft to the organization
- Discover the problem to Test solutionsCross-functional team
- Build to Run and measureThe same team, though the book says much less about how
ZeroBlockers
- Strategy and fundingProduct Team
- Discover the problem to Run and measureStream Team
ZeroBlockers keeps the hypotheses and the small experiments, and carries them through delivery. The same team builds, releases, and runs what it learns, and checks how customers use it.
Leaders agree the outcome the team should improve, such as onboarding, and which decisions it makes alone, so it can stop or change a solution without asking. As more teams adopt it, a shared strategy and weekly reviews keep them aligned.
The usual reply
“Lean UX already asks for all of this.”
Lean UX practitioners will say the book already asks the organization to change. They will add that a team practicing Lean UX well earns this kind of authority over time, as leaders see its evidence.
It does, and ZeroBlockers agrees with the direction. The difference is how specific it gets. Lean UX describes what the organization needs to become. ZeroBlockers says who funds what, who decides what, and what the Weekly Product Review covers. Without those specifics, a team with permission to fail still reports against a feature roadmap.
01 / Side by side
How the approaches differ
- ProcessHow work moves from idea to live use
Lean UX
Covers discovery: regular research with users and the smallest test that answers the riskiest assumption. It says much less about building, releasing, and running the solution.
ZeroBlockers
Covers delivery as well as discovery. The team that runs the tests also builds, releases, and runs the solution, then checks how customers use it and decides what to change.
- StructureWho is on the team
Lean UX
Small, dedicated, cross-functional teams. What each team owns, and for how long, is left to the organization.
ZeroBlockers
A Stream Team of two to four designers and developers owns one part of the customer journey for the long term. Other specialists coach the team, but they do not do the work for it, as they would in a Center of Excellence.
- GovernanceHow success is judged and who decides
Lean UX
Teams are measured on outcomes in place of outputs. Who decides when a test goes against the plan is left open.
ZeroBlockers
Each quarterly outcome target is paired with a second measure that guards quality. Leaders agree in advance which decisions the team makes alone, such as stopping a feature, and the team reports them at the Weekly Product Review.
- FundingWhether the scope gets locked
Lean UX
Says nothing about funding, so teams often work inside a roadmap of funded features, and a failed test cannot stop a committed feature.
ZeroBlockers
Funds a customer scope, such as onboarding, with no feature list attached. The scope stays open, so dropping a feature needs no new approval.
- AlignmentHow many teams stay aligned
Lean UX
The Lean UX Canvas starts from a business problem. Who sets that problem, and how many teams stay pointed the same way, is left to the organization.
ZeroBlockers
The Product Team sets the strategy, and each Stream Team agrees quarterly outcome targets with it. Teams choose their own solutions within that strategy, and an agreed list says which decisions stay with leaders.
- ScalingSkills and the rest of the business
Lean UX
Cross-functional teams take designers out of the design group. The book’s chapter on organizational shifts covers culture, team organization, and process, and says little about who develops each discipline or how Legal, Finance, and Marketing work with the team.
ZeroBlockers
Enabling Teams coach each discipline across teams, and the design and development leads own careers. Internal Product Teams turn common requests to Legal, Security, and the platform into self-service.
02 / Why it differs
The differences explained
A failed test is wasted if the team must build the feature anyway
The Lean UX book says plainly that the method needs support from the organization. Its principles include teams that own problems, permission to fail, and outcomes over output, and it has a chapter on the changes an organization has to make. It describes the shifts an organization needs. It does not set out a funding model or say which decisions the team makes and which stay with leaders.
Jeff Gothelf, co-author of Lean UX, has made the same point about large frameworks that adopt it. SAFe, a framework for coordinating many teams, added Lean UX in its version 4.5. Asked how the two are supposed to work together, he wrote: “The short answer is, I have no idea.” His test is how easily an organization changes direction after a discovery. A team can learn that a feature is unnecessary and still be told to deliver it.
Three of the ZeroBlockers changes apply directly.
- Funding. Fund a customer scope, such as onboarding, for the year. Leaders review the investment every quarter, while the solution can change any week.
- Decision rights. A Stream Team is a small, persistent team that owns one part of the customer journey from research through live use. It decides whether to change course, keep going, or stop a solution. The Product Team, the leadership group for the product, owns strategy and investment and agrees outcome targets with the team.
- Review. In the Weekly Product Review, a 30-minute meeting between the Product Team and its Stream Teams, each team reports one thing it learned, one decision it made, and one decision it needs, along with its outcome numbers. A team that stopped a feature explains why and says what it will test next.
Keep the hypotheses and the small experiments. What changes is the commitment around them: Finance funds a customer scope in place of a feature list, and Sales sells outcomes in place of dated features.
Sources and comparison scope
Reviewed September 2026. This page compares ZeroBlockers with Lean UX as documented, with attributed practitioner accounts where available. Descriptions of Lean UX follow its published guidance. Claims about common practice are attributed where they come from a named source. Other statements about what organizations typically do are our analysis. The worked example is our analysis and reports no measured results.