Design value: benefits over features
Stop talking about design quality and start talking about business impact. Learn the benefits-over-features method to position design as an essential business investment.
Designers, don’t forget: You were hired to build a business. But too often, we talk about our work in ways that don’t connect to business value. We describe features, quality, and user experience: language that only designers care about.
The goal is to solve problems for our users and create value for them through our designs. But design is the how; building a business is the why. To get a seat at the table, we need to talk about design in business terms.
Here’s how to show your value using the benefits-over-features method:
The problem with designer language
While design has been talking about “empathy” and “advocating for users,” product has been selling “acquisition, activation, retention, monetization.” And we wonder why they got a seat at the table.
The people paying your salary are focused on revenue, not empathy. We know the best way to sustainably achieve revenue growth is to understand what customers want and provide it with an attractive and intuitive service. But we need better frameworks for communicating it.
Language That Doesn't Work
When you say you “advocate for the user,” it sounds like you’re not advocating for the business. Empty phrases that don’t translate into tangible value include:
- “Improving design quality” or “consistency”
- “Making things look good” without linking to brand perception
- “Better user experience” without connecting to business outcomes
- Talking about design systems for “consistency” without showing impact
The benefits-over-features framework
Instead of describing what you did, describe what it achieves. Instead of talking about features, talk about benefits. Instead of design outputs, talk about business outcomes.
Don’t talk about design quality → talk about impact
Don’t say:
“I improved the quality of the design”
Say instead:
“This design reduces user errors by 30%, which decreases support ticket volume and improves customer satisfaction scores.”
Don’t present “cleaner design” → explain efficiency gains
Don’t say:
“I created a cleaner, more modern design”
Say instead:
“This design reduces cognitive load and boosts efficiency. Users complete tasks 40% faster, which increases productivity and reduces training costs.”
Don’t stop at “better UX” → connect to long-term profit
Don’t say:
“I improved the user experience”
Say instead:
“By improving onboarding completion rates, we’re increasing activation. Higher activation directly drives subscription revenue and reduces churn, creating long-term profit through improved customer lifetime value.”
Don’t sell accessibility as “the right thing” → talk about market potential
Don’t say:
“Accessibility is the right thing to do”
Say instead:
“Making our product accessible opens us up to an untapped market of 15% of potential users. This represents a significant growth opportunity and reduces legal risk.”
Don’t offer “intuitive navigation” → show path to purchase
Don’t say:
“The navigation is more intuitive now”
Say instead:
“Simplified navigation reduces steps to purchase by 3 clicks. In testing, this accelerated the path to purchase, increasing conversion rates by 12%.”
Don’t focus only on “inclusive imagery” → describe brand impact
Don’t say:
“I added more inclusive imagery”
Say instead:
“Inclusive imagery enhances brand perception and broadens our demographic appeal. This positions us as a modern, thoughtful brand, which improves brand search and referral rates: the cheapest form of acquisition.”
The pattern: features → behaviours → metrics → business outcomes
Every benefit statement follows this pattern. You connect your design feature to a user behaviour, that behaviour to a product metric, and that metric to a business outcome.
The Connection Chain
Feature: Simplified checkout flow
→ Behaviour: Users complete checkout faster with fewer errors
→ Metric: Checkout completion rate increases 15%
→ Business Outcome: Increased revenue and reduced support costs
When you frame design this way, you’re speaking the language of business. You’re connecting your work directly to the company’s growth and success.
Talking about work in terms of outcomes
Instead of saying “I created a new landing page design,” frame it as “I increased trial signups by 15% through a new landing page redesign.” Connect your design solutions to tangible results that matter to the business.
The format recommended by Google recruiters works well here: “Accomplished [X], as measured by [Y], by doing [Z].”
Example:
❌ “I redesigned the onboarding flow”
✓ “Using a combination of funnel analysis, session recordings, and usability testing, I redesigned the onboarding flow, increasing subscription rates by 12%“
Connecting design to business goals
The cheapest form of acquisition is through branded search and referrals, stemming from great design. Product-led growth is fueled by onboarding experiences that build trust and deliver early value. High retention rates are achieved through experiences that meet or exceed customer expectations.
All of this is only possible via design. We understand the critical role of design in these areas. Let’s stop second-guessing the direct correlation between every minute design change and a business outcome. Perfect data quantifying the value of design is a myth.
Instead, confidently link your work to key metrics. If you’re enhancing a particular aspect of onboarding, state that it’s a leading indicator of increased activation rates. That’s it. Not everything in design can be precisely tracked, and that’s okay.
The Reality of Design Metrics
You will never calculate the “ROI of design.” Developers have no idea about the value of their code either. But what you can do is:
- Design for an emotional response
- Expect a behavioural response
- Track the change in behaviour
- Understand the product metric that your work impacts
- Comprehend where your designs fit into the wider business context
Design alone does not produce value; it’s only when combined with development, sales, marketing, support, etc., that we produce value. Focus on tracking immediate changes in user behaviour and communicate an understanding of what business goals that behaviour influences.
Practical examples: reframing common design descriptions
❌ Feature-focused: “I created a new design system with consistent colors and typography”
✓ Benefit-focused: “A consistent design system reduces development time by 30% and ensures brand consistency across touchpoints, which improves brand recognition and reduces customer confusion.”
❌ Feature-focused: “I improved the visual hierarchy of the dashboard”
✓ Benefit-focused: “Improved visual hierarchy directs user attention to key actions, increasing feature adoption by 25% and improving time-to-value for new users.”
❌ Feature-focused: “I made the mobile experience more responsive”
✓ Benefit-focused: “Responsive mobile design captures the 60% of users who access our product on mobile, directly impacting user acquisition and engagement metrics.”
The language shift: from design to business
Design is at a turning point. Maybe now is the time to stop using language only designers care about. The people paying your salary are focused on revenue, not empathy. But we know the best way to sustainably achieve revenue growth is to understand what customers want and provide it to them in the most enjoyable and seamless way possible.
Here’s how to translate design language into business language:
Design language → Business language
- “Advocating for users” → “Increasing activation rates”
- “Design quality” → “Reducing support costs”
- “Better UX” → “Driving retention”
- “Consistency” → “Improving conversion”
- “Cleaner design” → “Reducing churn”
- “More intuitive” → “Increasing revenue”
How to apply this framework
Before presenting any design work, ask yourself:
- What user behaviour does this design influence?
- What product metric does that behaviour impact?
- What business goal does that metric support?
- How can I frame this in terms stakeholders will understand?
Practice reframing your design descriptions. Take any feature or design decision and connect it through the chain: Feature → Behaviour → Metric → Business Outcome.
Quick Practice Exercise
Take a recent design project and practice reframing:
- Write down what you designed (the feature)
- Identify what user behaviour it should change
- Connect that behaviour to a product metric
- Link that metric to a business outcome
- Write a single sentence that captures the benefit
Use this sentence in your next presentation, case study, or portfolio.
Remember: design is how, business is why
Use the benefits-over-features method to position design as an essential investment for the business, linking your expertise directly to the company’s growth and success. When you talk about design in business terms, you demonstrate strategic thinking. You show you understand why design matters, not just how to do it.
The goal is to solve problems for our users and create value for them through our designs. But design is the how; building a business is the why. When you communicate in terms of business value, you’re speaking the language that gets you a seat at the table.