Long tasks must be breakable and savable
Aliases: segmented save · resume later · attention lapse recovery
What it is
Attention leaves mid-flow: a call, a task switch, a fatigue spike. If a long process can only be finished in one sitting, an attention disability is not slowness—it is impossibility. Save progress in long tasks requires that the flow can stop at a meaningful boundary, that finished work is kept, and that return picks up where it stopped rather than emptying the form.
The object of control is whether the work still exists after an attention lapse. It is not “one question per screen to match cognitive load,” and it is not “facts from the last page must be visible on this one.” Those are different adaptations. The failure here looks like: sixty percent done, session dies or the person walks away, return shows a blank form.
Why it happens
Attention lapses are expected events, not surprises. Unsaved progress translates a lapse into total loss; the restart cost talks people out of trying again. Segmentation supplies a legal place to leave: a completed step is written down, and attention can go elsewhere between steps.
Save has to happen even when the user never presses Save. Demanding an extra “remember to save” stacks prospective memory on attention that is already unstable. If a session timeout wipes the draft, a time limit and this adaptation undo each other: the clock stops, and so does the work. The resume entry also has to be findable, or the save exists only on the server.
Studying it
Force an interruption at halfway (switch apps, close the tab, wait out a near-timeout) and measure whether people return to the same step with the same data. Compare per-step autosave against write-on-submit-only.
Independent variables: save grain (per field / per step / submit only), whether timeout destroys the draft, whether resume is visible on the return path. Dependent variables: rate of return to the original step, number of fields re-typed, abandonment attributed to lost progress.
When recruiting people with attention disabilities, the interruption should be imposed by the tester; do not wait for them to “naturally wander” to produce the datum.
Where it stops holding
A one-screen action that takes a minute does not need a wizard plus a draft. The rare legal signing that must happen in one sitting can still demand continuity, but already-filled fields should survive an interruption. Drafts that hold sensitive data need expiry; expiry must be announced and warned before it happens, not a silent delete people still believe is there. Cross-device resume needs account-side storage; signed-out users at least need in-session persistence.
Applying it
- Autosave a draft at the end of every step. Do not rely on a Save draft button that is easy to forget.
- On return, put Continue last time on the original entry point and land on the step they left, not the home screen.
- Warn before session timeout; keep the draft after timeout unless the user explicitly discards it.
- Verify: fill to about sixty percent, close the tab, come back through the same entry—step and data must still be there. Then force a session timeout and confirm the draft was not wiped. Any Back that erases filled fields also fails.