To truly resonate with an economic buyer, align your solution to the specific KPIs they are personally accountable for. These metrics often differ from those of your champion or general corporate objectives like revenue and cost savings, requiring tailored messaging.

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.

Not all design impact can be quantified with metrics. When data is unavailable, frame your value by highlighting contributions to competitive parity, internal team efficiency, or bug reduction. This holistic view of business health resonates with leadership beyond just product managers.

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.

Don't be afraid to surface problems to executives, as their job is almost entirely focused on what's not working. Withholding a problem is unhelpful; clarifying and framing it is incredibly valuable. Your champion isn't offending their boss by raising an issue, they're demonstrating strategic awareness.

Structure your final presentation by calling out specific problems you learned from individual contributors by name. Then, immediately pivot to show how solving their problem directly contributes to the high-level business objective owned by the executive decision-maker. This makes every stakeholder feel heard and demonstrates their strategic value.