5 Things a founder should know about UX

1. UX is not UI

This is the most common misconception. Founders hear "UX" and think visual design: colors, fonts, layouts. That's UI (User Interface). UX (User Experience) is bigger.

Don Norman coined the term in 1993 when he joined Apple as their first "User Experience Architect." His definition covers every interaction a person has with your product, from the first visit to your website to the moment they cancel their subscription.

UX includes how easy your product is to learn, how quickly users accomplish their goals, how they feel using it, and whether they come back. It's research, information architecture, interaction patterns, content, and yes, visual design too, but as one piece of a much larger puzzle.

When founders equate UX with aesthetics, two things happen:

• They spend $50K-$100K on pixel-perfect design that doesn't move metrics

• Or they dismiss UX entirely because the budget isn't there for a "designer"

Neither is right. UX starts with understanding your users, not opening Figma.

For a deeper dive into the full scope, see our guide on what product design actually covers.

2. UX directly impacts your revenue

This isn't soft advice. The numbers are clear.

Companies in the top quartile for design outperform their peers by 32 percentage points in revenue growth (McKinsey Design Index). And CB Insights found that 17% of startup failures are directly attributed to poor user experience and product design, making it the third most common reason after lack of market need and running out of cash.

Here's where it gets practical for SaaS founders:

Onboarding is the silent killer. If your trial users don't understand your product in the first session, they're gone. One study across 12 SaaS products found that refining onboarding, pricing pages, and in-app flows produced an average 17% boost in trial-to-paid conversion.

Friction compounds. When users encounter friction, 88% won't come back. Every confusing form field, every unclear label, every extra click is a leak in your funnel.

A UX audit can identify these leaks for a fraction of what a full redesign costs. The difference between spending $3K on an audit now versus $100K on a redesign later is when you choose to look.

3. Talk to your users before you build

The most expensive UX mistake is building something nobody needs. And the fix is surprisingly cheap.

Jakob Nielsen's research shows that testing with just 5 users reveals about 85% of usability problems. You don't need a lab, a budget, or a dedicated researcher. You need 5 conversations.

Yet founders consistently skip this step. One commonly cited example: a founder spent 8 months and $47K building a food delivery app without ever talking to a single restaurant owner.

Here are good questions to ask before you start designing:

• What problem is this product supposed to solve?

• What are the real pain points of my target audience (not what I assume they are)?

• How are people solving this problem today, without my product?

• What would make them switch?

These aren't UX-specific questions. They're business questions. But answering them through user interviews rather than assumptions is the difference between building something people want and building something you think they should want.

We've seen this play out firsthand. When we helped InCalendar validate their MVP in two weeks, guerrilla user testing with just 10 professionals gave them enough signal to secure investment, before a single line of code was written.

4. Iteration beats perfection

One of the biggest traps founders fall into is waiting for the design to be "perfect" before shipping.

Here's the reality: it won't be perfect. It shouldn't be. Software design is iterative by nature. You ship, you observe, you improve. The goal isn't to get it right the first time. It's to learn as fast as possible.

This doesn't mean shipping garbage. There's a sweet spot between "too minimal" (a landing page with nothing behind it) and "too polished" (6 months of design refinement before any user sees it).

The sweet spot: solve one core problem well enough that users come back. Then improve based on what you learn.

A Design Sprint is one way to find that sweet spot quickly. In a structured sprint, you go from problem definition to tested prototype in days, not months. It forces decisions and kills the "Phase Two" mentality where good ideas go to die.

What iteration looks like in practice:

• Ship a focused first version

• Watch what users actually do (not what they say they'll do)

• Fix the biggest friction point

• Repeat

This is how outcome-focused design works. You're not chasing feature completeness. You're chasing the outcome that matters most.

5. UX is a team sport, not a designer's job

The last thing founders get wrong: treating UX as something you hand off to a designer and wait for results.

In a startup, everyone shapes the user experience. The developer who adds an extra confirmation dialog, the PM who prioritizes a feature nobody asked for, the founder who insists on a complex pricing page - these are all UX decisions. They just aren't being made with UX thinking.

The fix isn't hiring a "magical UX designer" who solves everything solo. The fix is making UX a shared discipline.

What this looks like:

• Engineers sit in on user interviews so they see the problems firsthand

• Product decisions start with "what user problem does this solve?" not "what should we build next?"

• Design reviews include someone from support who hears complaints daily

This is what we mean by co-design. When the whole team participates in understanding users, the product reflects that understanding. When design is siloed, you get a pretty interface wrapped around confusing workflows.

The ugly truth about beautiful products

One contrarian point worth addressing: ugly products win all the time.

Craigslist generates over $1B/year in revenue with 50 employees and a design that hasn't changed since 1995. Early Google was a logo and a search box while Yahoo built a gorgeous portal. Reddit had 234M unique users while looking like a 2005 message board.

The pattern? These products delivered clear functional value. Users chose them not because they looked good, but because they worked.

The lesson for founders: don't confuse UX with polish. A clear, usable product with basic visuals will always beat a beautiful product that confuses people.

Invest in understanding your users and removing friction. The visual refinement can come later.

What to do next

If you're a founder reading this, here are three steps you can take this week:

1. Talk to 5 users. Not friends, not investors, actual users. Ask them what's confusing, what's missing, what they'd pay for.

2. Audit your onboarding. Watch someone use your product for the first time. Don't help them. Count the moments they hesitate.

3. Fix the biggest friction point. Just one. The one that causes the most drop-off or support tickets.

If you want an outside perspective, our free expert review gives you UX insights for your SaaS product in a 30-minute session. Or if you're ready for a deeper engagement, book a discovery call and let's talk about what's working and what isn't.

Related reading

• A Practical Guide to the Double Diamond Design Process - the discovery and delivery framework behind good UX decisions

• 5 Qualities of Great Product Designers - what to look for when you're ready to hire

• UI/UX vs Graphic Design - a deeper dive into the distinction covered in point #1

• Why You Should Invest in Design - the full business case for design investment

• Design Verification vs Validation - how to make sure what you build matches what users need