# Does a How It Works Section Reduce Hesitation? A/B Test Page: https://alidemirbas.com.tr/en/lab/ab-test-library/tests/does-a-how-it-works-section-reduce-hesitation-ab-test ## Hypothesis If the page adds a step-by-step section on what happens after sign-up, visitors may see more clearly what they are starting and hesitate less. Completions of the primary action could go up as a result, though they could also fall if the effort involved looks heavier than expected. ## When to run this test Support questions like “What happens next?”, surveys that call the process unclear, or session recordings of visitors pausing at the CTA point to visitors holding back because they do not know the process. When the section sets the right expectations, more visitors start the action and fewer drop off at the first actual step, since they know what is coming. Before you write the section, check each step against the real process: do not leave out a required step such as verification or consent, or make a long stage look short. If drop-off is concentrated in the sign-up form, look at the form first. ## Primary metric **Primary action completion rate**: Compare whether adding a process explanation changes completion of the target action. ## Other metrics - **Next-step completion rate**: Among visitors who start the action after seeing the explanation, compare completion of the predefined next step. - **Process-related support contacts**: Track support questions such as “What happens next?”. - **Process section visibility**: Measure whether the section enters the viewport; visibility does not prove it was read. - **Drop-off at the first actual step**: Compare abandonment among visitors who begin the first real step. ## What to check before and during the test - **Explanation**: Add one predefined sequence that describes the existing process. - **Keep constant**: Keep the real process, CTA, testimonials and other page copy unchanged. - **Effort**: Show the required work clearly; do not add an unmeasured time estimate. - **Audience**: Review existing segments with different product experience. - **Separate tests**: Test detail level or time estimates separately. ## What to watch when reading the result - Set the primary action result beside the next-step completion rate and drop-off at the first actual step. If actions rise while first-step drop-off rises too, the section may be setting the wrong expectation, so do not ship it. Section visibility does not prove the section was read. - This page and the sequence of steps you described are all the finding covers; review segments with different product experience separately. Compare process-related support contacts across both arms over the same period, since that is where reduced uncertainty is most likely to show. - If you illustrate the steps with images, compare page speed between the arms. If the variant loads more slowly, the difference may come from load time rather than the explanation, and you cannot read the result as is. - Two opposite effects may have canceled out when the result is unclear: some visitors may feel reassured while others are put off by the effort. Work out how many visitors per arm you need to detect a small net effect with the [sample size calculator](https://alidemirbas.com.tr/en/calculators/sample-size-calculator). ## Frequently Asked Questions ### How should a how-it-works section describe the process? Show the actual steps, including necessary verification or approval. Do not make a demanding process seem effortless by omitting required work. ### Can estimated completion times be included? Yes, when supported by reliable measurements and clearly applicable conditions. Fix the chosen presentation before testing. Unsupported numbers should not be used. ### Can explaining the process reduce conversion? Yes. The work involved may appear less appealing. Use completed main actions as the primary outcome and inspect first-step abandonment, progression and process-related support questions.