What it is
The practice of preparing and transferring designs to engineering with the specifications, assets, states, and behavior needed to build them faithfully.
When to use it
Late Prototype into Implement, whenever design moves into development.
Why (value)
Reduces back-and-forth and implementation drift by making design intent, states, and behavior explicit before build.
How to run it
- Finalize designs including all states and edge cases.
- Specify spacing, type, color, and behavior.
- Export assets and tokens engineering needs.
- Walk through the handoff with developers.
- Stay available for questions during build.
Inputs and outputs
- Inputs: Final designs, states, tokens, and behavior rules.
- Outputs: Specs, assets, and a shared understanding with engineering.
Time and effort
Medium. Depends on complexity and number of states.
Evidence and limitations
Handoff artifacts are expert-review specifications of intent, not evidence the design is right; they ensure faithful building, not a good outcome. See Evidence and limitations.
Tips and pitfalls
- Specify all states, not just the default.
- Prefer tokens and components over pixel redlines.
- Treat handoff as a conversation, not a wall toss.
Variations
Tool-based inspection handoff, redline specs, and living component handoff.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- Design annotations — Add notes to designs that explain behavior, logic, and intent for accurate implementation.
- Design QA — Check the built product against the approved design to catch implementation drift before release.
- Design documentation — Record design decisions, rationale, and specifications so the knowledge outlives the project.
