Write down what happened before deciding why.

A fictional inquiry journey

A participant reaches a project form, pauses at “Reference” and leaves the field empty. The observation is the pause and blank field. “They do not trust the business” is only one possible explanation; the label may simply be unclear.

Use a realistic task.

The GOV.UK guide to moderated usability testing describes observing participants attempt specific tasks. Its guidance recommends clear, relevant goals without instructions that reveal the route.

Agree suitable participation and data handling before a session. Use an appropriate test setting so the task does not unexpectedly send a real message or create a purchase.

Check the recorded outcome.

Does the event represent an attempted submit, a saved inquiry or a later qualified lead? Those are different outcomes. Review missing events, duplicates and internal tests before interpreting a conversion rate.

Choose a focused test.

Try a clearer label and instruction, then repeat the task. Check the effect on errors, completion and nearby decisions. Keep what was observed separate from an assumed future business benefit.

Report the limits.

Record the participants or data covered, conditions and unresolved questions. A small usability finding can guide a repair without proving a site-wide revenue effect.