The paradox of the active user: why your visitors will never read your instructions

A visitor lands on your page. They skip the intro paragraph, jump past the "How it works" section, ignore the three-step tutorial you carefully wrote, and click the most prominent button — often before having all the information needed to use it well. The copywriter's instinct is to read this as a clarity problem: explain better, add a diagram, lengthen the FAQ. But human-computer interaction research has documented this behavior for nearly forty years, and the conclusion is almost the opposite: the more explanation you add before the action, the less of it gets read — not because of inattention, but because of a predictable human behavior that has a name.

Where the paradox of the active user comes from

In 1987, researchers John M. Carroll and Mary Beth Rosson published a chapter that remains a reference in software ergonomics, "Paradox of the Active User", in the edited volume Interfacing Thought: Cognitive Aspects of Human-Computer Interaction (MIT Press). Their observation, made in lab studies of software users, fits in one sentence: people want to produce a result, not learn a tool — and that very motivation to act quickly is exactly what stops them from pausing to read a manual, even when that reading would save them time later. The paradox isn't that users are lazy or inattentive: it's that learning and producing compete for the same immediate resource — time and attention — and producing almost always wins.

The production paradox: the result outranks the method

Carroll and Rosson isolate a first mechanism, the production paradox: a visitor motivated by a concrete goal (trying a tool, getting a quote, downloading a guide) draws immediate satisfaction from progressing toward that goal, and this satisfaction actively discourages the pause needed to learn how the system works. Applied to a landing page, this means a block of text placed between the visitor and their goal — however well written — reads as an obstacle to clear rather than help to consult. A three-step "How it works" section, if placed before the main CTA, isn't read as instructions: it's simply skipped, the same way you skip a book's foreword to get to chapter one.

The assimilation paradox: your visitors interpret your page through what they already know

The second mechanism, the assimilation paradox, matters even more for a landing page. Because they don't read your explanations, a visitor doesn't discover your interface from scratch: they interpret it through habits picked up on other sites, other forms, other buttons. This assimilation works in your favor when your page resembles what the visitor already knows closely enough — that's exactly the principle behind Jakob's Law, which holds that a visitor carries their expectations from one site to the next. It works against you the moment your page departs from convention without signaling it: a button that looks like plain text, a menu that leads nowhere, a form field whose expected format is buried in a small explanatory note nobody will read. The visitor won't correct their interpretation by reading your explanation — they'll assimilate your page to a more familiar pattern, even if it's the wrong one, and leave if the gap grows too wide.

What the research shows about minimal instruction

The same research team tested the practical consequence of this finding. In a 1987 study published in Human-Computer Interaction, "The Minimal Manual", Carroll and his co-authors (Smith-Kerker, Ford, and Mazur-Rimetz) compare novice users learning word-processing software either with a classic exhaustive manual or with a reduced guide covering only what's needed to get started, organized around real tasks rather than features. Users given the minimal manual completed their tasks faster, succeeded more often, and scored better on a later comprehension test — while a notable share of the "full manual" group's time was spent recovering from errors that the shorter version simply avoided by never opening the path that led to them. The lesson isn't about length as such: it's that support organized around what the user is trying to do beats support organized around everything the system can do — exactly the difference between a landing page structured around the promised outcome and one structured around a feature list.

Classic mistakes on a landing page that assumes people will read it

• A "How it works" section placed before the main CTA — useful as a supplement, costly as a gate: it should inform a visitor who's already hesitating, not condition access to the action button.
• A forced tutorial or guided tour on first load, before the visitor has had a chance to see the product or offer for themselves — the production paradox predicts exactly this drop-off point.
• Hidden format instructions in small print under a form field ("use DD/MM/YYYY format") instead of a field that accepts any reasonable format, or a visible example inside the placeholder itself.
• An FAQ answering questions asked too late — if three questions in the FAQ re-explain what the offer even is, that's a sign the top of the page doesn't stand on its own, and no visitor scrolls down to the FAQ to fill that gap.
• A button label that doesn't say what it produces — "Continue," "Next," or "Submit" require having read what came before to make sense, whereas a label describing the outcome ("Get my quote," "See the demo") is self-explanatory without context, as covered in our guide to CTAs that convert.

Working with assimilation instead of fighting it

Since the visitor is going to interpret your page through what they already know regardless, the most reliable strategy is to make that assimilation accurate rather than correct it afterward with explanatory text.

• Keep standard visual conventions — a button that looks like a button (solid color, clear border, pointer cursor), not a plain underlined line of text that blends in with other links.
• Structure the form in the order people expect — name before email, email before phone — so the visitor fills it in on autopilot instead of needing to read an unusual order.
• Reserve navigation for patterns already seen elsewhere — anchor links to sections on the page rather than a menu mimicking a multi-tab marketing site, a common source of incorrect assimilation on a page built for a single action.
• Name things the way the visitor already names them — reuse the vocabulary of the industry or the search query that brought the visitor to the page, rather than internal jargon that would force them to learn a new lexicon before understanding the offer.

When you still need to explain

The paradox of the active user isn't an argument for removing all explanation: it tells you where to put it and in what form. A genuinely new or technical product — a developer tool with its own syntax, a B2B SaaS demo that assumes an integration — needs a minimum of context for the visitor to know what they're looking at. The minimal-manual lesson applies literally here: that context should be organized around the task the visitor is trying to accomplish ("how to connect my CRM," not "all our integration features"), stay as close as possible to the relevant field or button rather than grouped in a separate block, and remain optional for anyone who doesn't need it — a "see an example" link or a tooltip, never a mandatory step before reaching the rest of the page.

LanderKit templates ($59 each, $149 for the full bundle) are built so that much of this clarity comes from the structure itself — instantly recognizable CTAs, conventionally ordered forms — before adding a single word of explanation. It's especially visible on saas-waitlist, where the whole point is that a hurried visitor understands the offer and signs up without needing to scroll through any instructions.