Give the observation a context.
Record the task, materials, conditions, and any assistance provided. These details help someone understand what the observation represents. If the model or instructions change during the trial, note when and why.
In a visitor check-in illustration, a participant might ask whether their arrival was recorded. Record the question and the point at which it arose. “The wording was confusing” is an interpretation that may be reasonable, but it should remain distinct from the observed event.
Include the awkward parts.
An interrupted task, a missing instruction, or an unexpected question can be more informative than a smooth demonstration. Do not remove these events from the account merely because they complicate the story.
Also record when a condition was not examined. A short trial with a few prepared examples does not describe every user or operating situation. It can help identify an issue without establishing how frequently that issue occurs.
Choose an appropriate next question.
Ask which explanation the available observations support and what else could account for them. It may be useful to revise a model, repeat a task under different conditions, or gather information from another source.
A concise trial note can include the purpose, conditions, observations, possible explanations, and remaining uncertainties. The aim is a usable account that another person can question or extend. These notes describe general considerations, not company trial results.