| Google Docs Use to align UX and PM around the problem and requirements, before you start solutioning or designing. Can be used for copy-only work, especially exploring many versions of a message, that doesn’t involve visual or interaction design. |
| Miro Use when kicking off projects with colleagues inside and outside of design. Gets everyone working together on a focused project in the same space. Good for brainstorming, workshopping, organizing ideas visually, and diagramming. Can be slow to load for large amounts of visual content. FigJam can also be used in place of Miro. |
| Google Slides Use for stakeholder review (ex: PM, legal) of before/after UI and rationale for recommendations. Good for capturing screenshots, copy-only requests not involving complex flows, and historical context. Good for pointing non-design colleagues to specific pieces of an experience. Should not be source of truth for final visual and interaction design. |
| Figma Use for low and high-fidelity mockups, end-to-end flows, interactive prototypes, accessibility and localization reviews, detailed specs for ENG hand-off, and final source of truth for design and copy. Can be overwhelming for new users without guidance. Link to specific frames when possible. |