I think a lot of growth teams misread why a new user showed up in the first place.
We say they were motivated.
Sometimes that is true.
Sometimes they were hurried.
Sometimes they were cornered.
Sometimes they were sent.
A manager told them to set the thing up.
A teammate dropped a link in Slack.
A deadline made the old workflow intolerable.
A Google search found the one page that sounded close enough to the problem at hand.
The user arrived with energy, but the energy did not necessarily belong to the product.
It was borrowed.
That distinction matters more than a lot of onboarding plans admit.
Borrowed motivation is useful. It creates motion. It gets someone into the room.
But it is also unstable.
If the product cannot turn that outside push into a felt sense of ownership, clarity, and progress, the user often disappears right after the forcing function fades.
That is one reason I keep coming back to Self Determination Theory. The language is academic, but the operating idea is practical. People sustain behavior more reliably when the experience supports autonomy, competence, and relatedness, not just compliance.
Growth teams do not need to become psychologists to use that idea well.
They just need to stop treating arrival as proof of commitment.
A lot of acquisition runs on motivation the product did not earn
This shows up everywhere.
Search traffic is often urgency in disguise.
Referral traffic is often trust on loan from another person.
Sales assisted onboarding is often a mix of hope, obligation, and organizational momentum.
Lifecycle reactivation can be powered by guilt, curiosity, or a fresh deadline more than fresh love for the product.
The user still matters. The intent is still real.
But the motivational source is mixed.
I think that is where teams get sloppy.
They see the click, the signup, or the booked demo and start designing as if the user has already decided to build a habit.
Usually they have not.
They have agreed to one more step.
That is a much smaller commitment.
The Fogg Behavior Model is helpful here because it strips away some of the romance. Behavior happens when motivation, ability, and a prompt converge. If a user takes an action, that does not prove motivation was deep. It may just mean the prompt was timely and the action was easy enough in that moment.
A lot of growth product mistakes come from confusing that momentary convergence with durable intent.
The handoff moment is where the real work begins
I think of this a little like a relay race and a little like physical therapy.
In a relay, a fast start matters less if the baton exchange is clumsy.
In physical therapy, borrowed motivation can get someone to the first session. Pain, fear, or doctor advice gets them in the door. But durable progress usually starts when the patient feels the exercise working and begins to believe, on their own, that the routine is worth continuing.
Products have the same handoff problem.
External pressure gets the user to show up.
The product then has a short window to transfer the reason for continuing.
That transfer usually depends on a few questions.
Did the user get to make a meaningful choice.
Did they feel more capable, not just more processed.
Did the product help them connect the work to a real outcome they care about.
Did anything in the experience make the next return feel socially or personally grounded.
If the answer is no, the product has effectively rented the user for a session without earning the next one.
This is why overbuilt onboarding can underperform
I do not think most onboarding friction is caused by a single bad screen.
More often the problem is that the product spends borrowed motivation too carelessly.
It asks for setup work before showing progress.
It explains every option before the user has a reason to care.
It routes everyone through the same ceremony even when the incoming motivation is obviously different.
That is why I still like NN group on progressive disclosure. Show the important thing first. Defer complexity until the user has enough context to want it.
That is a usability principle, but I think it is also a growth principle.
Every extra requirement in the first session is drawing down from a limited motivational balance.
When teams forget that, they start designing as if every user arrived fully convinced and fully patient.
Very few did.
Some users are not buying the whole product yet
They are buying a narrower hope.
Maybe the hope is
- get my boss off my back
- finish this task before the meeting
- recover a broken workflow
- see whether this tool can do the annoying part for me
- avoid making the same mistake again
That hope is not a weakness. It is useful signal.
It tells you what kind of proof the product has to provide first.
A museum does not hand you the entire archive when you walk in. It gives you an entrance, a path, and enough context to care about the next room.
A good climbing gym does not start a beginner on the most complex route. It gives them an achievable wall that teaches trust in the holds.
A good shopkeeper does not force you to understand the whole store before helping you find the one shelf you came for.
I think growth product work has the same obligation.
Meet the user at the size of commitment they actually brought.
Then earn the next layer.
The artifact I like is a motivation transfer map
When a team is arguing about activation, onboarding, or early retention and the conversation keeps collapsing into generic funnel talk, I would write a motivation transfer map.
It is a small working artifact.
Not a strategy deck.
Not a giant lifecycle canvas.
Just a way to make the motivational handoff visible.
Motivation transfer map
- Entry source or trigger
- What pressure, promise, or person created the initial motion
- What the user hopes to get done in this session
- The first moment where outside motivation should become self owned progress
- What proof of competence the product must deliver before asking for more work
- What choice gives the user a sense of agency
- What reminder, teammate cue, or saved state supports return
- Where extra setup can be deferred
- Evidence
- Owner
That is enough to make better decisions.
The point is not to label every user perfectly.
The point is to force the team to ask a better question.
Are we designing for a committed user, or are we designing for a user whose commitment is still being negotiated.
Those are not the same job.
What this changes in practice
Once you make the borrowed motivation visible, a few useful changes tend to follow.
You stop asking every segment to prove seriousness in the same way.
You get more careful about what has to happen before the first meaningful result.
You write lifecycle messages that help renew the user’s own reason for continuing instead of only replaying the company pitch.
You become less impressed by shallow conversion lifts that came from stronger prompts but weaker ownership.
You look harder at whether the first session created confidence or only movement.
That last distinction matters a lot.
Movement is easy to overcount.
Confidence is harder to fake.
Good growth teams do a kind of motivational accounting
That phrase sounds colder than I mean it to.
What I really mean is that thoughtful teams notice where momentum came from, how fast it decays, and what the product has to do before the balance runs out.
A search click has one kind of half life.
A manager mandate has another.
A recommendation from a trusted teammate has another.
An urgent problem at work can create a burst of tolerance that vanishes as soon as the fire drill ends.
If you know which fuel brought the user in, you can design a more honest first session.
You can decide what to simplify.
You can decide what proof to front load.
You can decide what social cue or saved context needs to survive into the second session.
That feels like richer product judgment to me than another debate about whether the signup button should be green.
The deeper point
I do not think growth product is only about creating motion.
A lot of bad growth work creates motion.
The craft is in converting temporary energy into durable belief.
That means seeing the difference between a user who arrived because they had to and a user who returned because they wanted to.
Most products need help with that handoff.
The good ones treat it as design work, systems work, and writing work all at once.
That mix is part of why I like this corner of product so much.
You are not only tuning a funnel.
You are helping motivation change ownership without dropping it on the floor.
