Case studyCraft conventionIntermediate

One Long Form or Several Short Steps

Splitting a long form into steps did not raise completion until the team also saved progress and let people come back.

Definition

A decision case about form structure: why the first split failed, what the second attempt changed, and what the evidence actually supported.

Craft convention. True because the industry converged on it. Breaking it costs familiarity, not correctness.

A composite scenario assembled from situations that recur across teams. It is written to teach reasoning rather than to report on a named company, and outcomes are stated directionally rather than as invented measurements.

Problem

A twenty-eight field quote form had low completion. The team split it into six steps and completion did not improve.

Context

An insurance quote form requiring vehicle details, driver history and cover preferences. Many users needed to look up information such as policy numbers partway through.

Constraints

Regulatory requirements fixed a number of the questions and their wording.
A quote could not be produced without the full set of answers.
The underwriting system required the answers in a specific structure.

Decision

Keep the six steps, and add automatic progress saving, a resume link sent by email, a visible step count with named steps, and a review step before submission.

Rationale

The original diagnosis was wrong. The problem was not that the form looked long; it was that users had to leave to find information and lost everything when they did. Splitting it into steps addressed perceived length and left the actual cause untouched. Once progress persisted, the split became genuinely useful because each step was a natural save point.

Evidence used

Drop-off by field, which clustered on the questions requiring an external lookup.
Session data showing users leaving and returning to the start rather than continuing.
Usability sessions in which participants left the room to find a document.
Comparison of completion before and after each change, so the effect of saving progress could be isolated.

Trade-offs accepted

Saving partial data before submission raised data retention questions requiring legal input.
Resume links by email introduced a security consideration around link expiry.
The review step added a screen to the flow for users who had no problem completing it.

Outcome

Completion improved once progress was saved, and improved further with the resume email. The step split contributed, but only in combination with persistence. The review step reduced correction calls after submission.

Alternatives considered

Return to a single page

Why not: It would have removed the natural save points and made the form feel longer without addressing the lookup problem.

Reduce the number of questions

Why not: Attempted first. Most were regulatory or required for underwriting. Three were removed, which helped marginally.

Ask the lookup questions last

Why not: Helps a little, but the user still has to leave. Persistence solves it regardless of ordering.

Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.

Applies when you are designing

A Checkout A Form

Concepts behind this decision

What the reasoning in this case rests on.