Design operations — often shortened to DesignOps — is the practice of running design like an operation: the people, process, tooling and rituals that let a team ship high-quality design consistently, at speed, as it scales. It’s the difference between a team that has talented designers and a team that reliably produces good design.
Here’s the part most teams miss: when design quality slips, the cause is rarely a shortage of talent. It’s a shortage of operations — no clear process, no shared system, no project management, no protected time to do the work properly. Great designers in a broken system produce mediocre outcomes. Fix the operation and the same people produce visibly better work.
What is design operations (DesignOps)?
Design operations is everything around the design work that decides whether it ships well. If design is the what, DesignOps is the how — and the how governs quality far more than most leaders expect. In practice it covers:
- Process & project management — how work is scoped, sequenced, reviewed and shipped without stalling
- A design system — one source of truth for components and patterns, so quality is built in rather than re-negotiated every screen
- Feedback loops — short, structured critique and stakeholder review instead of ad-hoc opinions arriving too late to matter
- Tooling & handover — files engineering can actually build from, and a clean path from design to code
- People & priorities — who owns the quality bar, and how design time is protected from constant reprioritisation
Why does design quality break down?
Because talent is necessary but not sufficient. A capable designer will still produce inconsistent work if the conditions are wrong — competing priorities, nothing to reuse, vague briefs, reviews that land too late to change anything. Multiply that across a growing team and drift is inevitable: two designers solve the same problem three different ways, and the product slowly loses its coherence. This is an operations failure, not a hiring failure — which is exactly why hiring more designers rarely fixes it.
Why in-house design teams struggle
In-house teams have continuity and deep product context, which is a genuine advantage. They tend to break down for a handful of recurring reasons:
- No design leadership — nobody owns the quality bar, so it drifts with whoever is loudest in the room
- Reactive, ticket-driven work — design becomes a service desk answering requests, never getting ahead of the roadmap
- No system — every screen is drawn from scratch, so consistency and speed both suffer
- Competing priorities — designers spread across too many products, with no protected time to do any of them well
The result is a talented team shipping busy, inconsistent work — and leaders who conclude, wrongly, that the answer is to hire more designers.
Why agencies deliver inconsistent design
Agencies can move fast and bring an outside perspective, but the traditional model carries its own failure modes:
- Vendor incentives — paid to deliver a project, not to own an outcome, so the work stops at handover
- Bait-and-switch staffing — senior people win the pitch, junior people do the work
- Handover gaps — design lands as a static file with no context, and quality erodes the moment it meets engineering
- No continuity — each project starts cold, without the system or product knowledge that lets design compound over time
It’s worth naming the obvious: Biotik is a studio, so this is a critique of a model we deliberately don’t run. Most agencies operate as vendors. The alternative is to operate as an embedded partner — the operational rigour of an internal team with the seniority and outside view of a studio.
What good design operations looks like
Good DesignOps is mostly invisible — you notice it only in the outcomes: design ships on time, stays consistent, and gets better as the team grows. Concretely, it looks like:
- Senior people doing the work, not just selling it — fewer handoffs, fewer decisions deferred
- One design system as the source of truth, so quality is the default and speed comes with it
- Real project management — clear scope, sequencing and review points, so work moves without thrash
- Tight feedback loops — short, structured critique that catches problems while they’re still cheap to fix
- One team, end to end — from strategy through to build-ready files, with no gap where quality leaks out
How Biotik approaches design operations
Biotik is a product and design studio in London and Tallinn, working with startups and scale-ups across the UK, the Baltics and the rest of Europe. Since 2019 we’ve run engagements the way design operations prescribes — because it’s the only way we’ve found to hold quality high as the work scales.
In practice that means one senior team from strategy to handover, with no juniors doing the real work; a design system at the centre so the product stays coherent; project management built in rather than bolted on; and short feedback loops so decisions hold up under pressure. We work either as a fixed-scope product design engagement — typically six to ten weeks — or embedded by the month as a long-term partner. Either way you get the operational rigour of an in-house team without having to build and manage one. If you already have a team and want to see where the operation is leaking, a structured audit is the fastest way to find out.
Frequently asked questions
What is design operations (DesignOps)?
Design operations, or DesignOps, is the practice of running design like an operation — the people, process, tooling and rituals that let a team ship high-quality design consistently and at speed as it scales. It covers workflow, project management, design systems, feedback loops, hiring and how design connects to product and engineering.
Do you need a dedicated design operations role?
Not necessarily. Small teams need the practice, not the job title. What matters is that someone owns process, priorities and quality — a clear feedback loop, a shared design system and real project management. A dedicated DesignOps hire only makes sense once a design team is large enough that coordination becomes a full-time problem.
In-house design team or agency — which produces better design?
Neither wins by default. In-house teams struggle when they lack design leadership, a system and protected time; agencies struggle when they operate as vendors with junior staff and handoff gaps. The best outcomes come from a senior, embedded partner that brings the operational rigour of an internal team without the overheads — one team, one system, tight loops.
How is DesignOps different from project management?
Project management keeps a single project on time and on scope. Design operations is broader: it also owns the design system, the quality bar, tooling, rituals and how design decisions are made and reused across projects. Good project management is one part of design operations, not the whole of it.
More from the journal
- In-House Design Team vs Agency: The Real Trade-Offs
- Why Hiring More Designers Won’t Fix Design Quality
- The Hidden Cost of Design Without Project Management
- The Design Maturity Model: 5 Stages and How to Level Up
- How to Structure a Design Team as You Scale
- How to Hire a Design Lead
- Design QA: Shipping What You Actually Designed