The attention crisis is real, but most product teams draw the wrong conclusion from it. Shrinking attention spans don't mean you need louder hooks. They mean you have a smaller window to prove you deserve the attention you got — and that the real scarcity was never attention at all.
Attention is abundant; people notice thousands of things a day. Motivation — the willingness to actually change behavior, to try, to return, to switch — is the scarce resource. A product can win the glance and lose the user in the same minute.
Getting attention: the promise must match a struggle
Products don't earn a first session by being interesting. They earn it by intersecting a moment where someone is struggling to make progress — with a promise specific enough to feel written for that struggle.
The first screen isn't a canvas for cleverness; it's a claim about whose problem this product solves. Get the claim right and you attract users who will stay. Get it wrong and you attract users who were promised something else — who then churn and read as a retention problem when they were really a framing problem.
Keeping attention: progress is what makes people stay
What keeps people isn't engagement mechanics. It's felt progress: evidence, early and often, that they're closer to the outcome they came for. The first sessions should be built around one question — how quickly can this person experience genuine relief on the problem that brought them here?
Example
two first sessions
Before: account setup, a role question, a team-size question, a permissions screen, an interactive tour, an empty dashboard. Value arrives — maybe — tomorrow.
After: "Paste your messiest spreadsheet." Thirty seconds later the user is looking at their own problem, partially solved. Setup happens later, once staying feels worth it.
The first design charges a motivation tax before delivering value. The second delivers value and lets it pay the tax.
Demotivation: the silent growth killer
Users rarely quit because a product lacks features. They quit because something made them feel incapable, graded, lost, or stupid — an error message that blamed them, an AI that overwrote their work, a flow that demanded expertise they didn't have yet.
Demotivated users don't file complaints. They just don't come back. A motivated user forgives rough edges; a demotivated user forgives nothing.
Go deeper: the growth arithmetic
The math for a founding team is blunt. Demotivating users makes growth harder, because you're refilling a leaking bucket with paid acquisition. Motivating users and keeping the product simple makes growth easier, because retention compounds and advocates recruit. Motivation isn't a marketing concern. It's built — or broken — in the interface, and you can see it in your retention curve before it ever shows up in your NPS.
Reducing cognitive load: progressive disclosure as trust strategy
The third job is to stop the product from making people think harder than they have to — and this is where AI products most often sabotage themselves. The instinct is to show everything: every capability, every option, a 3,000-word answer to a simple question. It reads as power to the team and as noise to the user.
Progressive disclosure is the old, unglamorous answer, and it has never mattered more. Show the one or two things that solve the immediate problem. Hide everything else until the user's competence creates demand for it. Let mastery unlock complexity, rather than making complexity the price of entry.
For AI features specifically, progressive disclosure is also how trust gets sequenced. A new user shouldn't meet the most autonomous version of the system first; they should meet the version that gives them a quick, low-stakes win — then graduate, win by win, toward delegation. Each disclosure earns the next.
Try this — the one-screen audit
For any screen in your product, ask: does this ask for attention, or does it build motivation?
- Attention-asks are easy to ship and feel productive: badges, prompts, announcements, tooltips.
- Motivation-builders are harder: faster first relief, cleaner recoveries, visible progress, fewer choices per moment.
The ratio between them predicts your retention curve better than your feature roadmap does.
Attention gets a product tried. Motivation gets it kept. Founding product designers who understand the difference build growth into the interface itself — which is good, because in the AI era, nobody gets attention twice.