Loading…
Loading…
• Selling design decisions means making the rationale behind your choices clear, evidence-based, and tied to shared goals. • Use the framework: user need + business goal + evidence = persuasive argument. • The best designers don't just make good decisions — they make others understand why those decisions are good.
stellae.design
Selling Design Decisions is the skill of persuading stakeholders, clients, and team members that your design choices are the right ones. Tom Greever's 'Articulating Design Decisions' (2015) formalized this as a core UX competency. It combines evidence from user research, alignment with business objectives, design principles, and rhetorical skill. This isn't about manipulation — it's about helping non-designers understand the reasoning behind design choices that might seem subjective. Every unsold design decision is a missed opportunity to build trust and advance the user experience.
Even the best design work fails to ship if the designer cannot articulate why it is the right solution to the people who control resources, timelines, and technical direction. Selling design decisions is the practice of framing UX rationale in terms that resonate with each audience — executives care about business impact, engineers care about feasibility and maintainability, and product managers care about user outcomes and roadmap alignment. Designers who treat persuasion as a core skill, not an afterthought, see their work implemented more faithfully and build the organizational trust that earns them a seat at strategic conversations.
A designer proposes simplifying a mega-menu navigation after A/B testing shows that users find target categories 40 percent faster with a streamlined layout. Rather than presenting the design first, the designer opens the stakeholder meeting with the test results, walks through three user session recordings, and only then reveals the proposed solution as the logical response to the evidence. The data-first framing eliminates subjective taste debates and the redesign is approved in a single meeting.
A design lead reframes an accessibility remediation project for the executive team by quantifying the addressable market of users with disabilities, the legal risk of non-compliance, and the SEO benefits of semantic markup improvements. Instead of positioning the work as a compliance obligation, the presentation frames it as a growth initiative that opens a new customer segment while reducing legal exposure. The executive team approves the budget in the same quarter rather than deferring it indefinitely.
A designer walks into a stakeholder review with a polished high-fidelity mockup and no research, analytics, or usability data to support the proposed changes, relying entirely on aesthetic judgment and personal preference. When the VP of Engineering asks why the information hierarchy was reorganized, the designer responds with "it just feels cleaner," immediately losing credibility with a technical audience that expects evidence-based reasoning. The proposal is shelved and the designer is asked to return with data, delaying the project by six weeks.
• The most common mistake is leading with the solution instead of the problem — stakeholders who have not been walked through the user pain first have no context for evaluating whether the proposed design is appropriate. Another frequent error is using design jargon ("visual hierarchy," "affordance," "cognitive load") with non-design audiences, creating a communication gap that makes the rationale feel abstract rather than actionable. Designers also underestimate the power of showing failed alternatives; demonstrating what was tried and rejected builds confidence that the recommended direction was reached through rigorous exploration rather than arbitrary preference.
Was this article helpful?