UI/UX Audit: I Found 47 Dead Features in One Product (Here's How to Audit Yours)

I ran a UX audit on a SaaS product last year. The founder wanted a redesign: "Everything feels cluttered. Users get confused. We need to start fresh."

The audit revealed 47 features in the interface. Users actively used 12.

The other 35? Dead weight. Legacy toggles from 2019. Settings nobody changed. Flows that led nowhere. Tooltips explaining features that no longer existed.

The product didn't need a redesign. It needed a reckoning.

Before you book that redesign sprint – stop. You might not need new design. You might need to remove 70% of what's already there.

Your product works. Mostly. The flows are familiar. The navigation kind of makes sense. Nothing's technically broken.

And yet, everything feels... off.

That's not a design problem. That's accumulation.

Over time, products collect:

• Features launched and forgotten

• Settings screens full of toggles you no longer support

• Microcopy referencing workflows from three roadmaps ago

• Modals, tooltips, and checkboxes added "just in case"

• Hidden features nobody finds

It's not broken. It's bloated. Which means the fix isn't a new coat of paint. It's a hard look at what actually needs to be there.

I've run UI audits on 50+ products. The pattern is always the same:

Product launches lean. Team adds features. Nobody removes anything. Three years later, the interface is a museum of abandoned ideas.

A client once defended a 23-field settings page: "Power users need all these options."

Usage data: 6 of those fields had been touched in the last 6 months. Total. Across 3,000 users.

That's 17 settings taking up space, adding complexity, creating confusion – for zero benefit.

Redesigns fix:

• Visual inconsistency

• Outdated aesthetics

• Brand evolution

• Design system implementation

Product UX audits fix:

• Functional drift

• Feature bloat

• Navigation confusion

• UX debt accumulation

You can't redesign your way out of structural clutter. You'll just make the bloat prettier.

When you need a UI audit (not a redesign):

Your product feels cluttered, but you can't pinpoint why. A quick UX audit will show you.

Users say "it's confusing" but analytics show no specific error patterns. That's feature overload, not broken flows.

Your team debates adding more tabs/menus/sections. Stop. Audit what's already there first.

Navigation structure reflects internal org chart, not user mental model. Classic audit problem.

You're explaining features more than people are using them. That's clarity debt, not design debt.

When you actually need a redesign:

Your brand has evolved and the UI looks dated. Visual refresh makes sense.

Competitors have modern interfaces and yours looks like 2015. Perception problem, not function problem.

You're implementing a design system and need visual consistency. Good reason to redesign.

Your MVP evolved but the UI never caught up. Time to rebuild properly.

But before you redesign? Always audit first. Otherwise you're just polishing clutter.

Before you call it an audit, read what design audits are not.

Back to that product with 47 features and 12 actually used.

The founder wanted a redesign because:

• "Navigation feels overwhelming"

• "Users say it's confusing"

• "Competitors look cleaner"

• "We need a fresh start"

What the UI audit revealed:

Navigation chaos:

• 8 top-level nav items

• Only 3 got >20% usage

• 2 items went to pages with 0 weekly active users

• 1 item was a duplicate of another (different name, same feature)

Feature graveyard:

• 12 settings toggles changed by <5% of users ever

• 6 features launched 2+ years ago with 0 recent usage

• 4 "coming soon" placeholders that never shipped

• 3 export options that broke in 2022 and nobody reported it (because nobody used them)

Microcopy museum:

• Tooltips referencing "beta features" that launched 18 months ago

• Help text explaining workflows that no longer existed

• Error messages for edge cases the backend didn't support anymore

• CTAs like "Try our new dashboard!" (it was 2 years old)

Total inventory:

• 47 distinct features/sections/settings in the UI

• 12 actively used (>10% of users touched them monthly)

• 20 zombie features (exist but ignored)

• 15 actually dead (broken, outdated, or impossible)

What the founder thought: "We need to redesign everything."

What they actually needed: "Remove 35 things and clean up the other 12."

What you find in an audit is usually the surface: the painful truth about UX/UI debt sits underneath.

Here's my product design audit process. Takes 2-4 hours for most products.

1. Navigation Sanity Check

Questions I ask:

• Can each nav item be described in one sentence?

• Does structure reflect user journey or internal org chart?

• Are items grouped logically or historically?

• What gets clicked? What gets ignored?

Red flags:

• Nav item names that need explanation

• Items with <10% monthly usage

• Structure that mirrors company departments

• "Other" or "More" catch-all sections

Real example: Client had "Portal" and "Workspace" in nav. Both went to the same feature. Nobody knew which to use.

Fix: Picked one name. Usage jumped 31%.

2. Feature Relevance Audit

Questions I ask:

• Which pages have low/no usage?

• What hasn't changed in 12+ months but takes up UI space?

• What features are users asking for that already exist (but can't find)?

• What gets explained in support more than used in product?

Red flags:

• Features with 0 weekly active users

• Settings walls where 90% of toggles never get touched

• "Power features" that require training docs

• Features hidden 3+ clicks deep with no discovery path

Real example: Hidden export feature in advanced settings. Usage: 0.3%. After surfacing it prominently: 18%.

Decision: If <5% use it monthly and you can't surface it better – remove it.

3. Microcopy Reality Check

Questions I ask:

• Are you over-explaining things that should be intuitive?

• Does tone still match your current audience?

• Do error messages actually help or just apologize?

• Are you using jargon your users don't use?

Red flags:

• Tooltips on every button

• Help text longer than the action it explains

• Politeness theater ("We're sorry, but...")

• References to features/flows that changed

Real example: Button said "Initiate workspace collaboration framework." Users ignored it.

Changed to "Invite team." Click rate up 220%.

4. Dead Logic & Abandoned Flows

Questions I ask:

• Are there UI components active but unsupported by backend?

• What can users click that doesn't work?

• What flows lead to dead ends?

• What features exist in UI but not in docs/support?

Red flags:

• Buttons that do nothing

• Forms that submit but don't save

• Features that look active but aren't

• Workflows that end without confirmation

Real example: "Share via email" button existed. Clicking it did nothing. No error. No feedback. Just silence.

How long had it been broken? 8 months. Nobody noticed because nobody used it.

Removed it. Zero complaints.

5. Visibility vs. Clarity

Questions I ask:

• Is everything visible but nothing obvious?

• Have you added explanation instead of fixing confusion?

• Are critical features competing with tertiary ones for attention?

• Can new users find their first win in 60 seconds?

Red flags:

• Empty states with 6 paragraphs of text

• Dashboard showing 15 metrics at once

• Every feature having equal visual weight

• No clear starting point for new users

Real example: Dashboard showed 23 different metrics. Users asked: "What should I look at first?"

We prioritized 3 key metrics. Feature adoption improved by 40%.

Case 1: The 47-feature product

Removed:

• 15 dead features (literally broken or impossible)

• 12 zombie features (working but ignored)

• 8 redundant settings

Kept and improved:

• 12 actively used features (cleaned up, clarified)

Results after 4 weeks:

• Navigation clicks up 34% (easier to find things)

• Support tickets down 28% (less confusion)

• Feature adoption up 41% (visibility improved)

• User sentiment: "Finally makes sense"

Cost of audit: 8 hours of my time Cost of avoided redesign: $40K+ they didn't need to spend

Case 2: The settings graveyard

Client had 31 settings. Users changed 6 on average.

Audit revealed:

• 18 settings never touched by >95% of users

• 5 settings that broke things when changed (so nobody changed them)

• 4 settings referencing features that didn't exist anymore

Removed: 23 settings Kept: 8 actually useful settings

Results:

• Setup completion time: 8 minutes → 2.5 minutes

• Support "how do I configure..." tickets: down 64%

• User activation: up 29%

Case 3: The navigation nightmare

8 top-level nav items. 3 got meaningful usage.

Audit showed:

• 2 nav items led to 0 weekly active users pages

• 1 was duplicate of another (different name)

• 2 more could be combined under shared concept

Simplified to: 4 clear categories

Results:

• Time to find features: down 40%

• Feature discovery: up 55%

• Users describing product as "intuitive": 23% → 67%

Run a UI/UX audit when:

• Product feels cluttered but you don't know why

• Users say "confusing" but analytics show no specific errors

• You're considering adding more UI when existing UI is ignored

• You inherited a product and need to understand what's actually being used

• Before any redesign (always audit first)

Skip straight to redesign when:

• Visual brand has completely evolved

• You're implementing a design system for consistency

• MVP needs professional treatment

• Competitor pressure is about perception, not function

• You've already audited and removed dead weight

Never redesign without auditing first. You'll just make the bloat prettier.

A UI design audit isn't sexy. It won't show up in portfolios. It uncovers things nobody wants to deal with (especially if a feature was someone's pet project).

But if you skip the reckoning, your next redesign will just repackage confusion.

A redesign is a risk. An audit is strategy.

If your product feels off but you're not sure why – don't reskin it. Run a proper UX audit. Ask the hard questions. Rip out what doesn't belong. Clarify what does.

Then – and only then – start designing again.