For intermediate product designers who want to structure Figma files, hand designs to developers, and record design decisions clearly. You will be able to set up a file system that teammates can follow without you explaining it.
6 lessons · 2 hr 48 min, plus 1 optional (5 min more with the optional lessons)
Start here: reusable file templates, status colours and file hygiene give you the foundation for the rest of the path.
A lead designer at an early-stage startup walks through his Figma workflow, covering file templates, colour-coded project status, file hygiene, design checklists, managing iterations and a mobile design template. The interview is aimed at working designers who want to ship quickly.
Builds on file hygiene by organising files for engineers, using Dev Mode handoff and planning empty states.
An interview with Hygraph's Head of Design, Darshan Gajara, who walks through a design project and shares advanced developer handoff techniques in Figma. It is aimed at product designers who already work in Figma and hand designs to engineers.
Adds a context page and project timeline, taking file structure toward stakeholder communication and critiques.
Jay interviews Tammy Taabassum, a product designer at Figma, about how she organises her Figma file, handles engineering handoff, and runs stakeholder collaboration and design critiques. It is part of a series looking inside designers' Figma files.
Covers handoff through Confluence and component specs, plus a good/better/best way to weigh options.
An interview with Jade, a senior product designer at Atlassian, about how she organises her Figma file and runs developer handoff. It covers using Confluence and Loom in design work, a good/better/best design framework, journey maps, component specs and design critique.
Shows the developer's view of what makes a file easy to implement and how to state design intent clearly.
A Config 2022 talk by Kazuya Seki, a former frontend developer, on how to build Figma design files that developers find easy to implement. The session covers making designs that are clear to the people who build them.
Closing example: one team file documenting decisions, leadership feedback and cross-functional reviews.
Staff product designer Nicole Weber walks through how the Firefox design team organizes its work in a single Figma file, covering project context, dev handoff, QA, wireframing, documenting decisions and critiques. It suits designers who already work in Figma and want to see a team's file structure in practice.
A short Dev Mode handoff checklist to apply after the longer talks; skip it if you already use Dev Mode.
A walkthrough of a design handoff checklist in Figma Dev Mode, covering marking designs Ready for dev, checking states and sizes, annotating and measuring, preparing assets, reading the Inspect tab, and verifying the build with design QA. It suits designers who already hand off work to developers in Figma.
For product people who want to know when to frame a problem and when to run a design sprint to decide and align a team. By the end you will be able to pick the right method and use it to reach a shared decision.
For intermediate designers who want to take a UI from layout grid to working code. You will plan interfaces, build interactive components, document them for developers and use AI to generate screens from a design system.
For designers who want to understand how product teams explore ideas, sketch quickly, iterate in the open and ship. You will follow real process stories from Figma, Slack and others to build a practical working method.
For intermediate designers who want developers to build their designs accurately. You will learn to structure Figma files, prepare designs for handoff, and work alongside engineers.