Adapt every stage of design thinking for remote and hybrid teams. Practical techniques for async empathy research, virtual workshops, remote prototyping, and distributed user testing.
Design thinking was developed in an era of physical co-location. Sticky notes on whiteboards. Shoulder-to-shoulder sketching sessions. In-person user interviews with real handshakes and body language. The methodology's emphasis on collaboration, empathy, and rapid iteration was built around the assumption that everyone is in the same room.
That assumption no longer holds for most teams. Whether fully remote, hybrid, or distributed across time zones, modern product teams need to adapt design thinking for a world where "the room" is a video call, the whiteboard is a digital canvas, and your closest collaborator might be 12 hours away. The good news is that every stage of design thinking can work remotely. It just requires deliberate adaptation rather than trying to replicate in-person rituals through a screen.
The risk with remote design thinking is not that it becomes impossible; it is that it becomes shallow. Video calls create "Zoom fatigue" that limits how long people can engage creatively. Chat and email strip out the nonverbal cues that make empathy research rich. Async communication introduces delays that can kill creative momentum. The techniques in this guide address each of these challenges specifically.
The most important mindset shift is accepting that remote design thinking is not a degraded version of in-person design thinking. It is a different mode with its own strengths. Remote work enables async deep thinking that is impossible in a noisy workshop room. It allows you to include participants from different geographies who bring diverse perspectives. It creates a written record of ideas and decisions that physical sticky notes do not. Embrace these strengths instead of mourning the loss of the whiteboard.
The Initialize stage translates well to remote work because it is primarily about alignment and documentation, both of which benefit from written artifacts that remote teams naturally produce.
Create a shared project brief document that every team member can access and comment on asynchronously. Include the problem statement, target users, constraints, success criteria, and project timeline. Use a structured template rather than a free-form document; templates ensure nothing important is omitted and make it easy for people in different time zones to contribute at their own pace.
Hold a single synchronous kickoff meeting (60 to 90 minutes maximum) to discuss the brief, answer questions, and build initial team rapport. Record this meeting for anyone who cannot attend live. After the meeting, allow 24 to 48 hours for async comments and questions before finalizing the project brief.
Remote empathy research requires rethinking how you observe and connect with users. You cannot follow someone through their workday or sit beside them as they use a product. But remote research has its own advantages: participants are in their natural environment rather than a sterile lab, you can easily include participants from diverse geographic and cultural backgrounds, and recording interviews for later review is trivial.
Video calls work well for user interviews, with a few adjustments. Ask participants to share their screen when demonstrating how they currently solve the problem you are investigating. The screen share gives you observational data that partly compensates for the lack of physical observation. Pay attention to their file organization, browser tabs, sticky notes on their monitor, and any workarounds they have developed.
For participants who are uncomfortable with video, offer audio-only interviews. Some people share more openly when they are not being watched. Diary studies, where participants record their experiences over days or weeks using a simple form or app, are another excellent remote research method that captures in-context data without requiring real-time observation.
Use a digital whiteboard tool (Miro, FigJam, or Lucidspark) to build empathy maps collaboratively. Have each team member add observations from their research independently (async, over 1 to 2 days), then hold a synchronous session to discuss patterns, resolve contradictions, and synthesize findings. The async-first approach ensures that everyone's observations are captured before group discussion introduces anchoring bias.
The Define stage involves synthesizing research into problem statements and How Might We questions. This synthesis work is inherently collaborative and requires rich discussion. In remote settings, break it into two phases.
Phase one (async, 2 to 3 days): Each team member independently reviews the research artifacts and proposes candidate problem statements and HMW questions in a shared document. Everyone can see and comment on each other's proposals.
Phase two (synchronous, 90 minutes): The team meets to discuss the candidate statements, debate framings, and converge on 2 to 3 final HMW questions. This is one of the few stages where synchronous discussion is essential, because problem framing requires the kind of nuanced back-and-forth that async communication handles poorly.
Use digital affinity diagrams to cluster observations before the synchronous session. Having pre-organized research reduces the cognitive load during the live meeting and allows more time for the creative work of reframing.
Remote ideation is where the biggest adaptation is needed. In-person ideation draws energy from the room: people feeding off each other's enthusiasm, building on ideas in real time, sketching on the same whiteboard simultaneously. Replicating this energy through a screen is difficult. Instead of trying, lean into async ideation techniques that play to remote work's strengths.
Brainwriting is arguably the best ideation technique for remote teams. Create a shared document or digital whiteboard with one section per participant. Set a 24-hour window for everyone to add their ideas independently. Then open a second 24-hour window where everyone reviews others' ideas and adds building-on-ideas or new ideas inspired by what they read. This two-round async approach produces more ideas than a single synchronous session and gives people in all time zones equal participation.
When you do need real-time energy, use short, focused sessions (45 minutes maximum) with structured techniques. Crazy 8s works well remotely: everyone sketches on paper simultaneously while on a video call, then photographs or scans their sketches and uploads them to a shared board. The time pressure and parallel work prevent the "one person talks while everyone else zones out" dynamic that plagues remote brainstorming.
Dot voting translates directly to digital tools. Most digital whiteboard platforms have built-in voting features. Set a voting window (4 to 8 hours) so that everyone votes independently without being influenced by seeing others' votes accumulate. Reveal results in a brief synchronous session where the team discusses the top-voted ideas and decides which to prototype.
Remote prototyping is arguably easier than in-person prototyping. Digital prototyping tools (Figma, Framer, even presentation software) are inherently collaborative and do not require physical proximity. Multiple team members can work on different screens or flows simultaneously, with real-time visibility into each other's progress.
For lower-fidelity prototypes, use shared presentation slides or document files. Each slide represents a screen or state. Add clickable hotspots if using tools that support them. This approach is fast, requires no design tool expertise, and produces something testable within hours.
The key discipline for remote prototyping is maintaining a single source of truth. When the prototype lives in a shared tool, everyone always sees the latest version. Avoid the trap of "I'll work on my version locally and share it later," which creates merge conflicts and version confusion.
Remote user testing has become standard practice even for co-located teams. Video call testing with screen sharing provides nearly all the observational data of in-person testing, with the added benefit of testing in the participant's natural environment.
Share the prototype link with the participant. Ask them to share their screen (not the other way around; you want to see their cursor movements and hesitations). Give tasks, not instructions: "Find the pricing page" rather than "Click on the Pricing link in the navigation." Record the session (with consent) for the team to review later.
Have a designated note-taker on the call who is not the moderator. The moderator focuses entirely on the participant; the note-taker captures observations, timestamps of interesting moments, and direct quotes. After the session, both compare notes to ensure nothing was missed.
For broader reach, use unmoderated testing where participants complete tasks on their own while their screen and voice are recorded. This approach lets you test with more participants across more time zones without scheduling overhead. The tradeoff is that you cannot ask follow-up questions in the moment, so your task descriptions need to be very clear.
The specific tool matters less than using it consistently. Pick one digital whiteboard (Miro, FigJam, Lucidspark), one communication platform (Slack, Teams), one prototyping tool (Figma, Framer), and one video platform (Zoom, Google Meet). Resist the temptation to try every new tool; context-switching between platforms is the enemy of remote collaboration.
Create templates for every recurring activity: empathy maps, affinity diagrams, Crazy 8s boards, dot voting canvases. Templates reduce setup time and ensure consistency across sessions. Most digital whiteboard tools let you save and share templates within your organization.
Remote workshops cannot run as long as in-person ones. A full-day in-person workshop might produce eight hours of productive work. The remote equivalent should be spread across two or three shorter sessions (90 to 120 minutes each) with async work in between. People need time away from screens to think, and the async work between sessions often produces better ideas than the live sessions themselves.
Start every synchronous session with a brief warm-up exercise that does not relate to the project. Two minutes of informal conversation or a quick creative exercise builds the interpersonal connection that in-person teams take for granted. Without these moments, remote collaboration feels transactional and people disengage.
Hybrid teams face a unique challenge: the people in the room have a natural advantage in energy, visibility, and influence. They can read each other's body language, sketch on the same whiteboard, and have sidebar conversations during breaks. Remote participants are at a structural disadvantage.
The best practice for hybrid design thinking sessions is the "remote-first" rule: even if some people are in the same room, everyone joins the video call from their own device and uses the digital whiteboard instead of a physical one. This levels the playing field by ensuring that the primary collaboration medium is the one everyone has equal access to.
This can feel awkward for the in-room participants. They are sitting next to each other but typing into a screen instead of talking across the table. The awkwardness is worth it. The alternative, where in-room participants dominate the conversation and remote participants become passive observers, produces worse outcomes and erodes trust over time.
The single biggest advantage of remote design thinking is documentation. Every async contribution is automatically captured. Every digital whiteboard is permanently saved. Every video call can be recorded and transcribed. In-person teams lose enormous amounts of knowledge when sticky notes fall off the wall, whiteboard photos are blurry, and nobody remembers what was decided in which session.
Leverage this advantage deliberately. Create a project wiki or shared drive that collects all artifacts in chronological order: research notes, empathy maps, problem statements, ideation results, prototype links, test recordings, and decision logs. This archive becomes invaluable for onboarding new team members, briefing stakeholders, and revisiting earlier thinking in future iterations.
Related guides: collaborative design · design thinking workshop · facilitating design thinking
Design Thinker Labs Home · All Guides · How It Works · Pricing