DesignOps operating rhythm
PublicThe operational layer for a large design org: intake, capacity, rituals, measurement.
How this workflow works
Intake
Airtable — Request triage
Every incoming design request lands in one queue and gets triaged against team capacity before it's promised to anyone.
Plan
Airtable — Capacity planning
Who's staffed on what, updated weekly, so a new request gets a realistic timeline instead of an optimistic guess.
Run
FigJam — Org-wide critique
A recurring cross-team critique session, open to any designer with work in progress — feedback from outside your own pod, on purpose.
Measure
Amplitude — Design health metrics
Cycle time, rework rate, review turnaround — the numbers that tell you whether the design org is actually getting faster, not just busier.
Manage
Slack — Ops comms
The weekly digest — what shipped, what's blocked, what changed in process — so nobody in a 40-person design org finds out by accident.
Questions
Ask about the reasoning, not just the tools. Answers stay attached to this workflow.
Sign in to ask a question.
No questions yet.