Choose against the task constraints
An example brief has company details, a workflow description and launch constraints. Users often adjust the workflow after checking timing. A fourth integration section appears only when an existing system must connect. The worksheet specifies behaviour, not a claim that one layout converts better.
| Condition | Sections on one page | Multi-step form |
|---|---|---|
| Compare workflow and timing | Both sections can stay available | Back/forward must preserve entered values |
| Conditional integration questions | Reveal only applicable questions | Skip the step only when its condition is false |
| Resume a draft | Restore fields and visible sections | Restore both fields and step location |
Start with sections for this cross-checking task. If a tested stepper improves the workflow, retain a final editable review and make backward navigation lossless. Optional sections are not automatically extra mandatory steps.
Conditional does not mean required for everyone
| Draft | Existing integration | Required sections |
|---|---|---|
| D-A | None | Company, workflow, timing |
| D-B | Connect current ERP | Company, workflow, timing, integration |
| D-C | Undecided; request advice | Retain uncertainty for follow-up |
Should D-A be blocked because it has no ERP field mapping?
Show the worked answer
No. It has no integration in the stated scope, so those conditional questions do not apply. D-B needs the relevant integration information; D-C needs follow-up on scope.
Check the chosen interaction
- Backward navigation preserves valid text and selected choices.
- Hidden, inapplicable fields do not generate false errors.
- The final review offers direct access to the section being changed.