Small teams coordinate by accident. Three designers, one channel, one weekly review — everyone knows what everyone else is drawing, and the process lives in people's heads rather than anywhere you could point to.
The symptoms of outgrowing it are specific. Two squads ship two different date pickers in one quarter. The same research question gets asked three times because nobody can find the last study. A new designer spends six weeks lost in a file structure that made sense only to whoever built it.
Adding designers to a process nobody wrote down makes the problem bigger, not smaller. Somebody has to decide where work lives, stop two squads solving the same problem twice, and keep one experience coherent across web and mobile. What happened by accident at three people has to be built on purpose at fifteen.
DesignOps
DesignOps is the plumbing — tooling and licences, file structure, research recruitment, critique cadence, hiring, onboarding, handoff to engineering. Roughly what DevOps is to engineering: the work that makes the other work possible, and that nobody notices until it stops.
Judge any DesignOps proposal by one test: does it remove a cost designers are paying now? Name the cost in hours — the weekly scheduling tax, the lag between a design being ready and an engineer opening it.
The failure mode is process for its own sake: a new ritual, a new template, a new review gate, and not one hour handed back to anyone. The trigger for a dedicated DesignOps person is a symptom, not a headcount — nobody can say who owns the component library, and the job lands on whichever designer looks least busy. Until then it is a slice of someone's job, but a named job, not a hope.