🤔 Find more resources and articles at http://askwhy.substack.com

Context and background

[This section is the place to gather existing documents, understand what the business is trying to do overall]

• What you already know, and what the team is assuming
• What the organisation as a whole is trying to achieve with the feature/product/area - business goals and objectives
• Links to relevant documents to pre-read

Hypothesis

[By having this clear and understood, as a researcher, you can suggest the right approach. Referencing the context and background will give you a sense are these real hypotheses the team needs answers to or do they already know all of this.]

Participants and demographics

[It should tie in again with your goals outlined in the context and background. Usually, the development team has an ideal customer in mind, and if they don’t then think about the customers that your organisation as a whole is focusing on. Another way to look at this is users and non-users.]

Method

[Choose an appropriate method or methods which matches the project objective and timeline. You might need to use different methods for the different hypotheses or goals.]