Stitch Fix accelerates design sprints by collaborating in Figma | Figma Blog (opens in new tab)
Stitch Fix uses Figma to make design sprints faster, more collaborative, and easier to manage across departments. Its browser-based workflow gives everyone access to one shared source of truth, eliminating file handoffs and tool-installation delays. Real-time collaboration and reusable components let the team focus on solving UX problems instead of managing files or repeating production work. ## Sprinting in the Cloud - Stitch Fix brings designers, engineers, marketers, and project managers together to brainstorm, whiteboard, and prototype solutions. - Because Figma runs in the browser, participants can join shared files through a URL, regardless of whether they use Macs or PCs. - The team avoids exchanging files and installing separate applications for design, prototyping, and developer handoff. - Head of Product Design Ellen Beldner describes Figma as a replacement for the combined workflow of Sketch, InVision, and Zeplin. - A shared cloud file creates a single source of truth from the beginning of the sprint. ## Brainstorming and Critiquing in Tandem - Design sprints often reveal technical challenges or unexpected effects elsewhere in the user experience. - Figma’s Multiplayer feature allows team members to inspect and edit the same design simultaneously. - Instead of gathering around one computer or emailing exported files, teammates can review specific areas directly in the shared file. - Ellen can leave comments, provide immediate feedback, or draw mockups to explain suggested changes. - Designers can return to the same URL later to review detailed critiques without scheduling additional walkthrough meetings. - Working in one file prevents conflicting versions and helps the team stay aligned as prototypes become higher fidelity. ## Shared Components Reduce Busywork - Tight sprint schedules leave little time for repeatedly recreating common UI elements. - Figma’s shared components provide reusable instances of interface elements. - When the master component changes, all instances update automatically. - During a card-based design-system sprint, Stitch Fix used components to test different card combinations efficiently. - Team members could continue placing component instances while others worked on navigation and related areas. - This automation freed designers to focus on broader UX questions rather than repetitive production tasks. ## Practical Conclusion Stitch Fix’s experience suggests that browser-based collaboration, real-time feedback, and reusable components can significantly streamline design sprints. Teams seeking faster cross-functional iteration should prioritize a shared design environment that reduces tool friction and keeps everyone working from the same source.