Design ops

For teams where design and engineering ship past each other. I build the bridge: shared tokens, working handoffs, and rituals that survive the next deadline.

SCOPE OF WORKFIG. 1

Token pipeline

Design decisions as code: from Figma variables into CI, drift caught early.

Handoff & workflows

Specs developers actually read; reviews that catch problems before release.

Tooling

Figma-to-code bridges, linting, scaffolds — the boring glue that saves weeks.

Process & rituals

Design reviews, contribution flows, naming that sticks after I leave.

TOLERANCES
ENGAGEMENT 2 weeks – ongoing
MODE remote-first
on-site IT / DE
LANGUAGES IT · DE · EN
COMPATIBILITY Figma · design tokens
your stack, your tools
PRICING fixed quote or monthly
agreed at intake, no surprises

PROCEDURE — FIG. 2

1

INTAKE

30-minute call, free. You state the problem.

2

OBSERVE

I watch how design ships today — where it stalls. Numbers, not impressions.

3

WIRE

Tokens, tooling, handoff — connected one piece at a time.

4

EMBED

Rituals documented and rehearsed. The team runs it without me.

START WITH THE INTAKE →

SHEET DS·SRV·03 · REV 01 · 2026–07