Engineering
How to write a handoff file engineers love
What goes into our handoff files, what we leave out and why fewer notes often work better.
Written by
Jonas Weber
What goes into our handoff files, what we leave out and why fewer notes often work better.
What we include
Every screen state: empty, loading, error and success
Components linked to the design system
Short notes only where behaviour isn’t obvious
What we leave out
We don’t annotate spacing or colours by hand. If the design uses the system, engineers can inspect it directly in Figma.
Review together
Before every handoff, we walk through the file with the engineer who will build it. Thirty minutes of questions saves days of back and forth later.
More articles
Research
What we learned from 400 customer interviews
The interview questions that work, the ones that don’t, and how we turn answers into design decisions.
Process
Our discovery playbook for week one
How we spend the first five days of every project, and what you get at the end of the week.
Design systems
Design systems small teams can maintain
Most design systems fall apart when the person who built them leaves. Here is how we set ours up to last.
Two project slots open for January
Book a 30-minute call. You’ll get a scope and a fixed monthly price within two days.
Use this free template ↗