UX and research · Beginner · 12 min
Write a one-page research plan
By Padding · Updated 18 Nov 2026
Any shared document and a calendar · November 2026
You will have a research plan that fits on one page, with every question tied to a decision, and a stakeholder sign-off you got in a five-minute read.
On this page
A research plan is not there to prove you are being thorough. It is there so that the people who will act on the findings agree, before anyone talks to a user, on what you are trying to learn and what they will do with the answer. If that agreement is missing, a good study still ends in "interesting, but we were going to do it anyway".
Long plans fail at this. Nobody with the authority to approve them reads past the first page, so the parts that matter (scope, the decision, who must watch) never get challenged until the readout. One page forces you to choose, and a short plan is one a busy product lead will read and answer the same day.
This tutorial builds a plan for a made-up example: a regional bus company whose app sells single tickets, and a team split on whether to add a monthly pass. You will start from the decision, write questions that feed it, cut the ones that do not, then fill in method, participants, schedule and observers. The rule that runs through every step: if a question's answer would not change what the team does, it does not go on the page. Swap in your own product as you go.
Step 1 · Write the decision at the top
Open a new document and give it a plain title, such as "Research plan: monthly pass in the app". Leave a line for the date and your name.
Before any questions, write one line headed Decision this feeds. Name the decision, who makes it and when. For the bus app:
Decision this feeds: Whether to build a monthly pass in the app for the March release, or keep single tickets only and spend that time on journey planning. Decided by the product lead (Amara) at release planning on 9 December.
If you cannot name a decision, stop and find one. Ask the person who requested the research: "What will you do differently depending on what we find?" If the answer is "nothing yet, we just want to understand users better", that is still allowed, but say so. Write the decision as "Which of these three problem areas we put in next quarter's roadmap", or whatever it really is. A plan with no decision tends to grow until it covers everything.
Add a second line, Options on the table, listing the choices the decision maker is weighing. Two or three is normal:
- A: Build a monthly pass in the app
- B: Keep single tickets, build journey planning instead
- C: Sell monthly passes through the website only, no app work
Check it worked
Read the top of your page aloud. It should name one person, one date and at least two options. If you wrote "the team" instead of a person, or "soon" instead of a date, ask until you can replace them.
Step 2 · List every question people want answered
Under a temporary heading, Question dump, write every question anyone has raised. Pull them from the request message, meeting notes, the team chat and your own head. Do not filter yet. One question per line.
For the bus app the dump might be:
- How many riders travel often enough for a monthly pass to save them money?
- Do frequent riders already buy passes somewhere else, and where?
- What do riders think of the app's colour scheme?
- Would riders pay upfront for a month, or do they prefer paying per trip?
- How do riders currently show a ticket to the driver?
- Would riders use journey planning in our app or keep using a maps app?
- What do drivers think about scanning passes?
- Which competitor apps do riders use?
If your team has already mapped its assumptions, the riskiest ones belong here as questions. "We assume frequent riders want to pay monthly" becomes "Do frequent riders want to pay monthly?"
Check it worked
Your dump has at least six questions and includes at least one you suspect is off-topic. A dump with only perfect questions means you filtered too early, and the next step will have nothing to cut.
Step 3 · Tie each question to an option, then cut
Go through the dump one question at a time. For each, write next to it which option the answer would push the decision towards, and how. Use this form: "If we learn X, that favours option A; if we learn Y, that favours B."
- Q1 (how many ride often enough): if few riders travel often enough to save money, that favours B. If many do, A or C. Keep.
- Q2 (buy passes elsewhere): if they already buy paper passes at kiosks and are happy, that favours C or B. If they find it a hassle, A. Keep.
- Q3 (colour scheme): no answer changes A, B or C. Cut.
- Q4 (pay upfront or per trip): if most prefer per trip, the pass has a weak case, favouring B. Keep.
- Q5 (how they show a ticket): affects how a pass would be built, not whether to build it. Park.
- Q6 (journey planning): if riders say they would never leave their maps app, B loses its appeal. Keep.
- Q7 (drivers): matters, but riders cannot answer it, and it shapes building rather than choosing. Park.
- Q8 (competitor apps): interesting background, changes no option on its own. Cut.
"Park" means a real question for a later study. Move parked and cut questions to a short line at the bottom of the page, Not in this study, so nobody thinks you forgot them. Stakeholders accept cuts far more readily when they can see the question was heard.
Keep three to five questions. More than five in a study of this size means each gets a few minutes per session and none gets a solid answer. If you still have too many, keep the ones where you are least sure of the answer: a question the team can already predict is not worth a participant's time.
Rewrite the survivors as Research questions, numbered, each with its "favours" note in brackets. These are questions for the team, not the wording you will use with participants. That comes later, in the interview guide.
Check it worked
Every remaining question has a bracketed note naming at least one option it would favour. Cover the notes with your hand and ask: could I predict the answer to this already? If yes for any question, cut it or say why you still need evidence.
Step 4 · Choose a method that can answer those questions
Pick the method by what the questions ask, not by what you ran last time. A rough guide:
- Questions about why people do something, how they decide, or what they do now: interviews, or watching people in context.
- Questions about how many or how often: a survey, or existing data such as ticket sales and app analytics.
- Questions about whether people can use something: a usability test on a prototype or the live product.
Several questions often need two methods. For the bus app, Q1 is a counting question: the sales data already shows how many riders buy more than a certain number of single tickets a month, so it needs no participants at all. Q2, Q4 and Q6 are about current behaviour and reasons, which suits interviews.
Write the Method section in two or three lines:
Method: 30-minute remote interviews with frequent riders (answers Q2, Q4, Q6). Ticket sales export for the last six months, counting riders by trips per month (answers Q1). No prototype testing in this round.
Saying what you are not doing is as useful as saying what you are. It stops someone from expecting usability findings at the readout.
Check it worked
Each research question number appears at least once in the Method section. If one is missing, either add a method that answers it or move the question to Not in this study.
Step 5 · Say who you will talk to and how many
Write a Participants section. Describe people by what they do, not by age or job title, because behaviour is what your questions are about. For the bus app:
Participants: 6 riders who took the bus at least 12 times last month. At least 2 who have bought a paper monthly pass in the past year, and at least 2 who never have. Mix of app users and riders who buy tickets from the driver.
Six to eight interviews for one group is a common starting size for this kind of question. You will usually hear the main patterns repeat by then. If your plan covers two clearly different groups, budget for each one separately rather than splitting six people across both.
Add one line on how you will find them, such as "In-app message to riders with 12 or more trips last month, plus a notice at the two busiest stops", and one line on the thank-you you will offer. Keep the detail of screening and recruiting out of this page. It belongs in a separate screener.
Check it worked
Read the participant description and ask: could someone recruit from this without asking me anything? Each criterion should be something a person can answer yes or no to, such as "took the bus 12 or more times last month", not "regular rider".
Step 6 · Put dates on it and name who watches
Add a Schedule section that works back from the decision date. Planning backwards shows straight away whether the study is possible:
- 9 December: release planning (decision)
- 5 December: readout to the product lead and team, 30 minutes
- 1 to 4 December: synthesis
- 24 to 28 November: interviews
- 18 to 21 November: recruit and confirm participants, write the interview guide
If the dates do not fit, change the plan now. Cut a question, use fewer participants, or ask for the decision to move. Discovering this in week two is worse for everyone.
Then add Who watches. Name at least the decision maker and one person who will build the thing. People who watch even two sessions argue less with the findings, because they heard them first-hand. Ask for a specific commitment, not general interest:
Who watches: Amara (product lead), at least 2 sessions. Tunde (mobile developer), at least 1 session. Sessions recorded with consent for anyone who cannot attend.
Check it worked
Your schedule ends on the decision date from the top of the page, and every person in Who watches has a number of sessions next to their name. Send each of them the session slots now, so the commitment is in their calendar and not only on the page.
Step 7 · Trim it to one page and get sign-off
Put the sections in this order: Decision this feeds, Options on the table, Research questions, Method, Participants, Schedule, Who watches, Not in this study. Delete the Question dump, since the questions you kept are now under Research questions.
If the page runs over, trim in this order:
- Background paragraphs. The decision line already says why the study exists.
- Method detail beyond what a stakeholder needs to agree to (session structure belongs in the interview guide).
- Adjectives and hedges such as "we hope to explore".
Do not trim Not in this study. It is the line most likely to prevent an argument later.
Send the page to the decision maker with a short message that asks for something specific:
Here is the plan for the monthly pass research. Could you check two things: are the options at the top the real ones, and would answers to questions 1 to 4 change your decision? Reply by Thursday and I will start recruiting on Friday.
If they add an option or question, run it through the same test from step three before adding it. If it would not change the decision, it goes under Not in this study, and you can say why.
Check it worked
The plan prints on one A4 or US Letter page at a readable size, with no section cut off. You have a written reply from the decision maker confirming the options and the questions, or a list of changes you have already made in response.
Next steps
Your plan is a working document. Keep it open during the study and check your interview guide against the research questions before the first session.
- Before you write the plan, use Map your assumptions and choose which to test first to decide which questions are worth a study.
- Find the people in your Participants section with Recruit participants for user research.
- Turn your research questions into what you actually ask with Write an interview guide without leading questions.
- When you have results, take them back to the decision with Report research findings so the team acts.
Part of these paths
Related tutorials
- Map your assumptions and choose which to test firstYou will turn your team's guesses about a product into a ranked map and leave with the two or three riskiest assumptions, each written up as a test you can run.
- Recruit participants for user researchYou will have a one-page recruitment plan, a private scheduling sheet and a first round of research sessions booked with the right people, including a spare for the person who does not turn up.
Need this done for you?
Padding does this work for growing companies, from the first diagnosis to a system that keeps working.
Get new tutorials