Book a call

Work / CARS24

CARS24CARS24 · 2025 · Governance, Operations

How the design system team stopped being the bottleneck

As CARS24 grew, every team needed something from the design system, and one small team couldn't keep up. Requests piled up, nobody could see what was happening, and teams built around us. We changed how work came in, got decided and got built.

Role
Design Systems Lead
Focus
Governance, prioritisation, contribution
Platforms
Web, iOS, Android
Markets
India, UAE, Australia
Requests from six teams flowing through one front door, a score and three ownership tiers to release

The 30-second version

The problem

Every request from every team ran through one small team. No front door, no shared rules, no way to help. Most requests just waited.

What we did

One front door, a 70-point scorecard anyone can apply, three ownership tiers, a contribution playbook and a steady listening rhythm.

What changed

Every decision came with a reason. Teams planned around releases, and more people built with the system instead of around it.

70 pts
scorecard any team can apply
7 steps
one path for every request
3 tiers
core, extended and custom ownership
4
listening rhythms: daily to quarterly
01

Six requests a week, one answered

Requests arrived by DM, Slack, meetings and hallway chats. Yes or no depended on who asked loudest, so teams stopped trusting the answer.

# design-system-help6 new requests this week · 1 answered
SE

Product designer · Seller10:14

We need a custom card for car pricing on the seller flow. Can it go into the library? We launch in two weeks.

No replies yet

LO

Frontend engineer · Loans11:02

Can we add a heatmap chart? Our dashboard needs one and I'd rather not build it from scratch.

👀 1

BU

Product designer · Buyer16:40

Our flow needs a special carousel. Is there a way to do it with what we have?

NC

Product designer · New cars09:31

Can I add this new filter pattern? Happy to do the Figma work myself.

2 replies · last reply 9 days ago

AE

Mobile engineer · UAE12:05

We built a checkout component. Can other teams use it? Where would I even put it?

AU

Product designer · Australia15:22

How do I propose a new button variant? Is there a form somewhere?

👍 4 · +1 same question

Recreated from real requests. Names removed.

No front door

Requests came in everywhere, so nobody could see them all, including us.

No shared rules

Answers depended on who asked, so teams couldn't predict them.

No way to help

Teams that had already built something had nowhere to put it.

02

We tried the usual frameworks first

Seven angles of research, from shadowing to surveys. Then we scored real requests with RICE and MoSCoW. With RICE, people argued about the numbers; with MoSCoW, everything was a Must.

RICE: tried

Weighs value against effort, but reach and confidence are guesses for a shared component. The score became the argument.

MoSCoW: tried

Quick and familiar, but every team's request was a Must, and the label never explained why.

Our scorecard: used

Four questions a product designer can answer without us: where, who reuses, do we have it, how hard.

Tested in the open

Requesters scored their own asks next to ours. Where it felt wrong, we adjusted it.

Read the detail

We interviewed designers, engineers and PMs; mapped where requests got stuck; looked at unused and stalled requests; benchmarked Base, Shopify Polaris and Agoda; surveyed how much teams trusted the process; ran experiments; and shadowed teams to watch delays happen live.

03

Every request takes the same path

A bug, a new variant or a whole new component: everything goes through the same seven steps, so anyone can tell where a request is and what happens next.

Step 1 of 7

Ask

Post in #design-system-help or fill in the proposal form: what it's for, who needs it and how often it comes up.

Who
Anyone
When
Any time
What comes out
A request with context
04

A score instead of an argument

Four plain questions, each worth points. Any ✕ stops a request. 55+ is accepted and built first, 40–54 accepted, under 40 deferred. Try it on a request of your own.

Where is it needed?

Work in main products helps the most people.

How many can reuse it?

A design system is for shared things.

Do we already have it?

Filling a real gap beats rebuilding what works.

How hard is it to build?

Quick wins go first.

0 / 70
Filter patternNew cars
55
Checkout componentUAE
50
Button variantAustralia
45
Carousel variantBuyer
35
Pricing cardSeller
25
Heatmap chartLoans
Won’t fix
The six requests from the channel, scored and put in order. Scores are illustrative.
05

Not everything belongs in the core

Three rings. The closer to the centre, the more widely a component is used and the more the system team looks after it. Select a ring.

Used everywhere: buttons, inputs, tokens.

  • Designs: system team
  • Builds: system team
  • Reviews: system team
  • Maintains: system team
06

A system you set and forget falls apart

Listening was built into the routine at every speed, and a four-step playbook let teams contribute: propose, review and score, build together, document and release.

W1
W2
W3
W4
W5
W6
W7
W8
W9
W10
W11
W12
W13

Daily: Slack help and release channelsWeekly: office hoursQuarterly: system audit

One quarter of listening: every day, every week, every quarter.
07

From gatekeeper to partner

Flip between before and after.

  • Teams worked in silosA shared language and shared habits
  • Forked styles and duplicate workConsistency through tokens and the system
  • Rules handed down from the topContributions led by the community
  • The design system was a blockerThe design system was an enabler
  • Fear of changeTrust and collaboration

Designers

Trusted the tools and patterns.

Engineers

Started suggesting improvements themselves.

Product managers

Saw the system as a way to ship faster, and planned around releases.

The system team

Stopped being a bottleneck and became a facilitator.

08

What we'd do again

Agree on the goal first, and treat governance as the thing that lets you scale.

Agree on the goal first

Every later argument is easier when everyone signed up to the same outcome.

Governance is what lets you scale

Without it, more demand just means a longer queue.

Templates are lifelines

They made the right thing the easy thing.

Culture matters as much as code

The process only worked once people trusted it.

+

From the files

Select any image to see it full size.

Led by Aniket Pandey as Design Systems Lead at CARS24, with CARS24's design, engineering and product teams. Images belong to CARS24 and are shown for portfolio purposes.

Need this for your product?

We do this work for product teams now. Start with a two-week audit.

Next case studies