Builders & Flows

DesignOps operating rhythm

Public

The operational layer for a large design org: intake, capacity, rituals, measurement.

Shun Leeby Shun LeePublished 25 Jul 2026, 02:03 · 18 views
0.0s / 0.0s

How this workflow works

Intake

AirtableRequest triage

Every incoming design request lands in one queue and gets triaged against team capacity before it's promised to anyone.

Plan

AirtableCapacity planning

Who's staffed on what, updated weekly, so a new request gets a realistic timeline instead of an optimistic guess.

Run

FigJamOrg-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

AmplitudeDesign 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

SlackOps 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. The author gets notified here.

No questions yet.