As asked
You need to change the Tabs component markup in a way that breaks some consumers. How do you ship it across a large organisation?
Sample answer outline
Inventory usage first so the blast radius is known. Provide a migration guide, codemod if feasible, compatibility wrapper, and a deprecation timeline with clear owner communication. Release the change behind a new major version or opt-in flag depending on the package model. Track adoption and support the highest-impact teams rather than waiting for breakage at the deadline. A good answer balances semantic versioning discipline with product reality: sometimes the design system team must help migrate critical consumers directly.
Expect these follow-ups
- When would you avoid a breaking change even if the new API is cleaner?
- How do you find all consumers in a polyrepo organisation?
- What support promise should a design system make?
versioningmigrationadoption