Skip to main content
Design ·

The designer to developer handoff

A production checklist for UI designers

Rob Sloan's portrait
Rob Sloan
Technical-drawing illustration of two workers in hard hats passing a geometric icosahedron across a gap, labelled transfer axis and alignment tolerance

Oh, the sting of disappointment when hours of painstaking design efforts are returned with a lackluster end product. The design system disregarded. The nuances lost. The pain is common, in fact, a study by Anima uncovered this issue to be the biggest frustration for UX/UI designers. 

In this situation, it’s easy to get ugly. Your craft feels disrespected. Dashed is your hope of creating something great for the user. Blame, resentment, and bitterness follow. You either resign to apathy or dig in your heels for the bout ahead. My advice? Do whatever you can to avoid this situation in the first place. 

At Ample, we rarely experience this drop off in work quality from design to development. That isn’t (just) because we’ve an outstanding core group of designers and developers. It’s because we were able to identify the underlying issue: every designer on our team needs to deliver UI assets in the same way. To address that inefficiency, we created a production checklist so that all our deliverables were more consistent – alleviating guesswork, Slack messages and project management time. 

We thought sharing this might help bridge the gap between designers and engineers (making our digital world a little brighter). So here it is…

Ample's Designer/Developer Handoffs Checklist (PDF)

There are tons of caveats here. Everyone’s team makeup is different. The work is different. The processes. On and on. I get it. Is this an exhaustive, one-size-fits-all, the-checklist-to-rule-all-checklists? Heck no. Consider it a step in the right direction. Or better yet, a start of a conversation. 

Rob’s pro tips:

  1. Review the guide we use for designer-to-programmer handoffs.

  2. Copy it into a place where you can eventually share it like Google Docs, Dropbox Paper, a Slack post or your project management tool of choice.

  3. Customize the list to fit your work, team or project.

  4. Share it with your development team to get their feedback.

  5. Make an instance of the checklist every time you handoff design work.

  6. Repeat steps 3-5.

One of our engineers signs off each email signature with, “an ounce of prevention is worth a ton of code.” The truth of that statement sticks. I believe developers want the same outcome as designers do – excellence. By digging in the corners during production (aka the least sexy part of the job) designers can extend their ownership of the process and ensure a smooth handoff each and every time. Then, instead of focusing on what’s wrong when you see the end product, you can collaborate with your development team to polish the details. 

Great teams make products better as they go. Hopefully this guide will help you get a little better.  

Frequently asked questions

What should a design-to-developer handoff include?

A design-to-developer handoff should include a complete production checklist of UI assets: finalized designs with all states accounted for, specs and measurements, and everything a developer needs to build the UI without guesswork. At Ample, we use a shared designer/developer handoffs checklist so every designer delivers UI assets the same way — which cuts down on Slack messages, project management time, and quality drop-off between design and build.

Why do designs lose quality during development handoff?

Usually because the designer and developer never agreed on how UI assets get delivered. An Anima study found this drop-off in work quality from design to development is the biggest frustration for UX/UI designers. We found the underlying issue wasn’t talent — it was inconsistency. When every designer on the team delivers assets the same way, the nuances and the design system survive the handoff.

How do I create a design handoff checklist for my team?

Start with a proven guide (like ours), copy it into a place you can share — Google Docs, Dropbox Paper, a Slack post, or your project management tool — then customize it to fit your work, team, and project. Share it with your development team to get their feedback, make an instance of the checklist every time you hand off design work, and repeat.

Is one design handoff checklist enough for every project?

No. Team makeup, the work, and the processes all differ — this isn’t an exhaustive, one-size-fits-all, the-checklist-to-rule-all-checklists. Treat it as a step in the right direction and customize it per project. A checklist that’s iterated with your developers beats a perfect one nobody uses.

Who’s responsible for a smooth design-to-dev handoff?

The designer can drive it. By digging in the corners during production — the least sexy part of the job — designers extend their ownership of the process and prevent the disappointment of seeing their design system disregarded in the end product. Developers want the same outcome designers do: excellence. An ounce of prevention is worth a ton of code.

What should I do after handing off design work to developers?

Stay collaborative instead of critical. If you’ve done the production work up front, the handoff conversation shifts from “what’s wrong with the end product” to polishing details together. Great teams make products better as they go.


Stay in the know

Sign up for our email newsletter. Nothing spammy about it — just a monthly rundown of what we're sharing.