How would you pitch funding for a design system to the leadership of a streaming service that ships on TV and web?
answer
- their problems, not your solution
- evidence from your own products
- honest costs and a timeline
- a phased ask with success criteria
- tie it to a funded initiative
basics
~20 sLead with a problem leadership already feels, such as slow launches on new TV platforms, prove it with your own products' data, state costs and payback lag honestly, and ask for a phased investment tied to a roadmap initiative.
solid answer
~50 sI would start from **leadership's problems**, not the system: in a streaming service that is usually the cost and speed of shipping each feature on many TV platforms and the web, inconsistent brand experience, and accessibility risk. I would bring **evidence from our own products**, such as how many times the same media tile or player control has been built, and what a recent cross-platform change cost. Then I would state **costs honestly**, including migration and the lag before savings appear, and make a **phased ask**: a small team for a defined period, focused on the most duplicated parts, with success criteria agreed in advance. Tying the first phase to an initiative already on the roadmap, such as a new TV platform launch or a brand refresh, makes the value concrete and the timing obvious.
go deeper
Recall that a pitch starts from a business problem leadership already has, not from the design system itself.
Explain which evidence from your own products supports a pitch, such as duplicated components or the cost of a recent cross-platform change.
Show how you would structure costs, the payback lag and a phased ask with success criteria, and handle objections about slowing feature work.
Choose the value frame that matches the organisation's strategy, attach the first phase to a funded initiative, and plan how evidence keeps flowing after funding.
## Why this is a judgement question There is no single correct pitch. The candidate is judged on whether they can translate a design and engineering concern into terms leadership uses to allocate money: risk, speed, cost and strategy. The most common failure is pitching the solution (“we need a design system”) instead of the problem it solves. ## Structure of a strong pitch 1. **The problem, in leadership’s language.** For a streaming service shipping on web and several TV platforms: every feature is built several times, launches on a new platform are slow, the brand looks different on each screen, and accessibility defects repeat across apps. 2. **Evidence from your own products.** Counts of duplicated parts (how many media tiles, how many sets of player controls), the effort a recent cross-platform change took, repeated accessibility findings. Your own numbers beat industry claims. 3. **The proposal.** What the system is, at the level of detail leadership needs: shared decisions and the most duplicated components, owned by a small team. 4. **Honest costs.** Team, tooling, the migration effort consuming teams will pay, and ongoing upkeep. Hiding costs destroys trust at the first overrun. 5. **The payback lag.** Savings arrive after reuse starts; say when you expect the curve to turn. 6. **A phased ask.** A defined first phase with scope, staffing and a review point, rather than an open-ended commitment. 7. **Success criteria.** Agreed in advance, so the review is about evidence rather than opinion. ## Framing options and when each works | Frame | Works when leadership cares most about | Watch out for | |---|---|---| | Speed to market | Launching features or new platforms faster | Early phases may be slower, so state the lag | | Cost of change | Rebrands, redesigns, platform expansions | Needs a recent costly change as evidence | | Brand and experience | Consistency across devices, premium feel | Can sound like aesthetics unless tied to user or revenue outcomes | | Risk | Accessibility obligations, quality incidents | Avoid fear-selling; the system reduces risk, it does not remove it | Most pitches lead with one frame and support it with one other. Choosing the frame is the judgement: it should match the organisation’s current strategy. ## Tying to a funded initiative A standalone system proposal competes with every feature. Attaching the first phase to an initiative already funded, such as launching on a new television platform or a brand refresh, changes the question from “should we spend on this?” to “how should we deliver what we already committed to?”. The initiative becomes the first proof point. ## Anticipating objections - **“Will this slow feature work?”** Yes, briefly for early adopters; show the phase plan and where the time comes from. - **“Why not let each team share informally?”** Informal sharing works at small scale; show the duplication evidence that it has stopped working. - **“What if it fails?”** The phased ask with a review point limits the downside. - **“Who maintains it?”** A named team or allocation; a system without owners decays. ## After the funding decision A pitch is the start of a relationship, not a one-off event. Once the first phase is funded: - report against the agreed success criteria on a regular cadence, including where results lag; - show concrete wins in leadership's terms, such as a feature shipped on a new TV platform with shared parts, rather than internal output; - raise problems early, such as slower migration than planned, with a revised plan; - use the review point honestly: continue, re-scope or stop based on the evidence. Leaders who see a steady stream of honest evidence fund the next phase more readily than those who heard one confident pitch and nothing since. ## What to avoid - Unsourced industry percentages presented as promises. - A large first phase that tries to cover every component. - Treating the pitch as a one-off: leadership needs regular evidence after funding, not only before. - Promising that the system solves product problems it does not touch, such as content strategy or recommendation quality. - Pitching only to design and engineering leaders; the people who own product outcomes and budgets must see their own problem in the proposal, or the funding will not survive the next planning cycle.
- Why ask for a phased investment instead of full funding up front?A phase with defined scope, staffing and a review point limits leadership's downside, forces the team to deliver visible value early, and turns the next funding decision into a review of evidence. It also fits the reality that a system's value depends on adoption, which cannot be proven before the first parts exist. Full funding up front invites both over-building and scepticism.
- How do you choose which value frame to lead with?Match the frame to what leadership is already trying to achieve this year. If the roadmap is about expanding to new TV platforms, lead with speed and cost of change; if it is a brand refresh, lead with brand consistency; if accessibility findings are escalating, lead with risk. A frame that matches an existing priority needs less persuasion than a new priority invented for the pitch.
saying these in an interview costs you the question
- Opens with what a design system is instead of the problem it solves.
- Quotes unsourced industry percentages as guaranteed savings.
- Hides migration cost to make the numbers look better.
- Asks for open-ended funding with no review point.
- Uses accessibility risk as a scare tactic with overstated promises.