Skip to content

opensite-ai/opensite-skills / multi-step-form-design

multi-step-form-design

Verified

Designing forms with multiple steps, progress indicators, conditional logic, and save-and-resume mechanics. The discipline of breaking complex data collection into stages that respect cognitive load while maintaining completion intent. Honest about kitchen-sink-single-page (overwhelms before the user starts), progress-theater (steps without genuine staging), and genuinely-staged (each step earns its own page) patterns. Triggers on multi-step form, multi-page form, form wizard, signup wizard, lead form, application form, intake form, configurator, onboarding form. Also triggers when a long form is converting poorly, when an audience is dropping off mid-form, or when a multi-step form is being scoped for the first time.

references/common-multi-step-form-failures.md

View on GitHub
# Common multi-step form failures

9+ failure patterns with diagnoses and cures. The patterns that surface as "the form did not convert" or "audiences abandon mid-form" or "we cannot tell what is going wrong."

---

## "Form converts at 4 percent; we expected 12 percent."

**The diagnosis.** Likely one of: too long, value of completing not clear, mobile-broken, or the audience-fit is wrong.

**The cure.** Audit the form length (`references/multi-step-decision-criteria.md`); audit the value proposition on the landing page (`landing-page-copy`); test on mobile devices; verify the audience matches the form's purpose.

---

## "Drop-off concentrates at step 3."

**The diagnosis.** Specific-step issue. Audit step 3's field count, sensitivity, and clarity.

**The cure.** Per-step audit. Reduce field count if step 3 has too many; reword sensitive questions; clarify why step 3 is needed; consider whether step 3's content belongs there at all. Detail in `references/drop-off-measurement-and-remediation.md`.

---

## "Mobile completion is half of desktop."

**The diagnosis.** Mobile design issue. The form was designed for desktop and breaks on mobile.

**The cure.** Mobile-first redesign. Touch-friendly inputs, single question per screen on long steps, sliders sized for thumb interaction, progress indicator visible without scroll. Test on actual devices.

---

## "Validation rejects valid inputs."

**The diagnosis.** Validation strictness. Rules are over-specified, rejecting inputs the system can handle.

**The cure.** Audit validation rules (`references/validation-strategy-patterns.md`). Email with plus-signs, international phone formats, non-Latin names should all pass.

---

## "Users abandon at submission."

**The diagnosis.** Final-step anxiety. The CTA is unclear; the user does not know what happens; the final field requires information they did not have.

**The cure.** Clarify the CTA ("Get my PDF" beats "Submit"). Add post-submission preview. Add a confirmation step. Move final-field demands earlier if the user needs time to gather info.

---

## "Save-and-resume is offered but nobody uses it."

**The diagnosis.** Trust communication missing. Users do not save because they distrust persistence.

**The cure.** Trust copy alongside the save option. What is saved, how long, who can access. Detail in `references/save-and-resume-mechanics.md`.

---

## "We added conditional logic; the form feels confusing."

**The diagnosis.** Conditional logic complexity outweighs benefit. Either too many rules or rules that change the user's experience visibly without explanation.

**The cure.** Simplify the conditional logic. Remove rules that do not justify their value. Communicate variability if it remains. Detail in `references/conditional-logic-patterns.md`.

---

## "We split the form into more steps; conversion did not change."

**The diagnosis.** Steps were not coherent. Progress-theater pattern. Splitting fields without grouping them into meaningful units does not produce the multi-step benefit.

**The cure.** Restructure into genuinely-staged steps. Each step should represent a coherent unit of cognitive work. Detail in `references/step-architecture-patterns.md`.

---

## "Progress indicator shifts mid-form."

**The diagnosis.** Conditional logic added or removed steps unexpectedly.

**The cure.** Either fix the indicator to handle conditional steps honestly, or fix the conditional logic to not change step counts visibly. Detail in `references/progress-indicator-patterns.md`.

---

## "We cannot tell where users abandon."

**The diagnosis.** Instrumentation missing. No per-step tracking.

**The cure.** Add per-step tracking before any further changes. Without data, remediation is guesswork. Detail in `references/drop-off-measurement-and-remediation.md` (instrumentation requirement).

---

## "Conversion is fine; lead quality is poor."

