A personal, no-drama guide for founders and marketing leads

You probably don’t need a redesign. You need to tell the truth about what helps people move, and cut everything that doesn’t. Fewer screens. Fewer decisions. More outcomes.
I’m tired of shiny reskins that make screenshots look clever while users still feel lost. If you’re a founder or a marketing lead, you probably are too. Real people are busy. They’re not thinking about your roadmap. They’re thinking please can this just do the thing.
Here’s the naïve bit - and I say naïve on purpose:
The best products feel obvious.
You click a button and it does the job.
No decoding.
No chess.
If that’s not what your UI\UX design feels like today, a redesign won’t save you. A reckoning will.
Redesigns fix visual inconsistency. Audits fix functional drift. Over time products collect:
Legacy features no one wants to own
Settings that point to backends you no longer support
Microcopy from three roadmaps ago
Guard-rail modals and tooltips added just in case
It’s not broken - it’s bloated. And bloat is a tax on every click.
Imagine explaining your product to someone you like over a cup of tea. No jargon. No slides. Just the path:
Land → Learn → Try → Value → Convert.
If you can’t say it simply, the interface can’t say it either.
Goal: remove hesitation, surface outcomes, align words with what the product truly does today.
Map the one path
Write the core journey in one line. Anything that doesn’t help that journey either moves down or moves out.
Delete the ghosts
If a screen has <2 percent usage, no clear owner, or hasn’t changed in 12 months - demote it or remove it.
Two-sentence nav rule
If you can’t explain a nav item in two sentences, rename or regroup until you can.
Outcome-first CTAs
Swap vague actions for clear wins: Create report → See your cost breakdown.
No dead ends
Every screen must offer the next confident step. Inline guidance over popups.
Proof at the decision
Place a line of proof next to the action - tiny stat, logo, benchmark. Not miles away on a testimonials page.
Delete to clarity
If a tooltip explains a basic control, fix the control, then delete the tooltip.
Ship three changes today. Measure next week. Keep going.
Score 0 to 5. Anything under 3 needs love.
Do I know where to click next after two seconds on the page
Can I describe this screen in one line without sighing
Does the primary action shout without yelling - clear but not aggressive
Would I feel safe clicking this button given the words around it
Is anything here clearly for the business not the user
Does this reflect the company we are now - pricing, packaging, ICP
If three or more areas are 2 or below, run a focused audit before you even whisper the word redesign.
Day 1 - Reality check
Top drop-offs, five biggest FAQs, three most painful support threads.
Day 2 - Screen inventory
List nav items, key pages, modals, settings. Add owner and last updated.
Day 3 - Quiet removals
Hide or demote anything unused, legacy or duplicate. No ceremony.
Day 4 - Rename for humans
Titles and labels that match how customers speak today - not how the org chart reads.
Day 5 - Conversion clean-up
Outcome-first CTAs, helpful empty states, proof near decisions.
Day 6 - Sanity checks
Three recorded sessions or five quick calls. Note confusion. Fix once.
Day 7 - Ship and track
Measure activation, task time on the top three flows, tickets per 1000 users.
Cut the top nav to five items max. Group the rest under names people actually use.
Make the first in-product headline match your website promise word for word.
Remove settings that don’t map to a live capability. Archive the rest.
Trim forms to what changes the outcome. Everything else can wait.
Empty states should teach and move: what this is, why it matters, one action.
Buttons must show state: Generate report → Generating... → View report.
CTA formula
Do X → Get Y outcome.
Connect data → See your churn risk now.
Feature card
Outcome line + one-sentence proof.
Spot silent churn before it happens. Used by teams cutting 18 percent churn in 90 days.
Empty state
What this is, why it matters, one action.
You haven’t created a cohort. Cohorts track changes that impact revenue. Create your first cohort.
Tooltip alternative
Label + micro-hint.
Threshold - alerts trigger above this value.
Activation - percent of new users who reach first value within 24 hours
Task success - time to complete the top three actions
Support load - tickets per 1000 users on core flows
Conversion - free to paid or trial to paid and where drop-off happens
Targets, not vibes. Weekly, not once.
Ask the blunt questions:
If we remove this, who hurts - the user, or our comfort
If we rename this, does the anxiety drop
If we rebuild this, will the next five features still fit
A redesign is a risk. A reckoning is relief. Be a little naïve. Ask for the obvious thing. Click the button that does the job. If that’s not your product today, it can be.
If you want a pair of outside eyes, we can sit with your team for a week, cut the noise, and leave you with a cleaner product and a calmer funnel.
2
12
0