# All Fields Upfront vs Step-by-Step Reveal A/B Test

Page: https://alidemirbas.com.tr/en/lab/ab-test-library/tests/all-fields-upfront-vs-step-by-step-reveal-ab-test

## Hypothesis

With a step-by-step reveal, visitors see only the next required field at any moment, so the form may feel more manageable; showing all fields upfront makes the remaining work clear from the start. The step-by-step reveal may come out ahead on the form completion rate, but if later fields feel like a surprise, the advantage could shift to the all-fields option.

## When to run this test

The form's length may be putting people off before they begin if a high share of visitors see the form but never start, or if survey answers call it long. If the step-by-step reveal wins, expect more visitors to start and reach submission without sudden drop-offs at revealed fields. If drop-offs cluster at one required field, that field may be the problem rather than the length, so look at it first. Do not hide a sensitive request behind a later reveal; explain it upfront or find another way to ask.

## Primary metric

**Form completion rate**: Compare successful submissions to see whether progressive disclosure affects completion.

## Other metrics

- **Form start rate**: Check whether a shorter initial view encourages visitors to begin.
- **Optional-field completion rate**: Make sure the quality of collected data does not fall materially.
- **Average completion time**: Check whether expanding and collapsing sections adds time.
- **Field-level abandonment**: Track whether visitors leave when a field appears.

## What to check before and during the test

- **Reveal rule**: Choose one progressive-disclosure mechanism before launch; the current setup does not specify one.
- **Keep constant**: Keep field count, required status, copy and validation unchanged.
- **Expectation**: Make required information and remaining work clear before visitors begin.
- **Optional data**: Track completion without treating every decline as a reason to stop the test.
- **Device**: Review effects on smaller screens separately.

## What to watch when reading the result

- Look at field-level abandonment and the form start rate next to the form completion rate. Lower optional-field completion is not a reason to stop on its own; weigh it against the completion difference and check that the data you collect is still usable. If abandonment rises at the fields that appear, do not declare the step-by-step reveal the winner.
- If revealed fields make the page jump, the result measures layout shift as well as the reveal itself. Check scroll position, focus and the small-screen layout in both options, and treat the result as valid only for this implementation.
- For a small or unclear difference, compare the two options' form completion rates in the [A/B test significance calculator](https://alidemirbas.com.tr/en/calculators/ab-test). Without a significant gap, hold the decision and note side signals such as average completion time.

## Frequently Asked Questions

### How can hidden remaining work affect users?

Unexpected additional fields may cause abandonment. Explain the work ahead and avoid using progressive disclosure to conceal sensitive information requests.

### Should lower optional-field completion stop the test?

Not automatically. Use valid form completion as the primary outcome and assess data quality against the predefined guardrail. Not every optional-field decline is a stopping condition.

### Can appearing fields disrupt the experience?

Yes. Check scrolling, focus and mobile layout. Movement caused by disclosure is part of the implemented experience, so interpret the result with that usability cost.