Building the specialists in
Specialists leave. Their expertise shouldn't. Turning motion and content craft into system capability.
Design system teams are small by design. Mine is five people serving a 127-component estate across web and native app. Small teams accumulate craft gaps, and motion and content design were ours. The usual answers both fail: permanent specialist headcount is hard to justify on a platform team, and "everyone does a bit" produces guidance nobody trusts. So I used a different pattern, twice.
Motion
I made the case for a dedicated motion designer on a six-month fixed term, with the contract structured so the main deliverable wasn't a backlog of animations but the reasoning: a motion philosophy (efficient, intuitive, purposeful), energy-conscious guidance, and the full value set of behaviours, durations, easings, tokens and accessibility considerations, codified into the design system's public documentation before the contract ended. He left; the capability didn't.
Content
Here the pattern was structural. The content designer sits inside the design system team, adding principles and governance into the library from the start rather than reviewing other people's output afterwards. Her expertise became public system guardrails: a "content is the product" foundation, plain-language guidance targeting a low reading age, tone of voice, and content accessibility guidelines, connected to the component library and codebase.
The compounding payoff
Because motion and content existed as structured, documented rules rather than tribal knowledge, they became machine-readable: the foundation that let AI workflows apply our content standards with 100% accuracy where free-styling had managed 10%.
- craft specialisms turned into documented system capabilities
- 2
- AI content accuracy, built on the codified rules
- 10% → 100%
Outcome
Two craft gaps converted into publicly documented capabilities on a five-person team, without permanent specialist headcount, and a repeatable method: bring the specialist in, aim them at the system, and make the codification the deliverable.