State the decision and uncertainty
Describe the choice facing the team and the reason existing information is insufficient. For example, the question may concern how people interpret an action’s scope or where they expect to find a task. A broad request to “improve UX” needs a more specific starting point.
Identify who will use the result and when the decision needs to be discussed. This helps determine the appropriate material and the practical depth of the proposed investigation.
Define the audience and study material
The scope should describe relevant participant characteristics and how involvement will be arranged if sessions are included. It should also identify the interface, prototype, or information structure to be examined and who can prepare it.
Use invented or redacted information where it can answer the question. Access to existing systems, recording arrangements, and information handling should be agreed before the work depends on them.
Agree what will be delivered
A project can include a research plan, task material, observations, a findings record, and recommendations. The combination should suit the decision rather than reproduce a standard report package regardless of need. Specify review responsibilities and any dependencies.
The scope should distinguish assessment of current material from design or implementation of a revision. A recommendation may identify further work without including that work in the original engagement.
Set a sensible boundary for conclusions
The proposed method and audience determine what the evidence can support. A focused qualitative review and a broad measurement study answer different questions. Avoid promising a kind of certainty that the selected investigation is not designed to provide.
A written scope should preserve assumptions, exclusions, and open questions. If the product question or material changes, review the effect before continuing as though the original plan still applies. Schedule, price, and continuing services are agreed directly for the project.