Name the decision
behind the study.
Start with the product question in ordinary language. What is difficult to understand? What is the team considering changing? Which assumption needs to be examined?
A research request becomes more useful when it is connected to a real decision, even if that decision is still being shaped.
Gather what
the team already knows.
Existing research, support themes, analytics and product history can help define the starting point. Bring the evidence and explain how it was gathered, rather than presenting a conclusion without its context.
Include conflicting information. A disagreement between sources may be exactly the reason to investigate further.
Check access
and prepare the product.
Describe the product stage, the prototype or material available and the tasks the team wants to explore. Note any access constraints, unfinished paths or dependencies.
Recruitment, consent, recording and observer access also need attention. These arrangements should be planned before a session is put in a calendar.
Prepare to
look and listen.
Observers need to know the purpose of the session and how to take useful notes. Recording what happened separately from an interpretation makes later synthesis easier to discuss.
Agree how questions will reach the researcher and when the team will review the material together.
Prepare your brief