I think a lot of growth work gets flatter than it needs to because teams optimize for the click and stop there.
The ad click.
The search click.
The signup click.
The CTA click inside the app.
The reactivation click in the email.
Those clicks matter.
They are just rarely the whole job.
A click usually means the user is willing to ask the product one more question.
Will this help me solve the problem I came in with.
Will this page answer what I hoped it would answer.
Will this workflow be easier than the old one.
Will this tool make me feel more capable or just more busy.
I think growth product work improves when you treat each click less like a conversion event and more like a handoff into the next useful question.
That sounds small, but it changes a lot.
The click is a question, not a conclusion
One reason I still come back to Jobs to Be Done in Harvard Business Review is that it keeps the user in motion.
People do not show up for pages, tours, and features in the abstract.
They show up with a job under way.
Search is often a question in disguise.
Product evaluation is often a question in disguise.
Early activation is often a question in disguise.
Even retention is often a question in disguise.
Do I still trust this tool enough to keep working here.
That is why I get skeptical when teams celebrate a click as if it means the user is fully persuaded.
Usually it means the user granted you one more turn.
The product still has to earn the next one.
Good products feel a little like good bookstores, museums, and teachers
I like watching how good physical spaces guide curiosity.
A good bookstore does not only help you find the book you came in for. It also helps you notice the shelf you did not know you needed yet.
A good museum does not throw the entire archive at you on the first wall. It gives you enough context to care about the next room.
A good teacher does not end the lesson with a pile of facts. They leave you with the next question that makes the next lesson feel earned.
I think product growth has the same obligation.
The page should not only answer the incoming query. It should set up the adjacent question.
The onboarding flow should not only complete setup. It should make the next useful move obvious.
The product should not only record progress. It should help the user see what they would naturally want to explore, finish, or understand next.
That is part of why Raluca Budiu’s NN group piece on information scent is still useful. Users follow cues that suggest the next step will likely pay off. When the scent gets weak, they stop.
That is not just a navigation idea.
It is a growth idea.
Weak scent is one reason good traffic turns into shallow sessions.
Weak scent is one reason activated users stall after a promising first action.
Weak scent is one reason lifecycle messages get the open but not the return.
A lot of user loss is really a missing next question
Sometimes the product is broken.
Often it is only narratively incomplete.
The user lands on an SEO page and gets an answer, but not a clear sense of what to compare, try, or understand next.
The user finishes a first-run checklist, but not with enough context to know which part of the product matters now.
The user completes a task, but the product does not frame the next layer of value in a way that feels proportionate.
The user returns after a week away and sees a blank state that says nothing useful about where to pick back up.
Those moments do not always look dramatic in analytics.
They often show up as polite underperformance.
Pages with traffic and weak depth.
Trials with movement and soft activation.
Accounts with one good session and no believable continuation.
Lifecycle clicks that bounce into uncertainty.
This is where I find the idea of the adjacent possible helpful. In Steven Johnson’s conversation about that concept, he describes progress as moving one room at a time rather than leaping to the end state all at once.
Products ask users to leap too often.
We ask them to understand the whole model, invite the whole team, configure the whole system, or commit to the whole habit before they have crossed the next believable threshold.
That is not ambition.
A lot of the time it is sequencing failure.
Growth work gets better when the next step feels proportionate
The phrase I keep coming back to is proportionate curiosity.
After each meaningful interaction, what is the next question the user is realistically ready to ask.
Not the question we wish they were ready to ask.
The question they have actually earned.
If someone arrived from search, maybe the next question is whether this approach works in their situation.
If someone just finished one useful workflow, maybe the next question is whether the product can save them time tomorrow too.
If someone invited one teammate, maybe the next question is whether shared usage changes the quality of the work.
If someone came back after a quiet week, maybe the next question is not whether they want advanced automation. Maybe it is whether they can reconstruct context in thirty seconds.
I think the Fogg Behavior Model helps here because it keeps the bar honest. If the next step demands more motivation or more ability than the user currently has, the handoff breaks.
A lot of growth product design is really the craft of making the next question small enough to approach and meaningful enough to matter.
The artifact I like is a next-question map
When a team is doing decent work surface by surface but the whole journey still feels oddly shallow, I would write a next-question map.
Not a giant funnel document.
Not a content calendar pretending to be strategy.
Just a working artifact that keeps the chain of curiosity visible.
Next-question map
- Entry point or triggering moment
- User question at arrival
- What answer or proof we gave first
- The next question that should naturally open up
- The product cue, page cue, or lifecycle cue that should carry them there
- What would make that next step feel too large
- What signal tells us the next question was compelling enough to continue
- Evidence
- Owner
That is enough to sharpen a lot of fuzzy growth debates.
It helps SEO work feel more connected to product education.
It helps onboarding focus on the next meaningful move instead of the full product surface.
It helps lifecycle work sound less like a reminder machine and more like a continuation of the user’s own inquiry.
It also forces a useful discipline.
If the team cannot name the next question, there is a good chance the experience is relying on momentum it did not actually create.
What this changes in practice
You start looking at search landing pages less like endpoints and more like bridges.
You get stricter about whether onboarding screens are teaching the next move or just clearing internal setup tasks.
You become less impressed by clickthrough lifts that do not lead into deeper curiosity or stronger product understanding.
You write lifecycle messages that reconnect the user to the next unfinished question instead of replaying the company pitch.
You notice when a blank state, success state, or dashboard is asking the user to invent their own continuation path from scratch.
That last one matters a lot.
Many users do not churn because they rejected the product outright.
They drift because the product stopped helping them know what to ask next.
The point
I do not think growth product work is only about removing friction or increasing prompts.
Some of the craft is more editorial than that.
It is about arranging the experience so the next useful question appears at the right moment with enough proof and enough clarity to feel worth following.
The click is only part of the story.
What matters is whether the product earns the next question after it.
