I think a lot of growth teams assume comparison starts on pricing pages, competitor pages, or in the sales process.
Usually it starts much earlier.
It starts on the search results page when a user decides which tabs deserve attention.
It starts on the landing page when they ask whether this sounds like the same problem they have in their own words.
It starts in onboarding when they decide whether this workflow feels simpler than the workaround they already trust.
It starts in lifecycle when they decide whether coming back here is more useful than falling back to habit, memory, or another tool.
The user is always comparing something.
The problem is that teams often leave the first comparison set unshaped.
So the user makes one up.
They compare the wrong feature to the wrong alternative.
They compare your setup cost to their old muscle memory instead of to the future payoff.
They compare a collaborative workflow to a solo shortcut because nobody framed when the extra coordination is worth it.
They compare the product to a fantasy version of a competitor or to the best five minutes they ever had with a spreadsheet.
None of that is irrational.
It is just what people do when the product does not help them build a sane evaluation frame.
Most users are not choosing between brands alone
This is one reason I keep coming back to Jobs to Be Done.
People are not only choosing between products. They are choosing between ways of making progress.
The real comparison set is often wider and weirder than the team expects.
Your product is not only up against direct competitors.
It is up against waiting.
It is up against asking a coworker for help.
It is up against doing the task manually one more time.
It is up against copying last quarter’s deck and pretending it is fine.
It is up against a notebook, a spreadsheet, a browser bookmark, or the path of least resistance that already lives in someone’s body.
That is why I think a lot of growth analysis gets too narrow too quickly.
We ask why the user did not choose us as if the decision was made inside our category page.
Sometimes the user did not reject the product.
They rejected the comparison we accidentally invited.
The first bracket changes the rest of the journey
In sports, the bracket matters because it shapes the path before the game even starts.
In retail, shelf adjacency matters because it shapes what feels comparable in the aisle.
In curriculum design, the first reading list matters because it shapes what the learner thinks belongs in the same conversation.
Products work like that too.
The first set of alternatives a user holds in their head becomes the frame for everything that follows.
If that bracket is sloppy, a lot of downstream growth work becomes cleanup.
Acquisition brings in visitors with the wrong expectation of what kind of solution this is.
Onboarding tries to rescue a mental model that should have been shaped before signup.
Lifecycle has to keep re-explaining value because the original comparison never got resolved cleanly.
Sales ends up answering phantom objections that came from a bad bracket, not from the product itself.
I think this is one reason information scent matters so much in growth work.
Raluca Budiu describes how people decide where to go next based on the cues they get and the value they expect to find there.
That is not only a navigation problem.
It is an evaluation problem.
A vague headline, a generic CTA, or a category label with weak scent does not just lower clickthrough.
It encourages the user to compare your product with whatever alternative is easiest to imagine.
That is rarely the comparison you want.
Too many options can still produce thin evaluation
I also think teams confuse more comparison with better comparison.
Give the user every feature.
Give them every plan.
Give them every use case.
Give them every template.
Give them every path through the product on the first visit.
That can look thorough from the inside.
From the outside it often feels like standing in a grocery aisle with twenty versions of the same cereal and no clue which difference actually matters.
That is why Barry Schwartz on the paradox of choice still holds up for me.
More options do not always create more confidence.
Sometimes they create more self-doubt, more second guessing, and weaker commitment after the decision.
I think a lot of growth surfaces suffer from that exact problem.
They do not fail because the value is absent.
They fail because the user is being asked to build the comparison logic themselves while also learning the product.
That is too much work for an early session.
Good growth work narrows the comparison without faking certainty
I do not mean the team should manipulate the user or pretend there are no alternatives.
I mean the product should help the user compare the right things at the right level of detail.
That often means making the first bracket smaller and more honest.
Not every feature deserves to be part of the opening argument.
Not every segment needs the same alternative set.
Not every page should invite the same evaluation mode.
A search visitor who wants a quick answer may need help comparing speed and fit.
A buyer in active evaluation may need help comparing workflow shape and switching cost.
A returning user may need help comparing the value of coming back today against the effort of restarting later.
Those are different jobs.
They deserve different brackets.
When teams skip that work, they often end up overexplaining.
The page becomes a brochure.
The onboarding becomes a museum with no docent.
The lifecycle message becomes a reminder that revives none of the original decision logic.
The artifact I like is a comparison starter
When a team has healthy traffic and plausible demand but the journey still feels oddly mushy, I would write a comparison starter.
Not a giant competitor matrix.
Not a sales deck wearing a product costume.
Just a small artifact that forces the team to say what comparison the user is likely making first, and whether the experience is helping with it.
Comparison starter
- Entry point or trigger
- The alternative the user is most likely comparing against in that moment
- What dimension of the choice matters most right now
- What dimension does not need to be introduced yet
- The sentence, screen, or cue that should narrow the bracket
- What misleading comparison the product is accidentally inviting
- What proof would make the right comparison feel more believable
- Where the comparison should deepen later in the journey
- Evidence
- Owner
That is enough to make a lot of fuzzy debates sharper.
It helps acquisition teams stop writing headlines that attract one job and route into another.
It helps onboarding teams decide which distinctions are worth teaching early and which ones should wait.
It helps lifecycle teams send messages that reopen a real decision instead of replaying brand wallpaper.
It helps product teams notice when the user is benchmarking against a workaround, not a rival logo.
What this changes in practice
Once the comparison is made visible, a few useful things usually happen.
You get more precise about what the page or flow is actually trying to disqualify.
You stop treating every alternative as equally relevant in the same moment.
You become less impressed by copy that sounds complete but does not actually narrow the decision.
You start looking for proof that belongs to the right bracket.
Maybe that proof is speed.
Maybe it is reversibility.
Maybe it is a saved hour next week.
Maybe it is the feeling that the team workflow will be cleaner, not just more feature rich.
You also get a healthier view of objections.
Some objections are real product weaknesses.
Some are artifacts of a comparison frame the product should have cleaned up earlier.
That distinction matters.
If the user is evaluating the wrong tradeoff, better nurture copy is not going to save you for long.
The point
I think a lot of growth work is really about helping people compare with better judgment.
Not more aggressively.
Not more theatrically.
Just more clearly.
The product should help the user understand what kind of choice this is before asking them to make too much of it.
When that happens, acquisition gets cleaner, onboarding gets calmer, and retention has less confusion to unwind later.
The user still has to choose.
They just do not have to invent the whole bracket alone.
