Design Ops

Design Ops organises production and collaboration around design, Research Ops does the same for user research. Research Ops has its own infrastructure, from recruiting participants to recording permissions, through to a space where findings are centralised. In smaller organisations, the same person handles both. DevOps responds to the same drivers but leans towards tooling and automation, where Design Ops is mostly about processes.

The design system is the most visible piece of work in Design Ops, hence the frequent confusion. It is only one among others, and it goes out of date quickly without governance, for want of knowing who can propose a component and through which process it gets integrated. The relationship works the other way round: it is often by launching a design system that an organisation discovers its need for Design Ops.

There is no absolute threshold. The literature on the subject mentions around a dozen people, but the number is a poor indicator taken on its own. The real trigger comes down to dispersion. Three designers spread across a department, an external provider and a business unit, with no shared tool or shared ritual, produce more friction than eight people gathered in the same team. The signals to watch are not knowing what the others are working on, screens redone when they already existed, and the time designers spend somewhere other than designing.

Three models coexist. The function can be embedded in each product team, carried by a cross-team group that steps in as support, or set up as a dedicated entity in the same way as DevOps. At a smaller size, an experienced designer takes it on part time, and someone working half-time is worth more than a post created too early. When the role becomes a job in its own right, that of Design Ops manager, it sits between design and the technical teams and calls for knowing the design process as much as knowing how to manage a budget and a schedule.

It is a support function: without a clear mandate, it has no real means of action. It does not produce design either, and an approach that becomes an end in itself adds process where it was meant to remove friction. Standardising too early freezes practices that have not yet found their shape. Finally, a well-organised practice is not necessarily a high-quality one: Design Ops improves the conditions of design work, not the work itself.