**The diagnosis.** The form is converting the wrong audience. Either the audience-fit on the landing page is broad, or the form does not filter for the audience the team needs.

**The cure.** Tighten the audience-fit upstream. The form may need fewer fields (less interrogation) but more qualifying fields (audience-segmentation). Detail in `lead-magnet-design`'s audience-fit qualification.

---

## "Conversion was strong at launch; it has declined 30 percent over a year."

**The diagnosis.** Form decay. Stale references, broken integrations, validation rules that no longer match reality.

**The cure.** Quarterly maintenance audit. Update references, fix broken integrations, refresh validation rules.

---

## "We A/B tested adding a progress indicator; conversion did not change."

**The diagnosis.** Either the form was already short enough that an indicator was not needed, or the indicator was poorly designed (dishonest, hidden, or confusing).

**The cure.** Audit the indicator's design. If the form is genuinely short (3-4 steps), the indicator may not lift conversion much. If the form is longer, the indicator should help; redesign if it is not.

---

## "The form looks great in QA; users complain it is broken."

**The diagnosis.** QA tested with the team's devices and browsers; users have different setups.

**The cure.** Cross-browser, cross-device, cross-network testing. Consider real-world conditions (slow connections, older devices, accessibility tools).

---

## "The form's submit button is gray; we cannot figure out why."

**The diagnosis.** Validation logic is preventing submission but the error is not surfaced. Common cause: a hidden required field or a cross-field validation that fails silently.

**The cure.** Surface all validation errors visibly. Submit button state should follow form state visibly; the user should see why submit is disabled.

---

## "We added save-and-resume; nobody resumes."

**The diagnosis.** Either users save but the recovery link does not arrive, or the resume experience is broken, or the form's value did not persist (the user's interest faded).

**The cure.** Test the recovery email deliverability. Test the resume experience end-to-end. Consider whether save-and-resume is genuinely needed or whether it is decorative.

---

## "Sales says the form-sourced leads are wrong type."

**The diagnosis.** Audience-fit mismatch. The form is converting the wrong segment.

**The cure.** Audit the form's qualifying fields and the landing page that drives traffic. Either tighten the audience filter at the landing page, or add qualifying fields to the form that route based on segment.

---

## "We made the form shorter; submissions went up but lead quality went down."

**The diagnosis.** The fields removed were qualifying fields. Conversion improved because friction dropped; quality dropped because the qualifying signal was lost.

**The cure.** Decide whether quality or quantity matters more. Restore qualifying fields if quality matters; accept the lower quality if volume is the priority. Often the right answer is to restore some fields and accept some conversion impact.

---

## "The form works on Chrome desktop; it crashes on Safari mobile."

**The diagnosis.** Browser/device-specific bugs. The form was tested on the team's primary platform.

**The cure.** Cross-browser, cross-device testing. The audience uses what they use.

---

## "We translated the form to Spanish; conversion is half what English is."

**The diagnosis.** Translation quality, cultural mismatch, or audience-fit issue specific to the Spanish-speaking audience. Often a combination.

**The cure.** Audit the translation quality (idiomatic vs literal). Audit cultural assumptions (date formats, phone formats, name conventions). Verify the audience matches.

---

## The pattern across failures

Most multi-step form failures fall into one of three patterns.

**Pattern 1: The form is the wrong structure.** Kitchen-sink-single-page, progress-theater, arbitrary-chunking, hidden-length. The fix is structural.

**Pattern 2: The form does not match the audience or the device.** Mobile-broken, validation-strict-against-international-inputs, audience-fit weak. The fix is matching the form to where the audience actually is.

**Pattern 3: The form decays.** Stale references, broken integrations, drift in conditional logic, instrumentation drift. The fix is maintenance discipline.

The metric pattern: form failures often look fine on submission count alone. The signal is in completion rate, drop-off per step, lead quality, and downstream conversion. Programs that track only submission counts keep shipping the same patterns.

---

## Methodology-level choices that stay in the public skill

The catalog of failure patterns with diagnoses and cures. The pattern across failures (structure, audience-device match, decay). The principle that submission count alone is insufficient as a success metric.

## Implementation choices that stay internal

Specific failure cases the team has encountered and the lessons learned. Specific multi-metric dashboards the team uses. Specific cures the team applies. The team's audit and retirement processes. These vary by team.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall