The short answer
A design system team needs, at minimum, a designer and an engineer working as a pair, with one of them acting as lead. As the company grows it adds a dedicated lead or product manager, more engineers (including native iOS and Android), and shared specialists for accessibility, content and enablement, plus champions in every product team. Typical sizes: no dedicated people at a startup, 1–3 at a scale-up, 4–8 at a mid-sized company, and rarely more than 20–25 at an enterprise, where growth comes from contributors and automation instead.
- Aim for at least as much engineering capacity as design capacity. Adoption happens in code.
- Give the system one accountable leader, whichever department the team reports to.
- A dedicated team should spend about a third of its time with product teams, not only on its own backlog.
The roles a design system needs
In a small company one person wears several of these hats. In a large one, each is a separate job. What matters is that every responsibility below is somebody's, by name.
| Role | What they do day to day | Key skills | Needed from |
|---|---|---|---|
| Design system lead / product manager | Owns the roadmap and priorities, talks to leadership and product teams, measures value, removes blockers. Runs the system as a product. | Prioritisation, communication, enough design and engineering literacy to make trade-offs | Scale-up (often a part-time hat) |
| Design system designer | Foundations, component design, Figma libraries, usage guidance, design reviews, workshops. | Systems thinking, interaction design, accessibility, Figma, writing | Startup (part-time) |
| Design system engineer | Builds components and the token pipeline; testing, releases, code review of contributions. | Front-end architecture, accessibility in code, API design, testing | Startup (part-time) |
| Native engineers (iOS, Android) | Build and maintain native component libraries from the shared tokens. | Platform expertise and platform accessibility | When native apps exist |
| Accessibility specialist | Sets standards, reviews components, tests with assistive technology, trains others. | WCAG, screen readers, testing | Scale-up (shared) |
| Content designer | Voice, vocabulary, message patterns, documentation writing standards. | UX writing, information architecture | Mid-sized (part-time) |
| DesignOps / programme manager | Runs rituals, community, enablement, communication and metrics. | Operations, facilitation | Mid-sized |
| Developer advocate / enablement lead | Training, onboarding, office hours, migration support, sample code. | Teaching, engineering credibility | Enterprise |
| Champions (in product teams) | The system's voice in each team: early feedback, local help, contributions. Not a full-time role. | Credibility in their team, curiosity | Scale-up |
Hiring the designer, forgetting the engineer. A design system team without engineers produces a beautiful Figma library and very little real use. At every size, aim for at least as much engineering capacity as design capacity on the core team.
How many people, at what size?
| Company | Dedicated people | Model | Contributors |
|---|---|---|---|
| Startup (10–50 people) | 0 | Embedded: two owners with ~20% of their time | Everyone, informally |
| Scale-up (50–300) | 1–3 | Small central team, starting hybrid | A champion per squad |
| Mid-sized, distributed (300–2,000) | 4–8 | Hybrid, written-first | Regional champions plus protected contributor time |
| Fast-growing, many business units | 8–14 | Hybrid with business-unit extensions | Extension teams plus champions |
| Global enterprise | 15–25 | A family of systems with a central platform team | Federated contributors in every portfolio |
Org chart: the founding pair
For a scale-up, the smallest team that works is two people with a sponsor and a ring of champions. The designer usually doubles as the lead. The engineer often reports into engineering with a dotted line to design.
Org chart: a product team of six to eight
At a mid-sized company the system becomes a product with its own lead, design and engineering roughly balanced, and specialists shared with the wider organisation.
Org chart: a platform organisation of about twenty
At enterprise scale the team splits into squads, each with its own focus, held together by a central lead and an enablement squad. Beyond this size, growth comes from contributors and automation, not headcount.
Foundations & tokens
Web components
Native
Enablement & ops
At IBM, the Riyadh Air design system was run with six named roles across three companies: IBM, Riyadh Air and Publicis Sapient. See the roles and how they worked together. At CARS24, the internal tools system ran with one system designer, two engineering maintainers and a squad of eight engineers for the build. Read the case study.
Running the system with no dedicated team
Most companies start here, and many stay here for good reason. It's cheap, close to real product needs, and spreads knowledge widely. It also fades quietly unless you set it up deliberately:
Name two owners and protect their time
One designer and one engineer, each with about 20% of their time (a day a week) reserved in their team's plan and written into their goals. Unprotected time is no time.
Form a small guild
Interested designers and engineers from each team meet every two weeks for 45 minutes: review new UI, decide what goes into the system, share problems.
Keep a single backlog
One visible list of system work. Items are picked up by whichever team needs them first, built properly, and contributed back.
Rotate the support role
A weekly rotation for answering questions in the system channel, so the owners aren't the only point of contact.
Build the system inside product work
New components are built when a feature needs them, with a little extra time to make them reusable.
What a dedicated team should and shouldn't do
- Own a public roadmap, planned with product teams each quarter.
- Ship on a regular rhythm, with release notes written for users.
- Spend real time with product teams: pairing, pilots, office hours.
- Run a support rota so questions get fast answers.
- Review and merge contributions quickly.
- Measure adoption, satisfaction and value, and report them.
- Building in isolation, then "launching" to teams who weren't involved.
- Being the only people allowed to change anything.
- Measuring success by components shipped rather than value delivered.
- Saying yes to everything, or no to everything.
- Spending more time on internal process than with product teams.
Where should the team report?
Reporting lines sound like an HR detail, but they shape what the system becomes.
| Reports to | Tends to be good at | Watch out for |
|---|---|---|
| Design leadership | Visual quality, foundations, design adoption | Weak engineering investment; code lags behind Figma |
| Engineering / platform | Code quality, tooling, releases, technical adoption | Design quality and the Figma library neglected |
| Product | Prioritising by business value; roadmap discipline | Treated as a feature team and constantly reprioritised |
| Joint | Balance; shared accountability | Needs two leaders who genuinely agree, or decisions stall |
Our recommendation: one accountable leader for the system, and clear, equal standing for designers and engineers on the team, whichever organisation they formally sit in. A common arrangement is a team reporting into design with engineers holding a dotted line to engineering (or the reverse), plus a joint quarterly review with both leaders.
Who's responsible for what
| Activity | System lead | Designers | Engineers | Champions | Product teams |
|---|---|---|---|---|---|
| Roadmap and priorities | A | C | C | C | C |
| Foundations and tokens | C | A/R | R | I | I |
| Component design | I | A/R | C | C | C |
| Component code and API | I | C | A/R | C | C |
| Office hours and support | A | R | R | R | — |
| Contributions | I | R (review) | R (review) | R | A for their own |
| Adoption in a product | C | C | C | R | A |
Signs it's time to grow the team
- Requests wait more than a few weeks for a first response.
- The part-time owners are always too busy with product work.
- Teams are building local copies of system components.
- A second platform, brand or business unit is coming.
- Nobody has time to measure adoption or write release notes.
When it's time, make the move carefully. Hire from inside where you can (the part-time owners often make the best first dedicated members), turn the guild into a champions network, announce clearly what changes and what doesn't, and clear the oldest requests in the first quarter. Trust is earned by response time. For the cost side of that decision, see design system ROI.
The short version
- Start with a designer and an engineer as a pair; balance design and engineering at every size.
- Add a lead, native engineers and shared specialists as the company grows; champions in every team.
- Without a dedicated team: protected time, a guild, one backlog and a support rota.
- A dedicated team runs like an internal product company and spends a third of its time with product teams.
- One accountable leader, whatever the reporting line.
Frequently asked questions
How big should a design system team be?
Zero dedicated people at a startup (two part-time owners), 1–3 at a scale-up, 4–8 at a mid-sized company, and 15–25 at the largest enterprises. Beyond that, scale comes from contributors and automation.
Should the team sit in design or engineering?
Either can work. What matters more is one accountable leader and equal standing for designers and engineers. Joint quarterly reviews with both design and engineering leaders keep it balanced.
What does a design system designer do?
Designs foundations and components, maintains the Figma library, writes usage guidance, reviews product designs for system use, and runs workshops and office hours.
Do you need a dedicated design system engineer?
Yes, as soon as you have a dedicated team at all. Without engineering capacity the system never reaches code, and code is where adoption and most of the savings happen.
What are design system champions?
Designers or engineers in product teams who spend a small share of their time (often about 10%) as the system's local voice: early feedback, local help and contributions.
Further reading
- Team Models for Scaling a Design SystemNathan Curtis, EightShapes.
- The Salesforce Team Model for Scaling a Design SystemSalesforce UX. A cyclical model for how teams grow.
- Design Systems Report 2025zeroheight. Survey data on team sizes.
- Most design system leads are just librariansLayer One. On what leading a system really involves.
