The default handoff is a link in a ticket. Designer marks "ready." Engineer opens the file alone. Two weeks later, someone says "that's not what I meant."
By then, change is expensive and blame is easy. That's not a tools failure. It's a ritual failure.
What broken handoff costs
Count it honestly for one sprint:
- PR comments fixing spacing that should have been settled in composition.
- Engineers rebuilding a pattern that exists in another squad's codebase.
- Design reviews happening after merge instead of before build.
- Slack pings asking "which button is canonical?"
Multiply by squads. That's your tax. On one product I worked on, aligning patterns cut reclamations ~90%. The UI wasn't prettier. It was consistent. Users stopped making the same mistake twice.
Five rituals that fix most of it
No new software required. Put these on calendars:
- Weekly design-eng sync (30 min). Drift, incoming patterns, blockers. Design lead + eng lead + system owner.
- Pair review before "ready for dev." Twenty minutes, same Figma file, same room (or call). Catch composition issues when they're cheap.
- Office hours twice weekly. Answer "which component?" once, update docs the same day.
- Design QA on system PRs. Shared components get a design pass: tokens, states, focus. Not pixel wars on feature branches.
- Monthly show-and-tell. One squad demos shipping with the system. Adoption is social, not mandated.
Start with 1 and 2 this week. Add the rest as your library grows.
When rituals need a person in the seam
Rituals still need someone who translates: constraints from engineering, intent from design, governance for both. That's design engineering. Someone who speaks both Figma and the repo and shows up in PRs, not only critiques.
Teams hire for feature velocity and wonder why the system rots. They need a seam-owner, even 20% of a role, or a fractional partner until the hire lands.
Try it for 30 days
Week 1: audit + weekly sync. Week 2: pair review + written "done" checklist. Week 3: one Button in Figma, code, and Storybook. Week 4: office hours + rough rework estimate for leadership.
If Slack questions drop and one squad ships on the system, you've proved ROI. Then scale.
Full playbook: Design × Development Collaboration ebook.