What it is
Two people (two designers, or a designer and an engineer/PM/content specialist) working on the same design problem together in real time, echoing pair programming.
When to use it
During Ideate and Prototype, for complex problems, onboarding, or tight design-engineering collaboration.
Why (value)
Merges perspectives, catches issues early, spreads knowledge, and often produces better decisions than solo work.
How to run it
- Pick a problem and a partner with a complementary perspective.
- Work the problem together, one drives, one navigates.
- Swap roles regularly.
- Think aloud and challenge each other constructively.
- Capture decisions and rationale.
Inputs and outputs
- Inputs: A design problem and two collaborators.
- Outputs: A jointly developed design and shared understanding.
Time and effort
Low. Ongoing during the work.
Evidence and limitations
A collaboration practice, not evidence-producing. Outputs still need validation. See Evidence and limitations.
Tips and pitfalls
- Pair complementary skills for the biggest payoff.
- Swap driver/navigator roles to stay engaged.
- Keep it collaborative, not one person dictating.
Variations
Designer-designer, designer-engineer, designer-content pairing.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- Design critique — Gather peers to give structured, goal-focused feedback on work in progress.
- Design studio — A structured sketch-critique-iterate workshop that gets a cross-functional group designing together.
- Coded prototyping — Build a working front-end prototype in code to test real interactions and technical feasibility.
