How you structure a design team should follow your stage, not a big-company org chart. A startup runs one or two generalists close to the founders; a scale-up moves to a design lead with specialists and someone owning the system; a larger org federates squads with a design-ops function keeping standards consistent. Copy a model that’s too big too early and you add overhead; stay too lean too long and quality fragments.
Getting the shape right is one of the highest-leverage decisions in a growing design operation — it determines whether adding people raises quality or just raises coordination cost.
Structure follows stage
There’s no universal design org — there’s the right one for where you are. Three broad stages:
- Startup (1–3 designers) — generalist product designers working directly with founders and engineers. Speed and range matter more than specialisation.
- Scale-up (4–15) — a design lead appears, specialists emerge (product, brand, research), and someone starts owning the design system. This is where structure starts to matter.
- Larger org (15+) — multiple squads, a head of design, and a design-ops function keeping craft consistent across teams that no longer sit together.
What roles does a design team need?
Roles specialise as volume justifies it — you don’t hire all of these at once:
- Product designers — the core; UX and UI for features end to end
- UX research — validates decisions with real users; often shared before it’s dedicated
- UI / visual & brand — craft and consistency of the interface and identity
- Content design — the words in the product; frequently the last specialist hired
- Design system / ops — owns the design system and the workflow so the rest can move fast
- Design lead / head of design — sets direction, protects quality, manages the people
Centralised, embedded or hybrid?
Three operating models, each with a trade-off. Centralised keeps craft consistent but can feel distant from product squads. Embedded puts designers inside teams for speed but risks fragmenting quality as each squad drifts. Hybrid — designers embedded in squads, with a central design lead and a shared system holding the standard — gives most scale-ups the best of both. The right answer depends on how many squads you run and how mature your design system is; the more squads and the weaker the system, the more central coordination you need.
What’s the right designer-to-developer ratio?
A common benchmark is roughly one designer to every six to ten engineers, but ratio matters far less than throughput. The real question: can design stay ahead of build and still QA what ships? If designers are permanently behind, you’re either under-resourced or under-organised — and more often than founders expect, the fix is better operations, not more headcount. A well-run team of four can out-ship a chaotic team of eight.
Reporting lines and where design sits
Where design reports shapes how much influence it has. Design reporting into engineering or product often ends up serving delivery rather than users; a design function with a direct line to leadership keeps quality a first-class concern. As you scale, give design its own leadership seat — not to build a silo, but so craft has an advocate in the room where roadmap and resourcing get decided.
How Biotik helps
Not every team is ready to hire a full design function — and not every stage needs one. Working across London, Tallinn and the rest of Europe, Biotik plugs in as an embedded design team or as the senior layer that sets up structure, system and process, so the team you do build starts on solid operations rather than inheriting chaos. Sometimes that means designing your first two roles; sometimes it means running design until the in-house team is ready to take it over.
Frequently asked questions
How should you structure a design team?
Structure follows stage. A startup runs one or two generalists close to the founders; a scale-up moves to a centralised or embedded model with a design lead, specialists (product, brand, research) and someone owning the design system; a larger org federates squads with a design-ops function keeping standards consistent. Match the model to your size — don’t copy a big-company org chart early.
What roles does a design team need?
Early on, product designers who can do UX, UI and a bit of research. As you scale, the roles specialise: product design, UX research, UI/visual and brand, content design, and design-system/ops ownership — coordinated by a design lead or head of design. You don’t hire all of these at once; you add them as the work volume justifies it.
What is the right designer-to-developer ratio?
A common benchmark is around one designer to every six to ten engineers, but ratio matters less than throughput. If designers can’t keep design ahead of build and still QA what ships, you’re under-resourced or under-organised — often the fix is better operations, not just more headcount.
Centralised, embedded or hybrid design team?
Centralised keeps craft consistent but can feel distant from product squads; embedded puts designers inside teams for speed but risks fragmenting quality; hybrid — designers embedded in squads with a central design lead and shared system — gives most scale-ups the best of both. The right answer depends on how many squads you run and how mature your design system is.