rampstackco/claude-skills / skills/multi-step-form-design
multi-step-form-design
VerifiedDesigning 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.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 363 B |
| SKILL.md | skill md | 21.4 KB |
| references/common-multi-step-form-failures.md | markdown | 8.9 KB |
| references/conditional-logic-patterns.md | markdown | 9.6 KB |
| references/drop-off-measurement-and-remediation.md | markdown | 10.3 KB |
| references/form-anti-patterns.md | markdown | 9.7 KB |
| references/multi-step-decision-criteria.md | markdown | 9.2 KB |
| references/progress-indicator-patterns.md | markdown | 9.3 KB |
| references/save-and-resume-mechanics.md | markdown | 10.1 KB |
| references/step-architecture-patterns.md | markdown | 10.0 KB |
| references/validation-strategy-patterns.md | markdown | 10.4 KB |
references/multi-step-decision-criteria.md
View on GitHub# Multi-step decision criteria
When to break a form into steps vs keep it on a single page. The conditions that warrant the multi-step structure, and the funnels where multi-step adds friction without lift.
A multi-step form is a meaningful build. Step architecture, progress indicators, conditional logic, validation, save-and-resume, drop-off instrumentation. The multi-step form earns this investment only when specific conditions are present.
---
## When multi-step earns the build
Five conditions that, when present, make multi-step the right structure.
**The form has more than 8-10 fields.** Single-page forms beyond this point overwhelm the audience visually. The user scrolls, sees the length, and leaves. Multi-step breaks the visual length into manageable pieces.
**The fields naturally group into logical categories.** Personal info, then situation, then preferences, then specifics. Steps that reflect real groupings respect cognitive load. Arbitrary chunking does not.
**The audience benefits from progressive commitment.** Each step builds investment. The user is more likely to complete after engaging with step 2 than they would have been if they had seen step 5's complexity upfront.
**Different paths through the form make sense based on early answers.** Conditional logic that adapts the form to the user is hard to do on a single page; multi-step makes the adaptation feel natural.
**The success metric warrants the build.** Higher completion rate, lower drop-off, better lead quality, faster review for the receiving team. Without a defined success metric, the build is hard to justify.
When all five are present, multi-step is a strong structure. When two or fewer are present, single-page often serves better.
---
## When multi-step does NOT earn the build
Funnels where multi-step is the wrong structure.
**The form has 4-6 fields.** A single-page form is faster to complete and faster to maintain. Multi-step adds friction (step transitions, progress indicators, save-and-resume mechanics) without adding clarity.
**The fields do not group naturally.** Arbitrary chunking is friction. "Step 1: name. Step 2: email. Step 3: phone." The user wonders why this is multi-step and the question itself signals friction.
**The audience expects speed.** Quick contact forms, simple lead-capture forms, and high-intent CTAs often convert better as single-page. The multi-step format implies "this will take a while," which depresses high-intent users.
**The team cannot maintain the multi-step complexity.** Multi-step forms have more failure modes (conditional logic bugs, progress indicator drift, validation issues across steps). The maintenance overhead is real; teams that cannot commit to it should choose single-page.
**The form is a follow-up to a hot conversation.** A demo-request form right after a sales call should be quick. Multi-step here adds friction the audience is not ready for.
The honest assessment matters more than the default. "Should the form be multi-step" is not the question. "Is multi-step the right structure for this specific data collection and audience" is.
---
## The opportunity-cost frame
A multi-step form is meaningful work. Account for the cost honestly.
**The build cost.** Step architecture, progress indicators, conditional logic, save-and-resume, validation across steps, drop-off instrumentation. A meaningful multi-step form often takes 30-80 engineering hours plus design.
**The maintenance cost.** Steps decay as the brand evolves; conditional logic bugs surface; progress indicators need updating. Quarterly review and maintenance run 2-6 hours per active form.
**The opportunity cost.** What else could the team have built? A simpler form that converts adequately, a different growth-tooling investment, a content piece. The multi-step form's success has to clear the bar of those alternatives.
The decision frame. The multi-step form earns investment when it produces more conversion than the single-page alternative, accounting for the full cost of build plus maintenance.
---
## The grouping precondition
Without natural field groupings, multi-step is arbitrary.
**The check.** Can the fields be grouped into 3-5 coherent categories? Each category representing a unit of cognitive work the user can describe in one sentence?
If yes, multi-step has natural step boundaries.
If no (the fields do not group; the only structure is "first half" and "second half"), multi-step will feel arbitrary. Either restructure the data collection (some fields may not be needed) or choose single-page.
**Examples of natural groupings.**
- Identity (name, email, role) + Context (company size, industry, current setup) + Need (goal, challenge, timeline) + Confirmation.
- Personal info + Loan details + Property details + Financial verification + Submission (mortgage application).
- Account info + Use case + Plan selection + Payment + Confirmation (signup wizard).
**Examples of forced groupings.**
- Page 1 (name, email, phone) + Page 2 (company, role, source, industry, size). The page break is arbitrary; nothing groups these fields meaningfully.
- Page 1 (most fields) + Page 2 (one final field). The split is purely decorative.
The discipline. If the team cannot articulate the unit of work each step represents, the steps are arbitrary; either rework the steps or use single-page.
---
## The decision worked example
A B2B SaaS company considering whether to make a "Talk to sales" form multi-step.
**Conditions check.**
- Field count: 12 fields (name, work email, company name, company size, industry, role, current solution, primary use case, timeline, budget range, source attribution, additional context). Above the 8-10 threshold; multi-step is on the table.
- Natural groupings: yes. Identity (name, email, role), company context (name, size, industry), current state (current solution, use case), buying intent (timeline, budget), additional (source, context). 5 natural groups.
- Progressive commitment: yes. The audience giving budget at the end after engaging with the early steps is more likely to give it than if asked upfront.
- Conditional logic value: yes. If the audience selects "evaluating" timeline, additional fields appear; if "active project," different additional fields appear.
- Success metric: defined. Conversion rate to submission, lead quality (audience-fit at SaaS companies above 25 employees), downstream conversion to demo within 21 days.
**Decision.** Build multi-step. The conditions warrant it.
**Step architecture.** 5 steps: Identity, Company, Current State, Buying Intent, Submission Confirmation.
**Maintenance commitment.** Quarterly audit of conversion, drop-off per step, and conditional logic.
The decision was not "should we make this multi-step" but "given these conditions, this is the multi-step structure to build."
---
## The single-page worked example
The same B2B SaaS company considering whether to make a "Subscribe to newsletter" form multi-step.
**Conditions check.**
- Field count: 2 fields (email, name). Below the 8-10 threshold.
- Natural groupings: no. Two fields do not group.
- Progressive commitment: no. The audience subscribing benefits from speed.
- Conditional logic value: no. No branching needed.
- Success metric: simple conversion rate.
**Decision.** Single-page. Multi-step would add friction without value.
The decision was "what is the right structure" and the answer was single-page even though multi-step was nominally available.
---
## The hybrid pattern
Some forms work best with a "main" single-page form plus one optional follow-up step.
**The pattern.** A short single-page form (3-5 fields) gets the user committed; an optional follow-up appears after submission for users who want personalization.
**When this works.** When the primary action is fast (signup, lead-capture) but a richer follow-up benefits some users.
**When this does not work.** When the follow-up has to be required for the primary action to be useful.
The hybrid avoids both kitchen-sink-single-page and forced multi-step. It serves the speed-seeking audience and the depth-seeking audience separately.
---
## When to retire a multi-step form (or convert to single-page)
Multi-step forms can become wrong as the form evolves.
**Retire-or-convert when:**
- Field count has dropped below 6 over time as fields were removed.
- Conditional logic has been simplified out, leaving the steps with no real differentiation.
- Drop-off concentrates uniformly across steps, suggesting the staging is not working.
- A simpler single-page form might convert better.
**The conversion-to-single-page move.** Sometimes the right answer is to revert. The multi-step format earned the build at one point; conditions changed; single-page is now better. Honest reversion is part of the discipline.
---
## Methodology-level choices that stay in the public skill
The conditions that warrant multi-step. The opportunity-cost frame. The grouping precondition. The decision worked example. The single-page worked example. The hybrid pattern. The retire-or-convert decision.
## Implementation choices that stay internal
Specific multi-step decisions for specific forms. The team's capacity benchmarks for build and maintenance. Specific tooling for form engineering. Specific success-metric definitions and baselines. These vary by team.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |