A conceptual model should be presented before feature detail, establishing the framework before filling in operations

What it is

Onboarding flows, help documentation, and feature tutorials are commonly organized around walking through steps in operational order. An alternative is to first spend a short passage laying out the system's core concepts and how they relate, before getting into specific operations — and this ordering choice matters on its own: presenting the framework first (advance organizer) gives every specific operation covered afterward a place to attach to, rather than leaving each one as an isolated rule that has to be memorized on its own.

Why it happens

Learning a series of operations with no framework means each one can only be rote-memorized as an isolated fact — click here for this, that button does that — with no connections between items, held together purely by repeated practice. With a framework in place, the same piece of operational instruction is no longer isolated information; it becomes a concrete instance of some relationship the framework already describes. Once a user understands the framework, encountering a new operational detail lets them slot it into a position the framework already has room for — assimilation replacing rote memorization — which noticeably lowers the memory burden and makes it easier to derive operations that were never directly taught.

This effect depends on the framework actually arriving before the details. If the framework shows up at the same time as the details, or after them, the user has no structure to attach details to when first encountering them; by the time the framework finally arrives, the details already memorized piecemeal have to be reorganized into it — and that extra reorganizing work adds a burden that cancels out the benefit the framework was supposed to provide.

Studying it

This corresponds to the advance organizer paradigm in educational psychology: give learners a short, general framework statement before the main learning material, and compare outcomes for groups with and without that advance organizer when they go on to learn the specific content.

Common independent variables: whether an advance organizer is provided, and its timing relative to the details (before / after / simultaneous). Common dependent variables: retention of the specific content, transfer performance to novel situations (whether the framework lets someone derive an untaught operation).

Transplanted into interface research, this paradigm is often used to evaluate the structure of onboarding design — testing "concept overview first, then feature walkthrough" against "jump straight into feature teaching," and comparing users' subsequent success rate on a task that was never directly taught.

Methodology note: the classic educational-psychology studies behind this effect targeted relatively complex, structured learning material. A lot of onboarding content in interfaces is structurally simple, without much of a relationship worth turning into a framework — applying the paradigm directly in those cases will tend to produce a small, indistinct effect size. Before evaluating, first judge whether the current product actually has structure worth explaining.

Where it stops holding

• Framework-first only pays off when the system genuinely has an internally coherent framework that actually explains the details that follow. Forcing a summary framework that doesn't actually match the real details leaves the user approaching subsequent content with a wrong expectation — worse than providing no framework at all.
• For users who have already picked up an equivalent framework through another channel (experience with comparable products, word of mouth), restating the framework has limited benefit and can cause unnecessary delay; the onboarding flow should let these users skip it.
• If the system itself has only a handful of unrelated feature points with no real structure, there's nothing for a framework to explain — in that case, going straight through operations in order is more direct and less effortful.

Applying it

• Open onboarding flows and help documentation with as short a passage as possible stating what the system's core concepts are and how they relate, and make sure this passage precedes any specific operational steps, rather than being interspersed among them.
• Check whether this framework passage can actually derive the operational details that follow — after writing it, go through the subsequent feature descriptions one by one and see whether each detail has a corresponding place in the framework. Any detail that doesn't fit signals the framework is incomplete, or that the content doesn't have structure worth framing in the first place.
• How to check: split the onboarding flow into a "framework-first" version and a "straight into operations" version, then test both on a task that was never directly taught in training but that can be derived from the framework, comparing success rate and time between the two groups.

Related

• Same group: A7.10.1 An explicit conceptual diagram is learned more accurately than a model left implicit in interaction · A7.10.2 A persistently visible status display is itself a form of conceptual-model expression · A7.10.4 When a stated conceptual model conflicts with actual interaction behavior, users go by behavior
• Nearby: A7.01 Definition and function of mental models · A7.08 Design model, system image, and user's model
• Search terms: advance organizer · framework-first · schema theory · onboarding structure