Why improving drop-off is worth the effort
Drop-off is the share of people lost at each step of the journey after a scan. Every step loses some people; measuring where the losses concentrate tells you which step to fix first.Some drop-off is healthy. People who were never going to convert should leave early rather than waste support time later.
Diagnose before you change anything
Improvement starts with diagnosis, not with redesign. Before changing a code, split drop-off by form step, page, device, and placement and look for the weakest segment. The weakest segment is where a fix buys the most, because it holds the largest pool of lost value. Also check the steps around drop-off: a problem upstream, such as poor placement, can masquerade as a problem with the code itself, and a problem downstream, such as a slow landing page, can waste scans that were earned fairly. Fix the constraint, not the symptom.Write down your diagnosis in one paragraph before you touch anything. State what you observed, which segment is weakest, and what you believe is causing it. This paragraph is your hypothesis, and it keeps the work honest: if the fix does not move the number, the hypothesis was wrong, and you learn something instead of merely changing things.
Levers that move drop-off
- Shorten the step with the worst drop-off before redesigning anything else. - Remove optional fields and surprise requirements from forms. - Show progress and confirm what happens after the final button.Work through the levers in order of expected impact per unit of effort. A lever that costs nothing and affects every scanner beats a lever that costs a print run and affects one placement. For each lever, state the change, the cost, and the segment it should move, then implement only that change. Bundling several changes together feels productive, but it destroys your ability to learn which one worked.
Test the change properly
Drop-off at a step = people who entered the step minus people who completed it, divided by people who entered, multiplied by 100.Illustrative example numbers, not real-world data: 120 people start a form and 60 complete it, giving (120 - 60) / 120 x 100 = 50% drop-off at the form step. Halving that drop-off would add 30 completions without a single extra scan.
Run the change as a comparison wherever you can: the old version against the new version, on comparable placements, over the same kind of period. Keep everything else stable, and decide in advance how long the test runs and what counts as a win. A test that ends the moment one variant pulls ahead is not a test, it is a reaction. If traffic is too small for a formal test, change one thing, record the before and after numbers, and treat the result as suggestive rather than proven.