# Design Handoff

Design handoff is the collaborative transfer of product intent into implementation through shared context, inspectable specifications, decisions, and continuing review.

- Type: practice
- Domain: Experience & interface
- Level: Advanced
- Last reviewed: 2026-09-22
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/design-handoff/>)

## What it means

Design handoff makes a design ready to build by connecting visual and behavioral intent with requirements, components, content, assets, states, data assumptions, and acceptance criteria. It is best treated as an overlapping collaboration between design and engineering, not a meeting where finished files cross a departmental boundary.

## Why it matters

Implementation requires decisions that static screens cannot contain. Without shared context, engineers must guess at responsive behavior, failure states, content priority, component reuse, and accessibility. A disciplined handoff reduces preventable rework, exposes feasibility questions earlier, and helps the built product preserve the outcomes rather than merely imitate a frame.

## When to use it

Prepare handoff incrementally as work moves from exploration toward delivery. The depth should match novelty and risk: a known design-system component may need little explanation, while a new interaction, complex data state, or cross-platform flow needs joint walkthroughs and prototypes. Keep designers available during implementation.

## How it works

1. Align on the user outcome, scope, constraints, supported environments, and source of truth before detailing screens.
2. Map designs to shared components and tokens, and identify intentional departures or new component needs.
3. Specify responsive rules, content, data assumptions, states, transitions, assets, accessibility behavior, and acceptance criteria.
4. Walk through the work with engineers and testers, resolve questions in the shared record, and revise for technical discoveries.
5. Review working increments and verify consequential fixes before release instead of waiting for a final visual inspection.

## A practical example

For a new account-recovery journey, the designer links each screen to existing form components, documents rate-limit and identity-check states, supplies content for delayed messages, and describes focus movement after errors. An engineer flags an unavailable status from the identity service, so the team revises the flow before build and adds the scenario to acceptance criteria.

## Where it breaks

No artifact can eliminate implementation judgment or changing requirements. Tool-generated measurements may imply precision while omitting behavior, semantics, performance, and platform conventions. Heavy handoff packages quickly become stale. Teams need a clear source of truth and a lightweight way to record decisions made during construction.

## Common mistakes

- Delivering polished happy-path frames without data, error, loading, permission, and responsive states.
- Assuming inspectable dimensions communicate user intent or interaction behavior.
- Ending designer involvement at handoff and discovering interpretation gaps only before release.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/design-handoff/#visualization-design-handoff>)

## Sources

1. [The Designer's Handbook for Developer Handoff](<https://www.figma.com/blog/the-designers-handbook-for-developer-handoff/>) — Figma · Professional guidance
2. [Guide to Dev Mode](<https://help.figma.com/hc/en-us/articles/15023124644247-Guide-to-Dev-Mode>) — Figma Help Center · Product documentation
3. [Design to Code: Turning Handoffs Into High-fives](<https://m3.material.io/blog/designtocode>) — Material Design · Design-system guidance

## Related topics

- [Design Annotation](<https://wiki.soroush.uk/topic/design-annotation/>)
- [Design QA](<https://wiki.soroush.uk/topic/design-qa/>)
- [Acceptance Criteria](<https://wiki.soroush.uk/topic/acceptance-criteria/>)
