ZeroBlockers vs Design Thinking
Good discovery needs an organization that can act on it.
What it is
A strong way to find the right problem and test ideas
Design Thinking is a human-centered approach to understanding problems, exploring possibilities and testing solutions. IDEO.org connects inspiration, ideation, and implementation in its human-centered approach.
Where it breaks
Discovery hands off to a separate delivery team
IDEO.org’s version names implementation as a phase, but it does not say who owns the solution once it is built, or who decides when customers prove the idea wrong. So organizations use what they already have. One group runs the research and workshops, and another team is funded to build whatever comes out of them.
The detail that mattered gets lost in the handoff, and findings from live use no longer reach the people who met the customers. The method also works on one challenge at a time, so the other teams and departments the solution depends on keep their own processes.
You will often see
- Research ends with a handoff deck.
- The delivery team never met the customers.
- Findings from live use have nowhere to go.
How ZeroBlockers fixes it
The same methods, in one team from research to live use
Who carries the work from idea to satisfied customer
| Strategy and funding | Discover the problem | Test solutions | Build | Release | Run and measure | |
|---|---|---|---|---|---|---|
| Design Thinking | Left to the organization | Design team | Left to the organization | |||
| ZeroBlockers | Product Team | Stream Team | ||||
Design Thinking
- Strategy and fundingLeft to the organization
- Discover the problem to Test solutionsDesign team
- Build to Run and measureLeft to the organization
ZeroBlockers
- Strategy and fundingProduct Team
- Discover the problem to Run and measureStream Team
ZeroBlockers keeps Design Thinking’s methods and puts them inside one team. The same designers and developers research the problem, build the solution, and watch how customers use it.
When customers prove an idea wrong, the same team changes it. The team is funded for a part of the customer journey, such as changing a booking, so the change needs no new budget.
The usual reply
“Good Design Thinking already includes delivery.”
Design leaders will say that IDEO.org’s approach runs through implementation, and that mature design organizations embed designers in product teams. In their experience, research and delivery are not split.
Where that is true, the handoff this page describes does not happen, and there is little to change. But since the method leaves open who owns the solution after launch and who decides when the evidence changes, many organizations retain the project delivery approach. ZeroBlockers settles those questions up front.
01 / Side by side
How the approaches differ
- ProcessHow work moves from idea to live use
Design Thinking
Covers discovery in depth: empathy, framing the problem, ideas, prototypes, and tests. The popular five-stage version stops at testing, and implementation gets far less detail.
ZeroBlockers
Covers delivery as well as discovery. The team that tests the ideas also builds, releases, and runs the solution, and watches how customers use it.
- StructureWho is on the team
Design Thinking
Leaves open who does the work, so research and workshops often sit with one group and delivery with another.
ZeroBlockers
One Stream Team of designers and developers researches, builds, and runs one part of the customer journey, with no handoff.
- GovernanceHow success is judged and who decides
Design Thinking
Evidence can change how the team sees the problem. Who decides when customers prove a built idea wrong is left open.
ZeroBlockers
Outcome targets, each paired with a quality measure, are reviewed every week. The team can change or drop a solution itself and reports the decision.
- FundingWhether the scope gets locked
Design Thinking
Treats staffing and funding as project tasks, so the chosen idea often becomes a funded project with a fixed scope.
ZeroBlockers
Funds a customer scope, such as changing a booking, so the solution can change without a new budget.
- AlignmentHow many teams stay aligned
Design Thinking
Works on one challenge at a time. How many teams stay aligned is left to the organization.
ZeroBlockers
The Product Team sets the strategy and agrees outcome targets with each team, and teams choose solutions within them.
- ScalingSkills and the rest of the business
Design Thinking
Leaves open how the team works with specialists and the rest of the business, which keep their own processes.
ZeroBlockers
Internal Product Teams turn common requests to Legal, Security, and the platform into self-service, so the team does not wait in another group’s queue.
02 / Why it differs
The differences explained
Handoffs lose what discovery learned
IDEO.org’s human-centered approach has three phases: inspiration, ideation, and implementation. The first two are rich in methods for understanding people and generating ideas. Implementation gets far less detail, and it treats staffing and funding as tasks for the project. The popular five-stage version, from empathize to test, stops before implementation. Neither says who owns the solution after launch or who decides when the evidence changes. So organizations use what they already have: a discovery phase first, then a delivery project with its own budget and fixed scope.
Once the delivery team has committed to that scope, new evidence has nowhere to go. The team did not meet the customers, so it cannot judge the finding. Its sponsor approved a fixed scope, so it cannot act on the finding either. A better research report fixes neither problem.
A ZeroBlockers Stream Team owns one part of the customer journey. Its designers and developers interview customers, test ideas, build, and watch live use together. When a finding arrives, the people who have to act on it were in the room when it was found.
A team that tests an idea must be able to drop it
Good discovery lowers the risk of building the wrong thing, but it cannot remove it. Once early releases reach customers, the feedback keeps coming, and some of it will show that the idea does not work. In a delivery project that feedback has nowhere to go. The business case pays for the agreed scope, so the team keeps building it. Often the right move is to change the solution, or to stop the feature and spend the time on something else.
ZeroBlockers funds the customer scope, such as helping travelers change a booking. The Product Team, the leadership group for the product, sets strategy and agrees outcome targets. The Stream Team chooses the solution and can stop a weak one without asking permission.
The Weekly Product Review looks at what the team has already learned and decided, and experiments do not wait for it. Only some decisions stay above the team, such as customer contracts or pricing.
Discovery needs customers and time every week
AI makes it quick to produce convincing prototypes, but it tells you nothing new about your customers. A polished prototype is still a guess until real people use it. Teams need regular access to the right customers, the skill to learn from them, and time to watch what happens after release.
ZeroBlockers puts research into the team’s working week. Research, operations, and delivery all compete for a small team’s time, and leaders need to help it limit work. Enabling Teams, senior specialists who coach the teams, raise the quality of that research.
Sources and comparison scope
Reviewed September 2026. This page compares ZeroBlockers with Design Thinking as documented, with attributed practitioner accounts where available. Descriptions of Design Thinking 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.