Teams call it a tooling problem. "Figma doesn't match production." "We need better specs." "Maybe AI will fix handoff."

Sometimes. More often, underneath the tooling complaint is a teamwork gap: two groups with different definitions of "done," no one holding the center, and Slack threads substituting for a system.

The seam is where money leaks

Designers optimize for intent and coherence. Engineers optimize for shipping and maintainability. Both are right. Without a bilingual connective role, the compromise happens in production at 11pm, in a PR nobody from design will ever see.

That's expensive in ways leadership rarely measures:

  • Rework when the "quick" UI doesn't match the spec anyone thought they agreed on.
  • Onboarding drag when "how we build UI here" lives in people's heads.
  • Support load when the same action looks different on two screens.
  • Morale when every sprint includes a design-vs-eng argument someone could have prevented Tuesday.

I've watched one consistency fix cut reclamations ~90% on a product. No hero redesign. Same component, same behavior, everywhere. Alignment, not magic. Collaboration infrastructure pays like operations, not like polish.

What actually fixes it

New platforms don't fix distrust. These do:

  • Rituals: weekly design-eng sync, pair review before handoff, office hours, design QA on system PRs.
  • A shared language: semantic tokens, governed components, a definition of "done" both sides sign.
  • A seam-owner: a design engineer who speaks Figma and the repo, translates constraints early, and protects adoption.

At Nord, with Aurora used by dozens of teams and millions of users, the hard part was never drawing buttons. It was keeping dozens of contributors building the same thing. Governance and rituals scaled what hallway trust couldn't.

Design engineers are teamwork infrastructure

A design engineer isn't "extra design" or "extra eng." They're the person who makes design intent survive handoff: validating composition in code, shipping Storybook examples engineers trust, and saying no to one-offs that compound.

Hiring that role is brutal because most filters force a binary: designer or engineer. Teams contract design engineering for the same reason they contract security or platform work: the skill is rare, the cost of not having it is spread across every squad.

ROI you can explain in a meeting

Don't pitch "better collaboration." Pitch rework avoided:

  • Hours per month rebuilding patterns that already exist somewhere else.
  • Extra days for new hires to ship a screen without tribal knowledge.
  • Tickets tied to confusing UI (like reclamations dropping ~90% when patterns align).

Make the tax visible. Then show the 30-day sprint: audit, one ritual, one component adopted by a real squad, numbers in week four.

It doesn't have to be this way. Most of this is sequencing and teamwork, not talent.

Go deeper

I wrote a full field guide: rituals, roles, conflict patterns, ROI worksheet, and a 30-day collaboration sprint. Download the ebook (PDF).