How to create an impactful user research plan
Set yourself, your team, and your project up for success from the beginning
👋 Hey, I’m Nikki. Each week I write about UX research strategy, communicating impact, and using AI to do your best work. For more: Claude Skills Bundle | AI Prompt Library | Team Training
P.S. Paid subscribers get access to full archive, all content, a private Slack community, Substack lives, and a hub of templates, scripts, and mini-courses
I am an avid planner - I always have been, even when I tried to fight it. Planning ahead assures me that things will have a certain outcome and that everyone will be on the same page with expectations if anyone else is involved.
When it comes down to it, for me, planning is about managing expectations.
I didn’t apply this to my professional life for a long time. When I transitioned into user research, I was completely self-taught. Yes, I did a UX Design course at General Assembly, which mainly taught me I can’t design, but other than that, I read books and did my best to piece together the profession.
In my first role as a user researcher, I had little concept of planning. My colleagues and I would talk about research that needed to be done, and I would go and do it. At the time, I didn’t have the capacity to question why we were doing specific projects, asking certain questions, or what the outcomes were supposed to be.
My main downfall, and the reason behind this, was perfectionism. I wanted to appear like I was good at my job and that I knew everything.
We have to survey our users to determine what about our app was unintuitive? Sure thing!
We have to do discovery research to verify our assumptions? Can do!
In fact, I tried:
I didn’t know how to structure a goal — trust me, searching for user research goals and examples of them ten years ago led to absolutely nothing. The Interwebs was not my friend back then.
I didn’t know what to question, let alone how to respond to my stakeholders when they had questions.
What did this lead to?
Lack of clarity on what I was trying to research (either too broad or narrow in scope), which made it a nightmare to figure out appropriate methodologies and which questions to ask
Mismatched expectations on what colleagues got as outcomes of the research project
Inability to focus during the research because I was unsure about what topics I needed to cover or what I could skip
Little alignment on why we were doing the research project and what would make it successful in the end
What this list leads to is one word: disappointment. I don’t know about you, but (to me) nothing is worse than disappointing my team. And I’ve also found with disappointment comes skepticism. If research isn’t bringing value, do we need to do it? What’s the point?
That’s the last thing I wanted. So, I vowed to do better and, over time, built a research plan that I now use as a starting point (yes, still, to this day!) for my research projects.
What is a user research plan?
A user research plan is a document that lists the different parts of the research project, including why the research is happening to the research outcomes. They give you and the team an amazing overview of the research project and remind people exactly what the project is about, which greatly helps with scope.
The best part of a research plan is aligning people into a shared understanding so that everyone’s expectations are properly set up. Expectations are key when it comes to user research.
If a stakeholder is expecting that they will get a journey map out of a research project and we come to them with a written report, it won’t be the best of times.
Or, if a stakeholder expects deep insights and we conduct a survey, there will be a huge mismatch in the outcome.
A research plan is a forcing function (in the best sense possible) to get everyone’s thoughts and expectations of a research project out on paper, giving you, the researcher, clarity on how to best navigate the project for the necessary outcomes.
Below, I walk you through the full system I use to stop “random acts of research” and start running studies with clean scope, aligned stakeholders, and outcomes people can actually use:
The research plan framework that protects you from disappointment (how to set expectations, lock scope, and stop “wait, I thought we were getting a journey map” chaos)
The “does this project suck?” test (how to spot un-answerable requests early, push back without drama, and avoid wasting weeks documenting nonsense)
The intake document that replaces endless follow-up meetings (the exact prompts that force stakeholders to show their homework and give you what you need up front)
My complete research plan template, section by section (background, stakeholders, assumptions, goals, success criteria, methods, recruitment, deliverables, timeline, scripts, resources)
Two real examples you can copy (one generative plan, one evaluative plan, written the way stakeholders actually read)
Exclusively for paid subscribers
