Refract
Field notes
Studio4 min read

The case for embedded design

Agencies hand off. Embedded teams stay in the room. For companies moving fast, the difference shows up everywhere.

Author

JDJane DoeFounder, Refract
The case for embedded design

Key takeaways

  • The agency handoff model breaks down when the problem is still moving.
  • A design team's most valuable asset is context, and context evaporates on handoff.
  • Embedded design ends with the team keeping the speed and quality you built together.

The traditional agency model is built around the handoff. You brief, they disappear, they return with a deck. It works when the problem is well-defined and stable. It works much less well when the problem is still moving — which, for most growing companies, it always is.

Context is the asset

The most valuable thing a design team accumulates isn't files — it's context. Why a decision was made, what was tried and dropped, where the edges are. Hand off and that context evaporates. Embed and it compounds.

  • Fewer briefs, more conversations.
  • Decisions made with the team, not for it.
  • A system the company can run without us.

Embedded doesn't mean forever. The best version of this work ends with us leaving — and the team keeping every bit of the speed and quality we built together. That's the outcome we're actually selling.

Frequently asked questions

What is embedded design?
Embedded design is a model where a design team works inside a company's day-to-day — in its conversations and decisions — rather than taking a brief, disappearing, and returning with a finished deliverable. It keeps design context with the team as the problem evolves.
How is embedded design different from an agency?
A traditional agency is built around the handoff: brief in, deliverable out. Embedded design stays in the room, accumulating context and making decisions with the team. It suits fast-moving companies whose problems are still changing.

Written by

JDJane DoeFounder, Refract

Other articles