I think a lot of growth teams are still a little too afraid of clarity.
We say we want qualified traffic.
We say we want better activation.
We say we want healthier retention.
Then we publish landing pages, onboarding copy, and lifecycle prompts that try very hard not to scare anyone away.
The promise stays broad.
The tradeoffs stay fuzzy.
The real user stays implied.
The hard parts stay hidden until later.
It can work for a click.
It often works badly for a customer.
I have become more interested in the opposite move.
Help the wrong user rule you out early.
Not rudely.
Not with some smug anti growth posture.
Just honestly.
The right kind of clarity does not only reduce wasted signups.
It also helps the right user trust you faster.
Good growth work does not only persuade
It also helps people self select.
That sounds obvious, but a lot of product funnels are still built like a street vendor calling everyone over to the table.
The better analogy is usually something quieter.
A good trailhead sign tells you what kind of hike this is before you are two miles in.
A good museum placard gives you enough context to know whether this room is worth your time.
A good restaurant menu signals whether you are in the mood for the place before you order the wrong thing and feel vaguely annoyed for the next hour.
Products should do the same.
The user should not need a full week of setup, a half watched demo, and three lifecycle emails to learn the basic truth of whether the product fits their job, timing, or appetite.
I like the GOV.UK pattern on checking whether a service is suitable because it is refreshingly direct. Help users work out whether they can or should use the thing. Save them time. Reduce confusion. Point them elsewhere when needed.
That sounds like service design language.
I think it is also growth language.
A lot of shallow conversion is just delayed mismatch
This shows up all over the place.
SEO content that earns the click but not the fit.
Product pages that describe outcomes without naming the effort required.
Free trials that attract curiosity from people who do not actually have the right problem.
Onboarding flows that treat every user as equally ready for the same commitment.
Sales assisted journeys that create hope without surfacing the operational reality soon enough.
In all of those cases, the team can point to motion.
Traffic rose.
Signup rate improved.
Demo requests looked healthy.
The first session count went up.
Then the downstream picture gets muddy.
Activation feels soft.
Support questions arrive from people who expected a different thing.
Lifecycle channels work harder than they should.
Retention never catches up to the top of the funnel story.
I do not think every one of those problems comes from bad targeting.
Sometimes it comes from a timid product narrative.
The team wanted to be inviting, so it became vague.
It wanted to be persuasive, so it hid the effort.
It wanted to avoid friction, so it postponed the truth.
That is not always kindness.
Sometimes it is just deferring disappointment.
The right user usually likes honest edges
This is the part people forget.
Clear fit language does not only filter people out.
It also helps the right person recognize themselves.
Jakob Nielsen’s usability heuristics still hold up here, especially match with the real world, visibility of system status, and user control and freedom. If the product explains itself in the user’s terms, makes the state legible, and lets people back out without drama, trust rises.
I think that applies before signup too.
The right user wants to know
- who this is really for
- what job it is especially good at
- what kind of effort is required
- what it will not do well
- what conditions make it more likely to work
That is not a conversion tax.
That is part of the product.
A climbing gym grade card is useful because it helps you choose a wall you can actually climb.
A great shopkeeper is useful because they stop you from buying the wrong tool for the job.
An experienced editor is useful because they tell you which story is not ready yet.
Good growth product work can do the same kind of sorting.
Not every interested visitor should become an activated user.
Some should leave with a cleaner understanding that the product is not for them right now.
That is a better outcome than a low quality signup that burns support time, muddies the funnel, and leaves the person feeling faintly tricked.
I think this matters most in the jump between acquisition and onboarding
That handoff carries a lot of hidden risk.
Acquisition language tends to emphasize possibility.
Onboarding is where the product starts charging for reality.
Maybe the user needs teammates before the value really unlocks.
Maybe the workflow works best for a more repeatable use case than the copy suggested.
Maybe the product is excellent for one kind of urgency and mediocre for another.
Maybe the setup burden is fine for a manager with an ongoing need and terrible for someone solving a one time problem.
If the page before signup does not prepare the user for that reality, the onboarding flow inherits an expectation gap.
That is one reason I like the GOV.UK guidance on starting to use a service. It emphasizes giving people enough context before they begin, including what the service does, whether it meets their need, how long it may take, and what they will need.
Again, that is not only public service design.
It is a practical growth lesson.
You do not build trust by making the entry feel effortless if the truth gets expensive five minutes later.
The artifact I like is a fit note
When a team keeps attracting people who click, sign up, or book time but do not become healthy users, I would write a fit note.
This is not a giant positioning deck.
It is not a full messaging framework.
It is a small working artifact for one useful question.
What truth should the user know early enough to make a better choice.
Fit note
- The segment you most want to help
- The job they are trying to get done
- The signs this product is a strong fit
- The signs this product is a weak fit
- What effort, setup, or behavior the product requires
- What the user should reasonably expect in the first session
- What outcome should happen soon if the fit is real
- What alternative path or advice helps the wrong user leave smarter
- Evidence from research, support, sales, or behavior
- Owner
That is enough.
The point is not to write harsher copy.
The point is to make the fit legible.
Once that happens, a lot of decisions get easier.
The landing page can stop pretending every visitor needs the same pitch.
The signup flow can route people more honestly.
The onboarding can stop over explaining to the wrong segment and under preparing the right one.
Support can see where expectation debt is being created.
Lifecycle can stop trying to re persuade users who never really had a clean fit in the first place.
This can improve metrics the team actually cares about
I know this argument can sound suspiciously noble.
Tell the truth.
Reduce ambiguity.
Let some people opt out.
Very principled.
Also very practical.
When the right people self select faster, a few useful things tend to happen.
Activation gets easier to interpret because fewer users are arriving under false assumptions.
Retention gets cleaner because the product is serving people who actually have the repeat problem it is built for.
Support gets less clogged with preventable confusion.
Acquisition quality improves because the team can see which channels are sending users with real fit instead of only surface level curiosity.
Experimentation improves because each test is less contaminated by mismatch at the starting line.
I think of this as expectation hygiene.
It is less glamorous than a flashy conversion lift.
It is often more durable.
The hard part is emotional, not analytical
Most teams can name the weak fit cases if you ask them directly.
They know which use cases churn fast.
They know which leads ask for things the product is not built to do.
They know which user stories look exciting in a deck and ugly in retained behavior.
The harder part is saying that truth plainly in the user journey.
That can feel like leaving money on the table.
Sometimes it is.
Usually it is leaving bad revenue, bad data, or bad product learning on the table.
I would rather lose the wrong signup on the landing page than lose the right lesson three dashboards later.
I would rather narrow the promise than let onboarding absorb all the blame for a mismatch it did not create.
I would rather help a user say not now than trick them into a week of low confidence progress.
That is not anti growth.
That is product judgment.
What I would do in practice
I would start with one acquisition path that matters commercially.
Maybe a high intent SEO page.
Maybe the main homepage to trial flow.
Maybe a sales assisted demo request path that converts well but activates poorly.
Then I would ask a few blunt questions.
- Which users succeed here later
- Which users predictably stall
- What truth did the successful users understand early
- What truth did the stalled users discover too late
- Where in the journey could that truth be made clearer
Then I would update the path with more honest cues.
Name the user more specifically.
Name the use case more concretely.
Name the effort more candidly.
Name the bad fit more respectfully.
Name the first believable outcome more clearly.
That is usually enough to learn something important.
Not because the copy got clever.
Because the product finally stopped being coy.
The point
I think a lot of growth teams have been taught to treat disqualification as failure.
Sometimes it is the beginning of better product truth.
When the wrong user can rule you out early, the right user can lean in with better context, better trust, and better odds of actually getting value.
That seems like a healthier bargain for everyone involved.
