Tell your leadership team the company needs a design system, and the first question that comes back is almost always some version of “so what does that actually get us?” Consistency, efficiency, craft — the words designers reach for instinctively — tend to sound abstract to the people who sign off on budgets. Winning approval rarely starts with a better argument. It starts with a translation: taking the designer’s case and restating it in the language of business — time, money, and risk.
1. Talk about speed, not efficiency
“Our interfaces will be more consistent” is true, but it lands softly. “It will take less time to build a new screen” lands hard, because it points directly at something an executive already pays for. The most convincing material you can bring is not a vision deck — it is a short list of recent projects where your team rebuilt essentially the same component from scratch, again and again, with a note of how long each rebuild took.
If precise hours are difficult to reconstruct, don’t let that stop you. Simply counting the repetitions — how many times the same card, the same modal, the same form pattern was recreated across recent work — is usually enough to make the point. The number does the persuading; the framing just has to let it.
The weak version
“Consistency will improve.” Abstract, hard to price, easy to postpone.
The strong version
“New screens will ship faster.” Concrete, measurable, tied to cost.
2. Talk about risk — the cost you are already paying
The biggest obstacle to a design system pitch is that the status quo rarely looks broken. Screens ship, customers use the product, nothing is visibly on fire. Which is why the second translation matters: the absence of a system is not a neutral state. Every screen built with its own one-off components quietly widens the scope of future work. When the rebrand comes, or when accessibility compliance becomes a requirement rather than an aspiration, every inconsistency you tolerated becomes a line item.
For most leadership teams, “if we don’t start now, the eventual bill gets much larger” is a more persuasive frame than “we should invest in this now.” The first frames inaction as a decision with a cost. The second frames action as an expense. Same proposal — very different reception.
3. Start small and manufacture evidence
Asking for company-wide adoption in one move is the hardest possible version of this pitch. The realistic path is to pilot the system on a single project or team, measure what changes, and use that result to justify expansion. The pilot doesn’t need to be glamorous — it needs to be measurable. Use the same review criteria you would apply in design QA, and compare screen quality and defect rates before and after. The evidence for your next, bigger ask accumulates almost as a side effect.
Pick one project or team as the pilot — small enough to control, real enough to count.
Compare screen quality before and after, using your existing design QA criteria.
Record the changes in repeated-work time and defect rates as plain numbers.
Bring those numbers to the table and ask for expansion — with evidence, not projections.
There is a useful side argument here as well: AI tooling. As more design work flows through AI-assisted tools, the quality of their output depends heavily on the structure underneath. Without organized tokens and components, AI-generated screens inherit all the inconsistency of the source material. A design system is what makes the new tools actually deliver — and well-documented public systems like Google’s Material Design show how much faster new tooling lands when the foundations are in order. For an executive already curious about AI, that connection often carries more weight than any argument about craft.
💡 Pro tip — Keep a running log of repeated-work hours and rebuild counts before you ever make the pitch, and pair your ask with clear targets for the first three months after approval. Concrete numbers on both sides of the decision visibly raise your odds.
4. Don’t miss the window
The same proposal can pass or die depending on when it is raised. The moments when a company is already paying attention to its design output — a rebrand, a new product launch, an engineering migration that forces components to be rebuilt anyway — are the moments when a design system conversation costs the least to start. The appetite for change already exists; you are attaching your proposal to momentum rather than generating it from scratch.
Pitching in steady state
No shared appetite for change. Every point must be argued from zero.
Pitching at a transition
Rebrand or platform migration underway — consensus for change already exists.
The most common mistake is waiting for the deck to be perfect. In practice, the right timing beats complete material almost every time — if the organization is visibly at a turning point, pitch with what you have. This is also why the running log matters: when the window opens, you don’t want to be assembling evidence while it closes. And note that watching for timing is not the same as passively waiting for it. Look at the projects currently in flight and ask which of them could naturally carry a design system pilot — the window is often already open somewhere.
Closing thoughts
Condensed into a checklist, the pitch looks like this: turn repeated work into numbers, describe the concrete risk of doing nothing, run a small pilot before asking for company-wide adoption, connect the system to the AI tools your leadership is already curious about, and attach clear ninety-day targets to the ask.
Persuading a company to adopt a design system is, in the end, an act of translation — converting a designer’s daily friction into the company’s cost and risk. And the fastest route there is rarely the grand vision. It is one small piece of evidence, measured honestly, presented at the right moment.
Design Daily Life · Notes on design, daily