ZeroBlockers vs User-Centered Design
Research has to reach the team before it builds.
What it is
Keep the people who use the product at the center
User-Centered Design puts the people who use a product, their tasks, and their situation at the center of design and testing. The ISO standard applies it across the whole life of a product.
Where it breaks
Research arrives after the team has built
User-Centered Design expects users to be involved all the way through development, but it says little about how research and delivery fit into one team, or how researchers are shared across many teams. So research often becomes a separate service the delivery team has to request.
The team builds while it waits, and the findings arrive after the decision is made. With AI the team can build far more before the research comes back.
You will often see
- Teams wait for a research slot.
- Findings arrive after the build.
- Research reports critique features already shipped.
How ZeroBlockers fixes it
The same user focus, with research inside the team
Who carries the work from idea to satisfied customer
| Strategy and funding | Discover the problem | Test solutions | Build | Release | Run and measure | |
|---|---|---|---|---|---|---|
| User-Centered Design | Left to the organization | Multidisciplinary design team | Left to the organization | |||
| ZeroBlockers | Product Team | Stream Team | ||||
User-Centered Design
- Strategy and fundingLeft to the organization
- Discover the problem to Test solutionsMultidisciplinary design team
- Build to Run and measureLeft to the organization
ZeroBlockers
- Strategy and fundingProduct Team
- Discover the problem to Run and measureStream Team
ZeroBlockers keeps user-centered methods and puts research inside the team. The same designers and developers talk to customers, build the solution, and check how it works in live use.
Senior specialists coach them on harder research methods and accessibility, and the team can change a solution as soon as the evidence shows a problem.
The usual reply
“Research quality drops when non-researchers run it.”
Research leaders will say that research run by designers and developers produces leading questions and confirms what the team already believes. They will add that a central research team sees patterns across products that no single team can see.
Both risks are real. ZeroBlockers answers the first with coaching from specialists, specialist evaluation where it is needed, such as accessibility, and dependable support for recruiting participants. The second is worth keeping: a small central group can still pull findings together across products. What changes is that routine research no longer waits in a queue while the team builds.
01 / Side by side
How the approaches differ
- ProcessHow work moves from idea to live use
User-Centered Design
Understand the context, specify requirements, design, and evaluate, repeating across the life of the system. Where research sits is left open, so it often arrives late from a central queue.
ZeroBlockers
Research is part of the team’s working week, so findings arrive before the decision is made. The same team builds, releases, and checks the live result.
- StructureWho is on the team
User-Centered Design
Asks for a multidisciplinary team. In practice, researchers often sit in a central team that delivery teams request time from.
ZeroBlockers
Each Stream Team has its own designers, who lead the research, and developers who take part in it.
- GovernanceHow success is judged and who decides
User-Centered Design
Expects designs to change in response to evaluation. Whether a finding can change a committed plan is left to the organization.
ZeroBlockers
The team changes a solution as soon as the evidence shows a problem, within agreed accessibility, quality, and risk limits. Each outcome is paired with a measure that shows harm.
- FundingWhether the scope gets locked
User-Centered Design
Says nothing about funding, so findings often have to fight a committed feature plan.
ZeroBlockers
Funds a part of the customer journey in place of a feature list, so the plan can change when research shows a problem.
- AlignmentHow many teams stay aligned
User-Centered Design
Works on one system 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
User-Centered Design
Asks for multidisciplinary teams without saying who develops each discipline’s craft. Recruiting participants and accessibility testing are left to each team.
ZeroBlockers
Enabling Teams coach teams on harder research methods and accessibility, and functional leads own careers. Leaders fund shared support for recruiting participants and handling research data.
02 / Why it differs
The differences explained
Research that arrives late cannot change what was built
ISO 9241-210 covers human-centered design across the whole life of an interactive system, with users involved long after the first round of research, and it asks for a multidisciplinary team. It does not say where research sits, how that team is funded, or who decides when a finding conflicts with the plan. So organizations use what they already have: a central research team that delivery teams request time from, and a committed plan the findings have to fight.
When research comes from a separate queue, the team often builds before it understands the task. More building capacity widens that gap. AI can generate many more screens, and none of them prove that anyone checked the needs of the people who will use them.
ZeroBlockers puts research into the Stream Team, a small, persistent team that owns one part of the customer journey. Its designer leads the research and the developers take part. The same team chooses the solution, builds it, and checks live results. A finding goes straight to the people who can act on it.
A small team still needs specialists to call on
One designer cannot be an expert in every research method, domain, and accessibility need. ZeroBlockers Enabling Teams, senior specialists who coach teams, fill that gap. They also write guidance and run communities of practice. The Product Team, the leadership group for the product, stays responsible for hiring and skills.
Customer access needs dependable support too: recruiting participants, getting consent, running accessible sessions, and handling research data properly. Leaders fund that support alongside delivery, so research never depends on a designer calling in favors.
W3C recommends involving users with disabilities and combining that with formal accessibility evaluation. Stream Teams do both, with specialists joining for the formal evaluation.
A finding only matters if the team can change the plan
ISO 9241-210 expects designs to change in response to evaluation, which only happens if the plan can change. ZeroBlockers funds a part of the customer journey in place of a feature list, so the team can change a solution as soon as research shows a problem.
A higher completion rate can hide people accepting a choice they did not understand. So each customer outcome is paired with a second measure that shows damage, such as incorrect changes, complaints, or cancellations. Research sessions explain the behavior behind the numbers. The Product Team agrees those targets with the team, and the Weekly Product Review looks at the evidence and at decisions still open. The team changes a solution within its limits straight away. Only a serious policy or commercial issue goes to the leader who owns it.
Sources and comparison scope
Reviewed September 2026. This page compares ZeroBlockers with User-Centered Design as documented, with attributed practitioner accounts where available. Descriptions of User-Centered Design 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.