Skip to content
Team
UXR Lead: Name
Design Lead: Name
PM Lead: Name
DS Lead: Name
Background
Provide clear context and background about why research is needed. What are the problems that the research will solve? What business goals will the research help meet?
<Add links to any previous UX research>
<Add links to any competitive research>
<Add a link to the product PRD if available>
Goals
Research Goals
Clearly articulate the goals of the research. Why is this research being conducted? What are the questions that research will the help answer?
Provide the research goals in a bulleted format so they are easy to read and scan.
Business Goals
How will this research help the business meets its goals? What Objective Key Results (OKRs) is the research related to? How will the impact of the research be measured? Do you expect to see a change in KPIs based on changes made from research?
Hypotheses
Clearly state current hypotheses that will be tested. A good way to formulate hypotheses statements is to use the Lean UX Hypothesis format.
We believe that [doing this/building this feature/creating this experience] for [these people/personas] will result in [this outcome]. We will know this is true when we see [this signal/feedback/metric].
a. Hypothesis 1
b. Hypothesis 2
c. Hypothesis 3
Methodology
Type of Study
What research methods will you use to answer the questions? Ethnography, concept testing, usability, survey etc. Write a brief statement on why this is the best approach.
Feel free to show where the research falls in the design process. The double-diamond approach is an easy methodology to share when you are working with teams that are new or learning to work with research.
<Add Link to Prototype or any other asset>
<Add link to Jira Story/Airtable/Any other tools>
Research Sample
General Criteria of who are the participants who will be recruited? What will be the total sample size? Any cohorts within the sample? How many will you recruit within each cohort?
For survey research provide a detailed description of the sampling strategy. Use this to show your reasoning for the sample.
<Add link to the screener>
Research Timeline
Kickoff
Recruitment
Fieldwork
Debrief
Final readout
Apr 2025
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
May 2025
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Jun 2025
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
Jul 2025
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Aug 2025
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Sep 2025
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
Oct 2025
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Nov 2025
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
Dec 2025
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Month
TodayFit
Research Project Name
Title
Start
Duration
Description
Kickoff
9/24/2023
5 days
Kickoff with team
Recruitment
9/29/2023
5 days
Participant recruitment
Fieldwork
10/4/2023
5 days
Conducting sessions or survey in the field
Debrief
10/4/2023
5 days
Ongoing debrief
Final readout
10/23/2023
1 day
Final readout
There are no rows in this table
There are two easy ways to show the timeline. You can use Gantt chart or table view. I am personally a fan of the Gantt chart view.
I also am a big fan of inviting team members to all the research sessions while conducting qual research and sign them up to be note takers.
Deliverables
Set expectations early on what will be the final deliverable. Will it be a slide deck or something scrappy?
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.