Remote Design Sprints Workshop
summary
Claims that remote sprints work if process and empathy are set up and that the physical team room can be recreated digitally with Miro sticky capture and templates. Workflow uses Notion and Figma alongside Miro, staggers designers about two-to-three week design sprints roughly two weeks ahead of dev, converts photos of analog stickies into board items, runs timed activities (icebreakers, dot voting, retros) and periodic check-in energy matrix sessions. Multiple teams run parallel tracks (up to ~18 people) and report usable artifacts and smoother handoffs.
AI-written summary · about
chapters (14)
- 0:00Remote design sprints intro
- 7:28Process and empathy in remote collab
- 10:36Tools for remote sprints
- 13:22Digital team norms with Miro
- 14:25Miro intro and workshop overview
- 19:00Facilitating sprints with Miro tools
- 23:14Reading team energy remotely
- 28:28Engagement activities
- 31:59Remote brainstorming and engagement
- 33:03Team size and scope for sprints
- 36:15Including UX researchers
- 37:38Onboarding new members
- 39:22Feedback and retrospective
- 40:45Closing remarks
related talks
27mCollaborative, Remote, Design Working-Sessions
47mBuild Agility with Design Sprints
25mHow to run a design sprint without a panic attack
01h 29mSolving real-world problems with a (mini) Design Sprint
37mGet ready for the storm - Remote Event storming in action
22mInside Figma: Product design snippets
27mRunning a Design Sprint on Android
44mFaster from Problem to Prototype with Design Sprints: Are MvPs Dead?