A few years ago, I found myself in a situation that's probably familiar to many designers: trying desperately to impress stakeholders by proving how design delivers ROI. I poured energy into detailed arguments about how every interaction and every feature could be tied back to measurable business outcomes. I thought I was being strategic — showing that design was more than aesthetics, that it could drive tangible results.
In hindsight, I was overcorrecting. Those arguments reflected a workplace culture that didn't value or trust design. I wasn't writing about ROI because I wanted to — I was writing about it because I felt I had to. Design, in that environment, was something to justify, not something to trust. And no amount of well-argued business cases could fix the underlying problem: a lack of genuine partnership between design and the rest of the organization.
Eventually, I moved into a role where design wasn't constantly under a microscope. Instead of justifying our existence, my team worked in real partnership with stakeholders, aligning on priorities and ensuring our choices supported business needs. The difference was immediate. We weren't just delivering ROI — we were building trust, driving innovation, and creating outcomes everyone could get behind.
This taught me something I wish I'd understood earlier: tying design to ROI sounds like a strategy problem, but it's usually a trust problem.
The mechanics are genuinely hard — user satisfaction improvements reduce churn but quantifying that relationship isn't straightforward, usability fixes improve experience but the immediate revenue impact is invisible, and in freemium contexts where conversion is the primary KPI, it's difficult to prioritize work that doesn't directly move that number. These are real challenges. But they become manageable when design and the business are solving them together, and nearly impossible when the designer is expected to solve them alone.
When I look back at the ROI arguments I was writing, I can see now that I was doing the work of an entire organization by myself — trying to be the designer, the analyst, and the business strategist simultaneously. That's not a sustainable position, and it's not how good work gets done. Connecting design to business outcomes is a shared responsibility: designers bring knowledge of user behavior, data teams provide the metrics, and stakeholders ensure alignment with business goals. When all three are in the room, the story tells itself. When the designer is alone in the room, the story becomes a defense.
If you're a designer spending more time justifying your work than doing it, the problem probably isn't your argument. It's the environment you're making it in. The goal isn't to get better at proving design's value — it's to be in a place where that value is understood well enough that you can focus on creating it.
Disclosures: All thoughts are my own. My current employer trusts design enough that I no longer have to write essays proving it — which, fittingly, is what freed me up to write this one.