A fitness-tracker app's design-system team loses its executive sponsor in a reorganisation, and product leads start reclaiming contributors' time; what do you do?
answer
- what the sponsor actually provided
- who benefits most now
- value in the new leader's terms
- renegotiate allocations explicitly
- shrink scope to real capacity
basics
~20 sIdentify what the sponsor provided, usually funding protection, priority and escalation, then find a new sponsor among the leaders who benefit most, show value in their terms, renegotiate contributor time explicitly, and shrink commitments to what the remaining capacity can sustain.
solid answer
~40 sFirst I would name what the **sponsor** actually gave us: protection for budget and headcount, a priority that let contributors say no to product work, and an escalation path when teams disagreed. Then I would **find a new sponsor** quickly, starting with leaders whose goals depend on the system, such as whoever owns the next device launch, and show value in their terms rather than the system's. In parallel I would **renegotiate contributors' time explicitly** with product leads, so allocations are agreed rather than silently reclaimed, and **shrink scope** to what the remaining people can support, telling consuming teams what changes. Continuing as if nothing happened risks a slow decay nobody notices until the system is stale.
go deeper
Recall that an executive sponsor is a senior leader who protects the system's funding and priority, not someone who builds it.
Explain what a sponsor concretely provides, such as budget protection, priority and escalation, and why contributor time erodes when that support disappears.
Show the sequence you would follow: name the loss, find a sponsor, renegotiate allocations explicitly and shrink scope honestly, without alienating product leads.
Address the structural fragility of single-sponsor systems and how broad, regularly evidenced support protects the system through leadership changes.
## What an executive sponsor provides An **executive sponsor** is a senior leader who backs the design system: not someone who does the work, but someone who makes it possible. Their value is usually invisible until it is gone. Typically a sponsor provides: - **Funding protection**: headcount and budget that survive planning cycles. - **Priority**: a clear statement that system work matters, which lets contributors decline competing product work. - **Escalation**: a place to resolve disagreements between the system team and product teams. - **Alignment**: linking the system to organisation goals so it is not seen as a side project. When a reorganisation removes the sponsor, those supports weaken at once, and the first visible symptom is usually product leads reclaiming contributors’ time. ## The scenario A company building a fitness-tracker companion app runs a hybrid design system: two dedicated people and rotating contributors from the activity, sleep, coaching and device-setup teams. After a reorganisation, the vice-president who sponsored it moves to another division. Within weeks, two product leads pull their contributors back to meet a launch date. ## What to do, in order 1. **Name what was lost.** List what the sponsor actually provided. This tells you what the new sponsor must provide and what you must replace in the meantime. 2. **Find a new sponsor.** Look for leaders whose goals depend on the system, such as the leader of an upcoming wearable launch that needs shared components on a new screen size, or whoever owns accessibility risk. Prefer someone with influence over the product leads now reclaiming time. 3. **Show value in their terms.** Prepare evidence that matters to that leader, such as time saved on the last launch, accessibility defects avoided, or duplicated work removed, rather than component counts. 4. **Renegotiate allocations explicitly.** Meet product leads, acknowledge their deadlines, and agree what contributor time is realistic. An explicit smaller allocation is better than an informal larger one that keeps disappearing. 5. **Shrink scope to real capacity.** Decide what the system will keep supporting and what pauses, for example new components for the wearable, and tell consuming teams. 6. **Protect the core.** Continuity of the dedicated people matters more than any single feature; losing them turns a slowdown into decay. ## Mistakes to avoid | Mistake | Why it hurts | |---|---| | Carrying on as if nothing changed | Promises exceed capacity; quality drops quietly and trust erodes | | Fighting product leads for their people | Creates enemies at the moment you need allies | | Waiting for leadership to notice | Without a sponsor, nobody is looking | | Pitching the system in its own vocabulary | A new leader needs their problems solved, not a lesson in design systems | | Letting contributors drift away informally | The allocation vanishes without anyone deciding it should | ## Talking to the product leads The product leads reclaiming time are not opponents; they are under pressure from the same reorganisation. A productive conversation: - starts from their deadline and acknowledges it is real; - shows what their team gets from the system, such as the chart and tile components their next release relies on; - asks what contributor time they can realistically offer, even if smaller, and writes it down; - agrees when the allocation will be reviewed, for example after the launch. A smaller agreed allocation, recorded in planning, survives the next crunch far better than a larger informal one. ## Reducing dependence on one person The episode also exposes a structural risk: a system backed by one leader is fragile. Longer term: - cultivate support from several leaders who benefit, not one; - report value regularly, so the case is already made when leadership changes; - write contributor allocations into planning, so they survive a change of leadership; - make product teams’ dependence on the system visible, so its loss would be noticed. ## What the interviewer is listening for - Understanding that a sponsor provides protection, priority and escalation, not just approval. - Acting quickly and diplomatically rather than defensively. - Honesty about capacity: shrinking promises is a sign of maturity, not failure. - A plan to make the system less dependent on any single leader.
- How do you choose a new sponsor?Look for a senior leader whose goals depend on the system, such as someone owning an upcoming launch, brand consistency or accessibility risk, and who has influence over the teams contributing time. A sponsor who benefits directly will defend the system in planning; one who agrees in principle but gains nothing will not. Several supportive leaders are better than one.
- Why tell consuming teams when you shrink the system's scope?Because they plan their own work around what the system promises. If a component they expected pauses silently, they discover it at their deadline and lose trust in the system. Announcing what continues, what pauses and what they should do in the meantime lets them plan, and shows the system is being run honestly under constraint.
saying these in an interview costs you the question
- Keeps every commitment unchanged after losing contributors and a sponsor.
- Tries to win contributors back by fighting their product leads.
- Assumes the system will be fine because it is technically good.
- Pitches a new sponsor using design-system vocabulary instead of their goals.
- Treats the sponsor as a formality with no practical role.