ComparisonScaling Software Development - ZeroBlockers vs Design Thinking: Which problem-solving framework is better for you?
There is no one-size-fits-all framework for software development. Each framework covers different parts of the process in different ways. We have compiled an overview of the key features and approaches of the Design Thinking framework and ZeroBlockers to help you select the best framework for you.
ZeroBlockers vs Design Thinking: Overview
| Scroll | Idea Generation | Idea Evaluation | Business Case Creation | Business Case Approval | Plan | Analyse | Design | Develop | Test | Release |
|---|---|---|---|---|---|---|---|---|---|---|
| Design Thinking | ||||||||||
| ZeroBlockers | Step Removed | Step Removed |
Feature comparison
ZeroBlockers
Effective products with empowered autonomous teams
Framework
- Process
The core way of working.
- Discover opportunities, design and evaluate solutions, then deliver in very small iterations.
- Deliverables
The outputs of the process.
- User personas
User journey maps
Problem statements
Ideation boards
Prototypes
Working Software - Alignment
How solutions are handed over to the development team.
- No handover as designers and developers work together at all stages.
- Success Metrics
How success is measured.
- Customer satisfaction and impact on metrics.
Design Thinking
A non-linear, iterative process to understand users, and create innovative solutions to prototype and test
Framework
- Process
The core way of working.
- Empathise with customers, define their problems, ideate, prototype, test and implement.
- Deliverables
The outputs of the process.
- User personas
User journey maps
Problem statements
Ideation boards
Prototypes
User feedback and insights reports - Alignment
How solutions are handed over to the development team.
- Working prototypes with specifications and user insights reports.
- Success Metrics
How success is measured.
- Customer satisfaction and impact on metrics.
Core Differences
Framework
- Process
The core way of working.
- Defining the best solution and delivering
versus
just focusing on solution definition. - Deliverables
The outputs of the process.
- Very similar deliverables until the execution of the solutions.
- Alignment
How solutions are handed over to the development team.
- Continuous collaboration between research, design and dev
versus
handover from design to dev. - Success Metrics
How success is measured.
- Evaluating solutions right up until working software
versus
evaluating solutions up until dev handover.
ZeroBlockers unapologetically copies a lot of the solution identification and evaluation techniques from Design Thinking so there is a lot of overlap, particularly in the process, deliverables and success metrics.
But Design Thinking only goes as far as the solution identification. While these techniques definitely reduce the risk over whiteboard solutions there is still a lot of risk remaining. Until a customer has a working solution in their hand we can't know for certain whether it will be successful. ZeroBlockers includes the development phase as well as the solution phase because we will need to iterate on the solution as we build it as well.
ZeroBlockers vs Design Thinking: Approach
Feature comparison
ZeroBlockers
Effective products with empowered autonomous teams
Efficiency
- Time to Market
The time from when you identify an opportunity until the software is in place.
- Short lead time is a key metric for teams.
- Cost
The resources involved in defining solutions.
- Focus on minimising time (and cost) to market.
Design Thinking
A non-linear, iterative process to understand users, and create innovative solutions to prototype and test
Efficiency
- Time to Market
The time from when you identify an opportunity until the software is in place.
- Can be quick or slow depending on implementation.
- Cost
The resources involved in defining solutions.
- Can be cheap or expensive depending on implementation.
Core Differences
Efficiency
- Time to Market
The time from when you identify an opportunity until the software is in place.
- Short lead time as a core metric
versus
implementation time left up to teams. - Cost
The resources involved in defining solutions.
- Short lead time as a core metric
versus
implementation time left up to teams.
Design Thinking is very flexible in terms of how you implement it which makes a direct comparison a bit subjective.
ZeroBlockers is more opinionated as it makes Lead Time a core metric that teams are measured on. This means that teams must come up with innovative ways to do continuous research and prototype evaluation to ensure that they balance the investment in research and risk reduction with delivery.
Feature comparison
ZeroBlockers
Effective products with empowered autonomous teams
Effectiveness
- Customer Satisfaction
How well the solutions meet the needs of the customers
- Involve users continuously to iterate and refine the software based on their feedback.
- Innovation
The level of ingenuity in the solutions that are delivered.
- Cross-functional teams, with development involvement, and a customer focus deliver better solutions.
- Business Alignment
How well the solutions align with the business goals.
- Ensures solutions are aligned with business strategic objectives.
Design Thinking
A non-linear, iterative process to understand users, and create innovative solutions to prototype and test
Effectiveness
- Customer Satisfaction
How well the solutions meet the needs of the customers
- Involve users continuously to iterate and refine the solution based on their feedback.
- Innovation
The level of ingenuity in the solutions that are delivered.
- Cross-functional teams, with recommended developer involvement, and a customer focus deliver better solutions
- Business Alignment
How well the solutions align with the business goals.
- Ensures solutions are aligned with business strategic objectives.
Core Differences
Effectiveness
- Customer Satisfaction
How well the solutions meet the needs of the customers
- Evaluating solutions using prototypes and software
versus
just evaluating up to the prototype stage. - Innovation
The level of ingenuity in the solutions that are delivered.
- Ensure developer involvement to incorporate tech angle into solutions
versus
recommendation to involve developers. - Business Alignment
How well the solutions align with the business goals.
- Similar between frameworks.
Both frameworks identify that research and solution evaluation increases the effectiveness of the solutions we build.
The big difference is that Design Thinking only goes as far as the solution identification so there is still a lot of risk remaining. Until a customer has a working solution in their hand we can't know for certain whether it will be successful. ZeroBlockers includes the development phase as well as the solution phase because we will need to iterate on the solution as we build it as well.
ZeroBlockers vs Design Thinking: Team & Events
Feature comparison
ZeroBlockers
Effective products with empowered autonomous teams
Team Level
- Roles
The roles involved in creating the products.
- UX Researcher
Designer
Developers
Business SMEs as needed - Events
The key activities that teams perform while building the product.
- Ad-hoc
Customer Interviews
Ideation
Solution Evaluation
User Story Mapping
Daily
Retrospective
Weekly
Weekly Business Review
1-on1's
Design Thinking
A non-linear, iterative process to understand users, and create innovative solutions to prototype and test
Team Level
- Roles
The roles involved in creating the products.
- Researcher
Designer
Coach
Business SMEs as needed
Stakeholder - Events
The key activities that teams perform while building the product.
- Ad-hoc
Customer Interviews
Ideation
Solution Evaluation
Core Differences
Team Level
- Roles
The roles involved in creating the products.
- Skills to identify, evaluate and build solutions
versus
just skills to identify and evaluate solutions. - Events
The key activities that teams perform while building the product.
- Researching, validating and building solutions
versus
just researching and validating solutions.
Both frameworks advocate for cross-functional teams but Design Thinking stops at the solution identification stage so developers are not explicitly included. This leaves a gap in terms of identifying technical solutions to customer problems.
ZeroBlockers believes that the separation of thinkers (solution definers) and doers (developers) leads to problems because you need developers to be able to iterate quickly as feedback comes in. We don't want to introduce a sign off blocker.
ZeroBlockers vs Design Thinking: Implementation
Feature comparison
ZeroBlockers
Effective products with empowered autonomous teams
Implementation
- Buy In
The people you need committed to ensure a successful roll-out.
- Considerable changes are required across the business so buy-in is required at a senior level in IT, marketing, customer service and more.
- Training
The training and certification required for a successful implementation.
- ZeroBlockers provides a range of training and certifications for each role.
- Community & Support
The support available for implementing the framework.
- Large and growing community with documentation and resources.
Design Thinking
A non-linear, iterative process to understand users, and create innovative solutions to prototype and test
Implementation
- Buy In
The people you need committed to ensure a successful roll-out.
- Buy in required from business and technology leadership to provide funding and cross-functional teams.
- Training
The training and certification required for a successful implementation.
- A number of training courses are available for each role.
- Community & Support
The support available for implementing the framework.
- There is a large and active Design Thinking community.
Core Differences
Implementation
- Buy In
The people you need committed to ensure a successful roll-out.
- Similar between frameworks
- Training
The training and certification required for a successful implementation.
- Similar between frameworks
- Community & Support
The support available for implementing the framework.
- Similar between frameworks
Both frameworks require a large change to how companies identify the product features that they should build. ZeroBlockers is a little more complicated because it includes teams that are cross-functional across the business and IT divide as well.
While ZeroBlockers is challenging to implement you can start small - one product, one value stream. With over 10 years of UXDX content and case studies, there is also a large body of resources to assist in the rollout of the framework. The pain is worth the gain.
