Designers often focus on selling their craft to design managers, but the final hiring decision frequently lies with product leaders. To succeed, designers must frame their value as a business investment, emphasizing the ROI and metric impact that resonates with the ultimate approver.

Executives don't care about tactical benefits like 'five fewer clicks'. A crucial skill for modern sellers is to extrapolate that tactical user-level gain into a strategic business outcome. You must translate efficiency into revenue, connecting the dots from a daily task to the company's bottom line.

To get buy-in for developer experience initiatives, don't use generic metrics. First, identify leadership's primary concerns—be it market share, profit margin, or velocity. Then, frame your measurements and impact using that specific language to ensure your work resonates.

Stakeholders will ask "so what?" if you only talk about developer efficiency. This is a weak argument that can get your funding cut. Instead, connect your platform's work directly to downstream business metrics like customer retention or product uptake that your developer-users are targeting.

To get buy-in from skeptical, business-focused stakeholders, avoid jargon about user needs. Instead, frame discovery as a method to protect the company's investment in the product team, ensuring you don't build things nobody uses and burn money. This aligns product work with financial prudence.

To get product management buy-in for technical initiatives like refactoring or scaling, engineering leadership is responsible for translating the work into clear business or customer value. Instead of just stating the technical need, explain how it enables faster feature development or access to a larger customer base.

The company's design leadership is pushing back against justifying design solely through business metrics, arguing it signals a lack of confidence in craft. They foster a culture where the primary measure of success is the team's own high bar for taste, trusting this will ultimately drive long-term value.

Shift your team's language from tracking output (e.g., 'deployed XYZ API') to tracking outcomes. Reframe milestones to focus on the business capability you have 'unlocked' for other teams. This small linguistic change reorients the team toward business impact and clarifies your contribution to metrics like NPS.

While brand consistency is a benefit, the primary business impact of a well-built design system is operational efficiency. It drastically accelerates speed to market for new features and slashes onboarding time for new hires because the system's intelligence is effectively self-documenting.