Sequential structure forces a fixed order, as in tutorials and wizards

What it is

A sequential structure requires content to unfold in a fixed order: step 3 is unreachable before step 2. Tutorials, wizards, account opening, and checkout are this type. The next hop is neither “child class” nor “related”; it is “after.” An object’s place is its index in the sequence, not its belonging or its associations. People give up the freedom to choose the next hop in exchange for “no skipped step, no wrong order.”

Turning a tutorial into a topic tree, or a settings page into a wizard, is using the wrong structure type: the former needs skippable reading, the latter needs random access.

Why it happens

Some tasks have real preconditions: no address, no shipping method; no consent, no submit. Sequence writes those preconditions as the only path, so working memory need not keep “which step is still missing.” Numbers, progress, and Next replace tree-path place with temporal place: which step am I on, how many remain.

The cost of force is that random entry fails. A deep link into step 4 may find earlier state empty; a search hit on tutorial section 7 finds sections 1–6 not yet built. A sequential structure must either refuse that entry and pull back to a legal start, or fill in preconditions for a mid-sequence arrival. Otherwise “fixed order” is only a surface.

Studying it

Contrast tasks that must preserve order with tasks that should be skippable, to see whether sequence protects or blocks.

• Paradigms: wizard completion, skipped-step rate, drop-off points; locked order versus allowed skipping; recovery from a deep link into the middle.
• Independent variables: whether completed steps can be reviewed, whether skipping is allowed, granularity of progress, whether mid-entry fills preconditions.
• Dependent variables: completion, invalid submits, abandonment because a step could not be found, comprehension tests after mid-sequence entry.
• Methodological note: labs that always start people at step 1 overestimate how friendly sequence is. Real traffic drops into the middle from notices and search. Reviewing a past step is not the same as submitting out of order; test the two permissions separately.

Where it stops holding

Reference manuals, settings, and independently intelligible help articles turned into wizards lock down content that should be randomly reachable. When experts already know the sequence, step-locking is a penalty; offer “see all” or skip. Parallel branches (business customers take another line) are still a sequential variant, not a tree: each branch still has forced before-and-after, there are just several legal sequences. When items are only topically close, with no precondition, do not fake rigor with sequence.

Applying it

• Use sequential structure only when steps have real preconditions, and write those preconditions as checkable state, not merely page numbers.
• Allow review of completed steps; by default do not allow skipping a step whose preconditions are unmet.
• On a deep link into the middle, either fill prior state or send the person to the nearest step that can legally start.
• Verify by walking from step 1, then entering from an external link to step 4. If the latter can submit with preconditions missing, or cannot tell where it is, the sequential structure only holds for people who started at the beginning.

Related

• Within the group: G1.09.1 Hierarchy organizes content by parent–child links and is the usual default · G1.09.2 A matrix locates the same content by several attributes at once · G1.09.3 Hypertext organizes by associative links, not a single hierarchy · G1.09.5 Most systems keep hierarchy as the backbone and add hypertext laterals · G1.09.6 Structure type and organization scheme are independent dimensions · G1.09.7 A matrix demands complete metadata; missing fields block location
• Adjacent: G4.05 Resume from interruption · G4.06 Task chains and recovery · E5.10 Steppers
• Search terms: sequential structure · wizard · forced order