Marcus Andrey Study
Ler em português Library

Framework · DesignOps & capacity · 3 min read

Definition of Done for design

A short shared checklist (states, edge cases, accessibility, annotations, design-system usage) that says when design work is ready for handoff, agreed with developers and QA.

1States

Every new screen has its default, loading, empty, error and success states.

"What if the list is empty?"
2Edge cases

Long text, many items, missing data and no permission are covered.

"What if the name is very long?"
3Accessibility

Contrast, focus order, keyboard use and labels are checked and annotated.

"Can I do this without a mouse?"
4Annotations

Behaviour, rules and validation are written next to the design.

"When does this button enable?"
5DS usage

Library components only. Any exception is flagged and explained.

"Is this a new component?"

Agreed with developers and QA · kept short · reviewed every 6 months

Five areas that design work must cover before it is ready for handoff.

Use it when

  • Developers keep coming back after handoff with "what happens when the list is empty?" or "what does the error look like?"
  • Handoff quality differs a lot between designers or domains.
  • You set up minimum viable DesignOps and need a process standard everyone can point to.

How to use it

  1. Collect what goes wrong after handoff. Ask developers and QA which questions and bugs come back most often. Look at recent tickets. Output: a short list of real handoff gaps.
  2. Draft a short checklist. Start from the five core areas: states, edge cases, accessibility, annotations and design-system usage. Add only items that answer a real gap. Output: a draft of about one screen, not a document.
  3. Agree it with developers and QA. Walk through it together and ask: "If all this is done, can you build and test it without coming back to us?" Change the wording until they say yes. Output: an agreed Definition of Done.
  4. Use it at handoff and in critique. The designer checks the list before handoff. Reviewers use it in design QA. Make "Done" mean the list is complete. Output: a checked list attached to each handoff.
  5. Review it every 6 months. Remove items nobody needs, add new gaps. Every item needs a reason; if nobody can say why it is there, retire it. Output: an updated list with a next review date.

Worked example

An internal operations platform with 6 product teams. Developers report that most questions after handoff are about empty tables, long text and keyboard use. The UX lead, two designers, the frontend lead and a QA engineer agree this list in one 45-minute session.

Area Done means
States Default, loading, empty, error and success are designed for every new screen.
Edge cases Long text, zero and many items, missing data and no permission are shown or annotated.
Accessibility Contrast checked, focus order annotated, keyboard use described, labels on all inputs.
Annotations Behaviour, rules and validation are written next to the design, with numbered markers.
Design-system usage Only library components; any detached or new component is flagged and explained.

After two months, questions after handoff drop noticeably. At the six-month review the team removes one item nobody used and adds "responsive behaviour at the smallest supported width".

Watch out for

  • A list nobody outside design agreed. If developers and QA weren't in the room, it is a design wish list, not a shared standard.
  • Too long to use. Every extra item makes the list easier to skip. Keep it to one screen.
  • "Done" as a gate for blame. Use the list to catch gaps early, not to prove who failed.
  • Never reviewed. Products and tools change. A list that is two years old checks the wrong things.

Template

Copy this into your UX wiki and agree it with developers and QA.

Definition of Done for design (domain/team: ________)
Agreed with: dev ______  QA ______     Next review: ______

[ ] States: default, loading, empty, error, success
[ ] Edge cases: long text, 0 / many items, missing data, no permission
[ ] Accessibility: contrast, focus order, keyboard, labels
[ ] Annotations: behaviour, rules, validation, numbered markers
[ ] Design-system usage: library components only, exceptions flagged
[ ] (team-specific item, with the reason it exists)
Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close