Framework
Design systems are shared libraries of components (buttons, forms, colors).
PM's role: Ensure new features use the system.
| Scenario | Good | Bad |
|---|---|---|
| New feature needs a new button style | Ask design system team first | Build one-off style in feature |
| Button exists but needs tweaking | Propose addition to design system | Add styling in feature code |
| Multiple features need same pattern | Add to design system once | Each feature implements separately |
Actionable Steps
1. Collaborate With Design System Team Early
When designing new feature, ask: "Do we have components for this already?"
2. Resist One-Offs
Yes, building a custom button is faster. But multiply that by 10 features and you have inconsistent UI + maintenance nightmare.
3. Budget Time for Contributions
If your feature uses 60% existing + 40% new components, plan to contribute back to design system.
Key Takeaways
- Design system pays dividends over time. Resist short-term expedience.
- PM + Design collaboration here prevents waste. Get design system team involved early.