System Parameters
Getting Buy-In
Building organizational support by speaking each stakeholder's language
Key Insight
Design systems require sustained investment and deliver value slowly at first. Getting buy-in means framing the work in terms each stakeholder cares about — speed for engineering, feature velocity for product, cost reduction for executives. Start with a demonstrable pain point, propose a pilot scope to reduce perceived risk, and deliver early visible wins within 6–8 weeks.
Key Points
- •Frame ROI in the audience's terms: speed (eng), velocity (PM), cost (exec)
- •Quantify current pain before proposing the solution
- •Pilot scope reduces risk perception and enables early proof of value
- •Engineers who help build the system become advocates for using it
- •Adoption metrics (component usage %, duplicate pattern count) build ongoing support
Guidelines
- ✓Find the pain point everyone already feels — use it as your entry point
- ✓Show don't tell: a proof of concept beats a slide deck
- ✓Plan early wins within 6–8 weeks to demonstrate momentum
- ✓Build a cross-functional working group, not a design-only initiative
- ✓Document and share adoption metrics as the system grows
Want to learn this interactively?
Experience hands-on experiments and test your understanding.
🔥
Practice this topic
Active recall — strengthens long-term retention