Explore diverse design solutions simultaneously by having multiple teams independently solve the same problem.
Parallel Design has multiple designers independently create solutions to the same problem, then combines the strongest ideas into one concept.
Parallel Design is a collaborative design methodology where multiple designers or small teams independently create solutions to the same design problem within the same timeframe, then reconvene to compare, critique, and merge the strongest elements into a unified concept. By guaranteeing that genuinely different approaches are explored before convergence, parallel design counteracts the groupthink and tunnel vision that commonly occur when a single team iterates on one direction from the start. Product designers, UX teams, innovation labs, and design agencies use parallel design when the stakes are high enough to justify the additional resource investment. The method is particularly valuable for complex design challenges where the optimal solution is not obvious, where early commitment to the wrong direction would be costly, and where diverse perspectives are likely to produce meaningfully different approaches. While more resource-intensive than serial iteration, parallel design consistently produces higher-quality outcomes because the final unified solution draws from a broader pool of ideas and has been stress-tested through cross-team critique. The method also builds team engagement, as designers feel greater ownership when their ideas have a genuine chance of shaping the final product.
Create small design groups, ideally composed of 3-4 individuals, which can include UX designers, developers, and stakeholders. Each team will work independently on designing solutions for the same problem.
Clearly outline the goals, objectives, and requirements of the project. Each team should have a solid understanding of the problem they need to solve, target users, and any constraints or restrictions that may apply to the design.
Determine the appropriate amount of time for the design exercise. Give each team a deadline by which they need to present their design solutions. The timeline can be anywhere from a few hours to a couple of days, depending on the scale and complexity of the project.
Each team works independently to design their own unique solution to the problem. Encourage divergent thinking and exploration of different ideas during this phase. Teams should focus on creating functional prototypes or wireframes which represent their design solutions.
Bring all teams together to present their design solutions to the larger group. Encourage open discussion and critique of each solution, identifying strengths and weaknesses in each design. Look for trends and common elements among the different designs.
From the discussions, identify the best ideas, features, or components from each design. Work towards combining these elements into a single, cohesive design solution. It may be helpful to have a group discussion or voting process for selecting the best ideas.
Use the selected best ideas to create a unified design solution. Assign a smaller team or individual to integrate the different features and elements from the various solutions into a single, cohesive prototype or wireframe design.
Conduct usability tests on the unified design solution to evaluate its effectiveness in solving the original problem. Gather feedback from the target users and analyze the findings to identify areas of improvement.
Based on usability testing feedback, iterate on the design, making necessary improvements and refinements. Continue iterating and testing until the design meets the project goals and objectives, and provides a satisfying user experience.
Once the final design is developed and tested, implement the solution and launch the product. Monitor user engagement and gather feedback post-launch to fine-tune the design as needed for ongoing improvements.
After completing a parallel design process, the team will have explored the solution space far more broadly than serial iteration would allow, producing multiple genuinely different design concepts. The cross-team review will have identified the strongest elements from each approach, and the unified design will combine these into a solution that is more robust and well-considered than any single team's work. The team will have documented why specific approaches were selected or rejected, creating a valuable decision log. Usability testing of the unified design will validate that the merged elements work together effectively. Beyond the design artifact, the process builds team morale and investment, as every participant sees their contributions reflected in the final product.
This method is resource-intensive - ensure the design stakes justify the investment of multiple teams.
Compose balanced teams with complementary skills rather than grouping all senior designers together.
Give all teams identical briefs and constraints to ensure fair comparison of approaches.
Keep teams isolated during the design phase to prevent premature convergence on one idea.
Establish clear criteria for evaluating designs before the reveal session begins.
Look for surprising combinations - the best final design often merges ideas from multiple teams.
Document why certain approaches were rejected, not just why others were chosen.
Combine parallel design with usability testing to validate the merged solution with real users.
When teams share work in progress before the formal review session, their designs converge prematurely. Keep teams strictly isolated during the design phase to ensure genuinely different approaches emerge from each group.
Putting all the experienced designers on one team creates an unfair comparison and demoralizes other groups. Distribute skills and experience levels evenly so that every team has a realistic chance of producing strong solutions.
Without pre-established criteria, the review session devolves into subjective preference debates. Define clear evaluation dimensions such as usability, feasibility, innovation, and brand alignment before teams begin designing.
Simply picking one team's design as the winner wastes the method's potential. The real value comes from thoughtfully combining the strongest elements from multiple solutions into a unified design that is better than any individual submission.
Assuming that the merged design is automatically better because it combines multiple approaches is risky. Always test the unified solution with real users to ensure that the combined elements work together coherently.
Comprehensive document outlining goals, requirements, and constraints for teams.
Clear designation of team members, roles, and responsibilities per group.
Independent design solutions developed separately by each team.
Meeting notes from cross-team presentations, critiques, and discussions.
Integrated solution incorporating the best elements from each team.
Structured approach for testing the combined design with real users.
Summary of user feedback, pain points, and suggested improvements.
Revised design based on testing results and team feedback.
Comprehensive document detailing the final solution and design rationale.