I’m hosting a free 30-minute lesson on how Claude skills can be impactful and useful for user researchers on June 30th at 5:00pm BST (UK time). You’ll learn what skills are and how I apply them to my work. Recording will be sent out to all those who join (plus a discount code to my next workshop!).

Join the free session!

A few weeks ago, about thirty seconds before a discussion guide left my hands for a client, I typed three words into Claude, “red team this,” and it handed me back three leading questions I’d read straight past a dozen times without noticing. I fixed them on the spot, sent the guide, and ran those sessions without the usual little voice in the back of my head asking what I’d missed.

That tiny moment is the whole reason I’m writing this, and what I’ve come to value most about Claude is having a second set of eyes sharp enough to catch the things I’ve gone blind to in my own work, the leading question I can’t see anymore, the survey set up to hand me bad data, the number in my readout I can’t quite explain. I have a folder on my phone called “AI stuff” that is a graveyard of saved prompt lists I never once opened, and not a single one of them ever did for me what two words typed into Claude did that afternoon.

What actually changed how I work with Claude was a small handful of frameworks I could point at anything, a discussion guide, a slippery stakeholder request, a repository nobody’s opening, a readout I’m half-convinced will get skimmed and forgotten. Once I had the framework, I stopped reaching for the prompt lists entirely.

So these are the ten I keep coming back to, written for the work we actually do all day. The first five turn Claude into a sharper thinking partner. The last five help you find the holes in your work before a stakeholder finds them for you, and if you’ve ever sat through a readout where someone poked the one weakness you didn’t see coming, you already know in your body why I care about it this much.

None of them need a perfect prompt, which is sort of the whole point, since you type a couple of words and the thing on the other side shows up completely differently.

01. Interview Me

Type “interview me” before any big task and Claude asks you questions before it starts, instead of charging ahead and guessing like an over-eager intern who didn’t want to seem unsure. The questions it fires back at you are the brief you never wrote down, the scope you hadn’t pinned, the audience you waved your hand at and hoped for the best on.

I use this before almost every discussion guide I build now. The version of Claude that asks me six sharp questions first, who’s the participant, what decision is riding on this, what have you already tried, hands me a draft that’s ten times closer to usable than the version that fills in the blanks on its own with whatever it assumed I meant.

Interview me before you write anything. Ask me everything you need to know to build a discussion guide for a generative study on how freelancers manage irregular income, then write the guide once you have what you need.

It works on anything that starts from a blank page, a research plan you’ve been avoiding for a week, a screener you keep getting subtly wrong, or the vaguest gift of all, the stakeholder who drops “can we do some research on the new dashboard” into your Slack and then evaporates. I let Claude interview me to turn that one sad little sentence into a real scope before I write a single word back to them.

Interview me before we scope this. My PM asked for "some research on the new dashboard" and gave me nothing else. Ask me the questions that will turn that into a real research plan with a clear decision, a method, and a timeline.

We are researchers. Being interviewed before the work starts is the most natural thing in the world to us, so do yourself a favor and let Claude do to you what you do to your participants every week.

02. Socratic

Type “teach me this using the Socratic method” and instead of dumping the answer in your lap, Claude teaches by asking you questions until you walk yourself to it. Anthropic built a whole Learning mode around this, because it’s how the thing actually stays in your head past Tuesday.

I reach for this with the corners of research I never formally trained in, the stats most of all. When Claude just hands me a sample-size formula, I forget it by the next study and have to go looking for it again like keys I swear I left on the counter. When it walks me there through questions, I remember it well enough to defend it when a data scientist raises an eyebrow at me across the table.

Teach me how to calculate the sample size for a benchmarking usability test using the Socratic method. Ask me questions instead of handing me the formula.

I use it before I run a method for the first time too, when I’d rather understand the analysis than fake my way through and pray nobody asks a follow-up. You can tell Claude to pause and check your understanding as it goes, which keeps you honest about whether you genuinely followed or just nodded along the way we all do in meetings we’ve mentally left.

I'm setting up my first card sort and I'm shaky on how to analyze the results. Teach me how to read the output using the Socratic method, and pause to check I'm following before each new concept.

The real gift here is retention. A formula Claude hands me lives in a Slack message I will never find again, and an idea it walked me to lives in my head, ready and waiting for the exact meeting where someone asks me to explain myself.

03. Ultrathink

This one only works in Claude Code, so tuck it in your back pocket for when you’re in there. Type the word ultrathink anywhere in your prompt and Claude’s thinking budget jumps to roughly eight times its normal amount before it answers, which buys you its deepest reasoning on the genuinely hard problems instead of the quick first thing that pops into its head.

I save it for the design decisions where I can feel three tradeoffs pulling against each other like dogs on three different leashes, and I want every one of them named before I commit to anything.

ultrathink, help me design the analysis approach for a mixed-methods study where I have 14 interviews and a 600-response survey, and flag every tradeoff in how I combine them.

The other place it earns its keep is when two data sources flatly disagree and I need to reason carefully about which one to trust and why, the kind of problem where a fast answer will march me somewhere confident and completely wrong.

ultrathink, my survey says users are satisfied with onboarding but my interviews say they're frustrated and confused. Help me work through every reason these two could disagree, and how I should weigh them in my readout.

I don’t reach for it on the small stuff, though. Asking Claude to ultrathink a simple screener is like booking a moving truck to carry one kitchen chair. On the messy structural problems, the extra wait pays for itself.

04. Second Order

Add “second order” before a decision and Claude tells you what happens next, and then what happens after that, the downstream stuff most of us sail right past when we’re staring at the immediate win.

This earns its keep around democratization, where I keep watching researchers make a call that looks fantastic on Monday and detonates a quarter later when nobody’s looking.

Second order, if I hand my PMs a self-serve usability testing tool so they can run their own sessions, what happens next, and then what happens after that?

What I’ve found is that the first-order answer is always “more research gets done, great,” and the second-order answer is where you meet the person who’s going to be cleaning up all the bad data, and that person, plot-wise, is you.

I run it on the quiet process decisions too, the ones that look harmless in the moment and grow teeth later. The faster method that saves you a week now and costs you a re-do in three. The incentive you trim to protect your budget that craters your show-rate. The report template you standardize until every readout looks identical and reads like wallpaper. Second order is how I catch those while they’re still hypothetical and cheap.

Second order, if I switch from moderated to unmoderated testing to save time this quarter, what happens next, and then what happens after that, to the depth of what we learn and how stakeholders treat our findings?

05. Inversion

Instead of asking Claude how to make something work, you flip the whole thing over and ask how it could fall apart. Claude maps out every way the thing fails, and you walk off with a checklist of exactly what to avoid, which is a much more useful object than a vague pep talk about doing your best.

I run this on readouts constantly, because the question I actually care about isn’t “how do I make a good presentation,” it’s “how does a perfectly good presentation still end up ignored by Thursday.”

Invert this. I want stakeholders to act on this readout. List every way this presentation could get nodded at in the room and then completely forgotten by Thursday.

It’s just as good on the work where the failure stays invisible until it’s far too late to fix. A survey can pull six hundred responses and still be worthless if the questions were leaking or the wrong people wandered in, so before I launch one I ask Claude to invert it and tell me every way it plans to betray me.

Invert this survey. I want clean, trustworthy data on why users churn. List every way this survey could hand me garbage, leading questions, the wrong respondents, scales people misread, and tell me what to fix before I send it.

The whole trick with inversion is treating the failure list as your to-do list. Every item Claude names is a thing you go fix, one by one, before the work ever leaves your hands.

06. ELI5

Short for “explain like I’m 5.” Add it to any prompt and Claude breaks the most intimidating thing into the smallest, plainest possible words. I use it on the things I’m a little embarrassed to admit I’ve been nodding along to for months, the p-value my data scientist drops in Slack like it’s obvious, the SQL my analyst keeps referencing, the clause in a research vendor contract I definitely signed a year ago and definitely did not fully read.

ELI5, what does a p-value of 0.03 actually mean for the A/B test my data scientist just shared, and what can I honestly say about it in my readout?

I recommend this one hard if you came into research from a non-quant background like I did. There is no shame in not knowing something, there’s only shame in standing up in a readout and presenting a number you couldn’t explain if someone gently asked.

The move I love even more is flipping it around and asking Claude to ELI5 my own finding for one specific stakeholder, because if I can’t get my insight down to something a busy exec grasps in a single read, I usually don’t understand it half as well as I’d been telling myself.

ELI5 this finding for a VP of Product who has 30 seconds and cares mostly about revenue: "Users abandon checkout because the trust signals are buried below the fold and they don't believe their card is safe."

The day I can’t ELI5 my own finding is the day I know in my gut it isn’t ready to leave my laptop.

07. Pre-Mortem

Drop this in front of any plan and Claude pretends the project already cratered six months from now, then works backward to tell you exactly why. It surfaces the blind spots while they’re still cheap, before you’ve poured a quarter of real, unrecoverable time into them.

I wish I’d had this before the first research repository I ever set up, the one I lovingly tagged and color-coded and organized into oblivion, and then watched nobody open for the better part of a year.

Pre-mortem this. I'm about to launch a research repository for a 50-person product org. Pretend it's six months from now and nobody is using it. Walk me through exactly why it failed.

The failures Claude names are the ones I’d have sworn on my life wouldn’t happen to me, which is precisely why I needed to hear them out loud before launch instead of after, when they’re just called regret.

Pre-mortem and inversion are close cousins, and I use them for different sizes of bet. Inversion gives me a cold list of ways an artifact could fail, perfect for a survey or a deck. Pre-mortem tells me a whole story about a future where my big commitment already collapsed, which is the version I want before I sink real time into a repository, a research roadmap, or a democratization program I’m about to sell to leadership with my name on it.

Pre-mortem this. I'm about to pitch leadership on a democratization program where trained PMs run their own usability tests. Pretend it's a year from now and it's blown up in our faces. Tell me the story of how.

08. Steelman

Tell Claude to “steelman the other side” and it builds the strongest, smartest version of the argument you disagree with, the one that’s actually hard to swat away. It’s uncomfortable in the useful way, the way a good editor is uncomfortable, because it shows you exactly where your own thinking has gone soft.

I use this to prep for the stakeholder who wants to skip research and ship yesterday. If I can only argue against a cartoon version of their position, I lose the room in about ninety seconds, and if I’ve already heard the best possible version of “we don’t have time for this,” I can walk in and meet it head on.

Steelman the case for skipping research on this feature and shipping now. Give me the strongest version of my PM's argument so I can actually respond to it in our planning meeting.

The braver use is turning it on myself. When I catch myself dismissing a method out of hand, I ask Claude to steelman it, and every so often it changes my mind, which is embarrassing and also the entire point of asking.

I've been dismissing surveys for this question because I think it needs depth. Steelman the case that a well-designed survey is actually the better method here, and be convincing.

I run it on my own conclusions before a big readout too, asking Claude for the strongest possible case that my data says the opposite of what I’ve decided it says. I would so much rather find the hole in my story at my own desk, in my pajamas, than have a VP find it for me in front of the room.

09. Red Team

Add “red team this” before any plan, guide, or deck and Claude attacks it from every angle a critic would, like handing your work to a panel of professional skeptics who give you their honest notes in thirty seconds flat. You find the holes before the room does, which is the only good time to find them.

This is my last pass on every discussion guide I write. Leading questions hide so well from the person who wrote them, smiling and looking reasonable, and Claude is very good at catching the ones I’ve gone completely blind to.

Red team this discussion guide. Show me where my questions are leading, where I'll get shallow socially-acceptable answers, and where I'm asking people to predict their own future behavior.

I’ve started running it on the readout deck itself before big presentations, asking Claude to sit in the chair of the most skeptical person in the room. The VP who’ll ask “you only talked to eight people?” before you’ve finished your second slide. The engineer who distrusts anything qualitative on principle. The PM hunting for a reason to do the thing they already wanted to do. Hearing all of their objections a day early means I walk in with answers instead of standing there blinking.

Red team this readout deck. Sit in the seat of a skeptical VP and a data scientist who distrusts qualitative work. Where will they poke holes, question my sample size, or wave off the findings, and how should I answer each one?

10. First Principles

Add “break this down from first principles” and Claude stops parroting the conventional wisdom back at you and rebuilds the answer from what’s actually true. This is the one Elon Musk won’t stop talking about at parties, and the reason I love it for research is that so much of what we do is inherited habit nobody has questioned since before we got here.

Break this down from first principles. Do I actually need to recruit 5 users for this usability test, or is that just a number we all repeat because we read it once and it sounded official?

Half the time the first-principles answer brings me right back to the convention, which is fine and good, because now I’m doing it on purpose with my eyes open instead of on autopilot. The other half, it frees me from a rule that never fit my situation in the first place and was just along for the ride.

I aim it at the rituals I’ve stopped even noticing, the ones surviving on pure momentum because the last researcher did them this way and the one before that. The 60-minute interview that could have been 35 and everyone’s relieved. The full slide deck nobody asked for when a one-page memo would have moved twice as fast. The quarterly cadence we follow without ever once choosing it on purpose.

Break this down from first principles. We run a 60-minute interview and a full slide deck for every study out of habit. What is each of those actually for, and what would I do if I designed our process from scratch today?

Asking “what is this for, from scratch” is how I find the work I’m allowed to stop doing, and for most of us drowning in requests, that’s the most valuable answer there is.

Stack them

These get properly dangerous when you combine them, and stacking is where the real thinking-partner magic shows up.

Pre-mortem this research repository rollout, then steelman the strongest reason a team would refuse to use it, then give me the 3 changes I should make before launch.

Mix and match based on whatever you’re trying to figure out. Inversion plus red team for a survey you’re nervous about. Second order plus steelman before you walk into a democratization conversation you suspect will get tense. Interview me, then first principles, when you genuinely have no idea what you’re even solving yet. Or red team your readout, then ELI5 the fix for every objection it surfaces, so you can say each one out loud in the meeting without fumbling for words.

The one thing I’d love for you to take from all this is exactly where I started, treating Claude less like a search bar you fire questions at and more like the sharp, slightly skeptical colleague who reads your work before anyone important does. I didn’t need a folder of 500 saved prompts to get that second set of eyes, I needed about ten small moves and the nerve to point them at the work that actually scares me.

So if you do one thing with this, make it small and make it this week. Open the messiest thing on your plate right now, the discussion guide you’ve been avoiding, the survey you’re unsure about, the readout you’re presenting on Thursday, and before it leaves your hands, run one of these on it. Red team the guide, invert the survey, pre-mortem the launch, whichever one matches the part you’re most afraid of getting wrong, and let Claude find the hole while it’s still cheap to fix.

Come tell me in the comments which one you reached for first, and what it caught.

Stay curious,

Nikki

Want to become a Claude master (think Pokemon master but for Claude), check out my resources:

• 53 Claude Skills built for user researchers

• 7 Claude Agents to scale your research workflows

• Join my live Claude workshops

• Bring me to your company!

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

Subscribe now

If you’ve ever sat in a strategy meeting and watched the PM, the head of product, and the leadership team trade views on where the company should be in three years, and waited politely for someone to turn to you and ask the “user perspective” question, you’re not alone.

You probably know more about your users than anyone else in that room. You know the gaps in the product, the workarounds people have been building, the unmet needs that have been showing up in interviews for the last four quarters and that nobody has acted on yet. But none of that translates into “where should we be in 2030,” and I don’t think it’s because you don’t know enough. I think it’s because you’ve been pinned to a completely different kind of question for so long that the strategic muscle has gone unexercised.

The roadmap is loaded, the stakeholders need a usability test by Friday, the PM wants to know if the new flow tested cleanly, and there’s another tactical question on your desk before this one is finished. That’s been the whole job, every quarter, for years. The “be more strategic” feedback keeps showing up in performance reviews, the strategy offsite invitation keeps going to product, and you keep getting looped in only when something has already broken.

I think the frustrating part is that we, as user researchers, are the most under-utilised strategic foresight resource in any company. We already do half the futurecasting job by training and instinct, but we just have only ever been allowed to point those skills at next quarter.

Why user researchers were trained for this work

I want to make a case I haven’t seen anyone make clearly enough yet, which is that user research methodology is, structurally, the foundation of futurecasting. We don’t think of it that way because nobody has framed it that way for us, but once you see it, the whole career path opens up.

Here’s what I mean.

We study the past to understand the future

Every method in our toolkit is retrospective. Interviews ask people about past experiences and past behaviors. Diary studies capture recent past behavior. Behavioral analytics is, by definition, a record of what already happened. Journey maps reconstruct past sequences. Usability tests reveal how users have learned to interact with patterns over time. We are trained from day one to extrapolate forward from observed past behavior, which is exactly what futurecasting requires at its core.

When I conduct a generative interview about how someone manages their finances, I’m not really asking about today, I’m building a model of how their behavior has evolved over the last 5-10 years and using that trajectory to predict what they’ll need next. That’s futurecasting, just at the individual user level. The strategic version simply scales it up to the population, the segment, the industry.

We already make defensible calls under uncertainty

Every research recommendation we make is a forecast. “Users will struggle with this flow” is a forecast. “This concept will resonate with mid-market buyers” is a forecast. “The drop-off here will increase if we don’t address X” is a forecast. We just don’t call them forecasts, we call them findings, and futurecasting is the same skill applied to longer time horizons.

We are signal-trained

Researchers spot weak signals in qualitative data for a living. The unprompted aside in interview number seven that becomes the seed of an insight three weeks later, the comment three different participants make in slightly different ways, or the friction users describe but cannot quite name. We are pattern-matchers by craft, which is the single most valuable skill in foresight work.

We have direct access to the most valuable signal source in any futurecasting model

Qualitative user truth, gathered first-hand, is something no industry analyst report can replicate. Most foresight practitioners get qualitative input through commissioned panels and second-hand transcripts. We have it as our day job, which is a structural advantage we have never used at strategic scale.

The reason we haven’t been doing this work is not that we can’t, it’s that we’ve been too busy.

What AI actually changes for researchers

I want to be careful here because I think synthesis is one of the worst use cases for AI. Synthesis is interpretation, and interpretation is the job. The moment we hand interpretation over to a tool, we lose our edge.

What AI actually changes is three different things.

The from-scratch tax goes down

Every research project used to start from a blank page. New discussion guide, new screener, new analysis structure, new readout template, new stakeholder briefing format. With AI, you build the scaffolding once, save it as a reusable skill or prompt, and never start from scratch again. That gets you 2-4 hours back per project, which compounds into days you didn’t have before.

Smarter democratization eases the bottleneck

Custom agents and trained skills mean a PM can run a first-pass usability review or a screener draft without me, which gets me out of the queue and into the strategic seat. I’m not training stakeholders less, I’m training them better, with agents that hold the rigour I’d want them to hold even when I’m not in the room.

AI brings together radically more signal types than one researcher could process by hand

This is the actual unlock for futurecasting, and it’s the one nobody is talking about enough. Doing the work futurecasting requires (interviews plus behavioral analytics plus market trend reports plus competitor product moves plus regulatory shifts plus macroeconomic indicators plus public conversation in customer communities plus adjacent-industry signals) has been functionally impossible at the individual researcher level. AI changes that, because it can hold many signal types in working memory at once, surface cross-source patterns, and let you read the clusters and form your own interpretation.

To be clear, AI is the cross-signal-bringing tool, not the meaning-making tool. We still do the interpretation, the calls, the recommendations.

What futurecasting actually is

Futurecasting is a discipline that generates actionable strategic data for organisations by extrapolating from past and current large-scale trends in a given industry or operating sector. The output isn’t a prediction, it’s a set of plausible scenarios, each with named landmarks the organisation can watch for to determine which scenario is becoming the actual future. The point is to help the organisation prepare for, weather, or thrive through the futures it’s most likely to face.

Three things separate futurecasting from “trend-watching” or “predicting the future.”

Rigor. Futurecasting builds models with structured inputs across past, present, and projected signals. Trend-watching is reading newsletters and forwarding interesting articles. The difference is the same as between a research plan and “let me just chat with some users.”

Scenarios, not predictions. Futurecasting generates multiple plausible futures rather than one bet, because single-point predictions at strategic horizons are reliably wrong. The UXR analogue is the difference between a hypothesis you test and a guess you defend.

Revisitability. Futurecasting models are living documents you revisit quarterly, marking landmarks and updating scenario probabilities as events unfold. Trend reports are dead the moment they ship. The UXR analogue is the difference between a journey map you maintain and a journey map that lives forgotten on a Confluence page.

The reason user researchers are particularly well-positioned for this work is that each of the four points I made in the previous section maps to a specific stage of the futurecasting method. Past-behavior training maps to model-building. Defensible calls under uncertainty map to scenario generation. Signal-spotting maps to the quarterly revisit. Direct access to qualitative user truth runs through every stage.

A short example of what this could look like. A B2B SaaS researcher I worked with noticed across six months of interviews that buyers kept asking variants of the same question, “How do I know your AI features are actually saving us time?” That single weak signal, layered against support ticket data showing rising requests for ROI dashboards and a Gartner trend report on outcome-based pricing, became a futurecasting topic about how mid-market buyer trust in AI-generated work would shift between 2026 and 2029. The model produced three scenarios, the leadership team picked one as the North Star, and the product roadmap shifted from feature-led to outcomes-led six months ahead of any competitor in the space. That’s what this method produces when it’s done well.

If “be more strategic” has been the feedback you keep getting in performance reviews, and you’ve never had a clear path to actually do it, this is the path.

Below, I walk you through the full 5-stage futurecasting method I use as a researcher, with the templates, prompts, and worked examples you can copy this week:

• The futurecasting topic-selection framework (the 5 questions I ask before I commit to a topic, plus the worksheet I use to test whether my topic is actually viable)

• The 3-layer model template (past, present, projected, with the exact 8 signal categories I include and the spreadsheet structure I use to organise them)

• A step-by-step scenario generation process for your specific industry, with worked examples across B2B SaaS, healthcare, consumer fintech, and internal productivity tools

• The North Star workshop format (the 90-minute agenda, the slides, and the “likely vs desirable” voting move that surfaces the strategic disagreement nobody usually names)

• The landmark log template I use to revisit models quarterly and track which scenario is becoming the actual future

• 12 Bad/Better rewrites you can copy across topic, model, scenario, workshop, and revisit stages

• The minimum viable futurecasting practice (how to start with two hours next week)

If you’ve been waiting for a method that turns “more strategic” from a vague performance review note into a real practice, this gives you one.

Exclusively for paid subscribers

Read more

Subscribe now

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

**With the recent updates on Open AI privacy, I want to highlight that you do not have to use ChatGPT to achieve this. I have showcased ChatGPT because that’s where all my agents currently live, but I will be migrating them to other LLMs.

I’ve received a ton of questions recently on how UXRs can use AI more in a day-to-day workflow so I recorded this quick to showcase how creating and using specific AI agents can help with:

1. Offloading tedious/mundane tasks or starting with a draft versus a blank

2. Getting an additional perspective on something

3. Training others with more guardrails

If this looks like something that would benefit your team, happy to have a chat to see if I can help through a training workshop!

Let me know if you have any thoughts or questions below.

PS - If you need some help with prompt engineering, check out my AI Prompt Library for UXRs!

Happy researching!

Subscribe now

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

Most researchers I know have the same story. The same raised eyebrow. The same deep sigh before they open another LLM convo and brace for disappointment.

The first time I tried to use AI for something “simple,” I remember asking it to help me dissect a stakeholder brief. I pasted the vague, chaotic message, something along the lines of “We need to test the new dashboard design before Friday; can you put something together?” and waited for help.

What I got back looked like someone had skimmed a UX blog from 2012 and stitched together a few polite sentences. It read like a student trying to impress their professor without actually doing the assignment. No context. No understanding of the politics behind the request. No reading between the lines. Definitely no sense of the real decision hiding underneath the pretty words.

The problem is that we’ve been throwing AI at UXR tasks with the same energy we bring to reheating leftover lunch. Fast. Distracted. Half-formed prompts that barely capture what we actually need. Then we blame the AI when it hands back something flat, vague, or straight-up wrong.

Most UXRs are stuck in this loop:

• You give AI a tiny prompt.

• It gives you a tiny answer.

• You rewrite everything yourself.

• You decide AI isn’t ready.

• Then you go back to doing everything the slow way.

But, at the same time, you really have been burned.

You’ve tried using AI to:

• Clean up messy notes

• Summarize a long research plan

• Rephrase an insight for an exec

• Draft a kickoff email

• Clarify a brief written by a PM who sprinted through it between meetings

And the output felt like it came from someone who wasn’t in the room with you.

I’ve spoken to senior UXRs in fintech, SaaS, marketplaces, health tech, people who run teams, shape roadmaps, and handle cross-functional chaos every day, and every single one of them says something like:

“I can see the potential…but I don’t trust it.”

Not because AI is bad.

But because nobody taught UXRs how to use AI in a way that respects the complexity of our work. We didn’t get training.

We’re self-teaching in the middle of deadlines. We’re experimenting with prompts in between interviews. We’re trying to make sense of output that feels helpful one minute and deeply misguided the next.

AI becomes incredibly powerful for researchers once you give it the kind of direction your craft already relies on which is precision, context, constraints, intention, and the decision you’re supporting.

The magic doesn’t come from the model. The magic comes from your brain, paired with a structure that helps the AI act like a competent partner instead of an overeager intern.

Most researchers give up after a few half-hearted prompts. You ask something generic. It spits out something shallow. You move on. It’s not that AI can’t help you think better, it can, but only if you know how to push it.

Now we’re going to walk through the entire research process, from messy stakeholder kickoff to crisp, confident insights, and turn AI into the kind of co-pilot you’ve wished for since your first week as a researcher.

Why Pancake Prompts Fall Flat

If you’ve ever asked AI for help and felt mildly offended by the output, you’re not alone. Most researchers start with tiny prompts, get tiny answers, and assume the model just isn’t good enough. It’s the same energy as handing someone a sticky note that says write the whole report for Monday? and expecting them to read your mind, decode your org politics, and magically land on something useful.

The problem isn’t the AI. The problem is the prompt.

I know that sounds like the kind of patronizing advice thrown around LinkedIn, but stay with me. I spent months testing how UXRs actually prompt AI across dozens of real projects, interviews, surveys, strategy sessions, prototype tests, you name it, and most of the prompts UXRs write fall into the same patterns:

1. The “do everything for me” prompt

Example: “Write a usability test.”

What the AI hears: “Guess wildly.”

2. The “here’s a crumb, bake a cake” prompt

Example: “Help me write a kickoff doc.”

What the AI hears: “Please hallucinate intentions for me.”

3. The “I’ll tell you the task but not the stakes” prompt

Example: “Suggest tasks for a survey.”

What the AI hears: “Throw generic content at the wall.”

When you feed AI a prompt that thin, you get output that reads like the UX equivalent of a cookbook written by someone who has never eaten food. Lacking any awareness of real-world messiness.

AI has no idea what you actually care about unless you tell it.

And UX research is built on a whole lot of context:

• Why the team wants this research

• What decision sits behind the request

• Who’s pushing for speed

• What’s riding on the outcome

• What happened last time someone skipped research

• Who will use the insights

• What the constraints look like

• Which trade-offs matter

• What business metric is at stake

• How much is already known

• What’s being assumed without evidence

When your prompt doesn’t include these pieces, you’re asking an AI model to work blindfolded. I started experimenting with a completely different approach: stop treating AI like a vending machine, and start treating it like a very fast, very literal junior researcher who needs a real brief.

This is where the FAST model came from. A simple four-part structure that upgrades almost any prompt instantly.

Below, I walk you through the exact system that turns AI from “overeager intern” into a reliable research co-pilot:

• The FAST model (the 4-part prompt structure that fixes pancake prompts instantly)

• Before/after examples that show what “good” looks like

• Copy-paste prompts for kickoff, decision-mapping, risk surfacing, and assumption-breaking

• Mid-study checkpoint prompts to stop projects drifting off a cliff

• Synthesis guardrails so you get support without handing over judgment or raw data

Exclusively for paid subscribers.

Read more

Paid subscribers get the power tools: the UXR Tools Bundle wi…

Read more

Subscribe now

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

You know the drill: you’re managing five research projects, you just got pinged to “take a quick look” at a half-baked survey, and you’ve got feedback from 3,000 beta users, most of it vague, repetitive, or weirdly contradictory.

And yet, you’re still expected to be strategic, decisive, and insightful.

This guide is not about AI replacing user researchers, but about how to build a custom GPT agent that acts like a sharp, humble, unflappable thought partner. One that:

• Helps you clarify your thinking when your brain is fried

• Challenges you with smart questions (not just passive answers)

• Gets you out of blank-page paralysis

• Spots potential blind spots or contradictions before a stakeholder does

• Drafts starting points for tedious but necessary docs

Think of it as building your own research copilot. Not to do the job for you but to help you do it with more clarity, speed, and sanity.

This article is focused on creating a GPT through ChatGPT, because that is what I am most familiar with, but can be used on other LLMs as well.

Most researchers give up after a few half-hearted prompts. You ask something generic. It spits out something shallow. You move on. It’s not that AI can’t help you think better, it can, but only if you know how to push it.

I built an AI Prompt Library for user researchers who are tired of wasting time on useless outputs. These are the exact prompts I use when I want to:

• Pressure test my research questions

• Catch blind spots before they derail a study

• Frame insights so they actually land with leadership

• Prep for tough stakeholder conversations

• Kickstart deeper thinking when I’m stuck

It’s a working toolkit I’ve refined in real research projects with teams under pressure to deliver fast, smart, credible work.

If you want to stop messing around with AI and actually use it to get better at research, you can purchase the library below (starting at £297 for over 60 detailed prompts):

Get the UXR AI Prompt Library

What you’re actually building

You’re creating a custom GPT that works like an intern. It helps you move faster without cutting corners. It doesn’t replace your judgment or intuition but it gives you a solid first draft, a second brain, a structured way to think through messy tasks, or an outside perspective you may have missed.

It’s not here to “do research.” It supports the parts of your job that slow you down, such as writing from scratch, cleaning up notes, explaining something for the third time, or organizing chaos into something usable.

Your GPT should:

• Understand how research fits into product work

• Ask thoughtful questions when it doesn’t have enough info

• Stick to your preferred format (Docs, Markdown, Notion, etc.)

• Stay grounded in evidence

Step 1: Get Clear on What Your GPT Is Actually For

Before you start building anything, pause.

Most people skip this step and jump straight to writing prompts. Then they get frustrated when their GPT gives weird, useless responses.

That’s like hiring a new team member and just telling them, “Help with research.” You’d never do that.

This step is where you define the job. If your GPT is going to help you, it needs clear direction, just like an intern would.

You’re designing a GPT-powered agent that works like a trusted assistant:

• Helps you organize your thinking

• Reflects things back when you’re stuck

• Drafts first versions of the stuff you’d otherwise procrastinate on

• Challenges you when your plan is too big, vague, or stakeholder-pleasing

Let’s walk through how to define its job.

1.1 Pick a Specific Role

Trying to build a GPT that “helps with research” is like hiring someone and saying “your job is everything.” It won’t work.

Instead, think about a recent project where you said, “I wish I didn’t have to figure this out alone.”

That’s your first role.

Here are 6 realistic, high-leverage roles to choose from. These are built for busy UXRs dealing with limited time, pushy teams, and messy briefs.

Role 1: Study Goals & Scope Coach

Job: Help turn a vague or bloated request into a tight, meaningful set of research goals and define what’s out of scope.

Use this when: A PM says “We just need to understand what people want,” and you need to create something feasible without turning it into a 3-month epic.

What it might help you with:

• Turning broad goals into sharp questions

• Spotting red flags in scope creep

• Suggesting ways to align goals with actual product decisions

• Asking you clarifying questions when you’re stuck

Role 2: Method Matchmaker

Job: Recommend a suitable method (or hybrid) based on your study goals, team constraints, and timeline. Includes both rigorous and lean options.

Use this when: You’re toggling between three options—card sort? 1x1 interviews? diary study?—and need a sounding board to land on something defensible.

What it might help you with:

• Suggesting methods based on your real constraints

• Highlighting trade-offs you’re not considering

• Providing backup reasoning for your method when stakeholders push back

• Recommending ways to combine methods into a phased or scrappy approach

Role 3: Success Metrics Assistant

Job: Translate vague product or business goals into measurable indicators of research impact (or success). Not just “insightful findings” but change that matters.

Use this when: Your team says “We’ll know the research worked if people get it,” and you’re left guessing what “get it” means.

What it might help you with:

• Linking research goals to team or company metrics

• Coming up with proxy indicators (when hard metrics aren’t possible)

• Helping define what a “useful” outcome looks like ahead of the study

• Stress-testing your impact assumptions

Role 4: Stakeholder Pushback Coach

Job: Help you prepare responses to difficult stakeholder feedback: “Why are we doing this?”, “We already know this,” “Can we skip the research?”

Use this when: You’re emotionally exhausted from defending the value of your work and want help crafting a calm, credible, non-defensive reply.

What it might help you with:

• Drafting responses to common objections

• Helping you clarify the real resistance (budget? timing? ego?)

• Reframing research as a support tool, not a blocker

• Giving you talking points in plain language, not theory

Role 5: Communication Drafting Assistant

Job: Write first drafts of time-consuming or lower-stakes copy: intro emails to participants, internal study updates, screener survey logic, etc.

Use this when: You’ve got a dozen tabs open, a pile of notes, and zero time to sound polished.

What it might help you with:

• Writing readable stakeholder updates with different tones (PM, exec, designer)

• Turning bullet points into a screener survey

• Drafting opt-in emails or session invites

• Creating follow-up messages when sessions change or people ghost

Role 6: Business Alignment Sparring Partner

Job: Help you map research questions to business priorities, identify where the value is likely to show up, and anticipate what stakeholders care about.

Use this when: You’re asked to “just explore,” but you know the team will want something that ties back to growth, retention, or efficiency.

What it might help you with:

• Translating “user friction” into “potential revenue loss”

• Connecting product discovery to business OKRs

• Helping reframe user pain into decision-ready language

• Pressure-testing how your research supports real-world tradeoffs

Please don’t choose all of them. Start with one. Think about where you currently lose the most time or feel most unsure. That’s your GPT’s starting role.

1.2 Define Its Behavior: What This GPT Should Be Like

You’re now writing the personality and guardrails for your assistant. This is called the “system message.” It’s what runs under the hood, every time you use the GPT. This is where you train it to act like your ideal assistant.

Here’s a basic fill-in-the-blank version:

System Message Template

You are a [tone or seniority level] research thought partner who helps with [specific task].

You are [3 traits: sharp, structured, not too verbose].

You always:

• Ask clarifying questions before guessing

• Speak plainly and directly

• Offer options, not just single answers

• Reflect what I’ve said to check understanding

You never:

• Make assumptions without asking

• Speak like a marketer

• Try to sound clever

• Generalize without specific reasoning

Let’s look at a real example:

Example: Method Matchmaker System Message

You are a senior research advisor who helps select the right method for a study.

You are practical, thoughtful, and straight-talking.

You always:

• Ask about the project goals, timeline, and constraints

• Offer 2-3 possible methods with pros/cons

• Include a scrappy version and a gold-standard version

You never:

• Default to user interviews without justification

• Suggest things we can’t realistically run

• Use phrases like “delight” or “unlock”

You’ll paste this into the GPT builder when we get to Step 2. This is the blueprint for how your agent behaves.

1.3 Provide Context Every Time You Use It

This is the biggest mistake most people make. They drop in a vague prompt like, “What’s the best method for this?”

…and then wonder why the answer is useless.

GPTs aren’t mind readers. They need context to act like a partner. Here’s what good context includes:

• What the project is about (1-2 sentences)

• Who the team is

• What constraints you’re facing (time, people, budget)

• What stage you’re in (planning, revising, defending)

• What you want from the assistant (options? feedback? draft?)

Example: Good Setup Prompt

Read more

—

Alaine is an empathetic UX leader with a proven track record of driving user-centric strategies, adeptly managing teams, and delivering impactful research that drives business growth and strategic alignment.

In her role as a Research Manager at Dext, she oversees research delivery, strategy, and operational functions. With 12 years of extensive experience in user research and design, she is deeply passionate about leading and inspiring individuals while ensuring that customer insights remain at the core of product development.

In our conversation, we discuss:

• What happens when a six-person research team shrinks to one and how Alaine rebuilt from there.

• Why doing “more research” wasn’t the answer, and stepping back was the most strategic move.

• How to spot the right people to advocate for research, even if it’s not your direct manager.

• The messy reality of research democratization and what finally made it work.

• What it really means to operate as a business partner rather than a user advocate.

Some takeaways:

1. You can’t research your way out of a broken system. Alaine tried to do everything alone and quickly realized she was burning out while diminishing trust in research. The turning point came when she stepped back to understand what the business actually needed, then rebuilt with that in mind.

2. Get closer to product, not just users. Alaine shifted her focus toward building relationships with senior product leaders and learning how they think. Reporting into a VP of Product helped position research as part of the product org, not a separate function trying to fight for attention.

3. Strategic visibility creates pull, not push. Her first hires were two contractors focused on mission-critical work. Once stakeholders saw the quality and impact, demand for research grew naturally. From there, product teams started asking for more researchers, Alaine didn’t need to campaign again.

4. Democratization isn’t plug-and-play, it’s infrastructure. Initial attempts failed until she simplified tools, rewrote bloated processes, and treated it as a real change management project. Now, 30+ people can confidently run research with a central handbook and lightweight systems built around their needs.

5. Start with honesty, not idealism. The first step in rebuilding wasn’t a grand vision. It was getting brutally honest about how research was perceived across the company. Anonymous feedback and reflection helped clarify what role the business wanted research to play and that insight shaped every step forward.

Where to find Alaine:

• LinkedIn

Interested in sponsoring the podcast?

Interested in sponsoring or advertising on this podcast? I’m always looking to partner with brands and businesses that align with my audience. Book a call or email me at nikki@userresearchacademy.com to learn more about sponsorship opportunities!

The views and opinions expressed by the guests on this podcast are their own and do not necessarily reflect the views, positions, or policies of the host, the podcast, or any affiliated organizations or sponsors.

Stakeholder buy-in is a tale…well, a nightmare, as old as time. You run the research. You catch the cracks. You pull together quotes, clips, friction points, and five glaring moments of user confusion.

And then?

The meeting ends. Everyone goes back to business as usual. The roadmap stays exactly the same. And your work goes straight into the void…

Read more

If you want to see everything I post, subscribe below!

Subscribe now

This is a series on user research democratization — since this is a tough topic, there was way too much for one article. I will be writing this series and posting it over the next weeks and will edit this as I add to the series so you can easily navigate the different parts.

• Part 1: The Complex Landscape of Research Democratization (Free)

• Part 2: A Framework for Responsible Research Democratization (Paid)

• Part 3: Scaling research without sacrificing rigor (Paid)

Stop piecing it together. Start leading the work.

The Everything UXR Bundle is for researchers who are tired of duct-taping free templates and second-guessing what good looks like.

You get my complete set of toolkits, templates, and strategy guides. used by teams across Google, Spotify, , to run credible research, influence decisions, and actually grow in your role.

It’s built to save you time, raise your game, and make you the person people turn to.

→ Save 140+ hours a year with ready-to-use templates and frameworks

→ Boost productivity by 40% with tools that cut admin and sharpen your focus

→ Increase research adoption by 50% through clearer, faster, more strategic delivery

Grab the Everything UXR Bundle

You’ve made the leap and you’ve started democratizing user research. Stakeholders are getting involved, training programs are up and running, and suddenly you have more breathing room to focus on strategic work. Great, right?

Well, yes…and no.

If you’re anything like me, your journey probably started out promising. You saw stakeholders get excited about conducting research. They started running their own usability tests, sending out surveys, and occasionally producing some pretty solid insights. But somewhere along the way, you probably also encountered a situation where you had to bite your tongue and think:

“Wait, how did this insight even happen? That’s not what participants said at all.”

Sound familiar?

Maybe you noticed research being conducted without oversight or stakeholders accidentally twisting findings to fit their own narrative. Perhaps you’ve found yourself becoming more of a service desk, fielding endless requests to review interview guides, recruitment strategies, or analysis documents. (And, annoyingly, that’s exactly what you were trying to avoid in the first place.)

Democratizing user research is messy.

But that’s okay. You’re not alone, and this isn’t a sign of failure, just part of the process. After all, user research democratization is relatively new territory for most organizations. There isn’t a single team out there who hasn’t run into issues along the way.

By now, you already know the value democratization can provide, but you’re probably also realizing it comes with a host of challenges. My goal is to help you respond effectively to these inevitable bumps and frustrations.

In this article, I’ll share concrete strategies, realistic examples, and actionable frameworks for responding to the most common issues you’ll face while democratizing user research. I’ll walk you through how to proactively identify potential pitfalls, tackle them when they arise, and adjust your processes so they don’t become recurring headaches.

Together, we’ll cover how to:

• Spot early warning signs of democratization going sideways (before it’s too late).

• Establish clear, realistic guidelines that stakeholders can actually follow.

• Handle common pitfalls like misinterpreted insights, stakeholder overconfidence, and lack of oversight.

• Build a straightforward system to respond to ethical concerns and compliance risks swiftly.

• Navigate pushback from stakeholders or leadership who might question the value and role of user research altogether.

Democratization isn’t about handing over your expertise, it’s about helping your organization scale research responsibly.

Identifying Common Issues in UXR Democratization

When I first began democratizing user research, I felt like I’d found the solution to all my problems. Stakeholders running their own usability tests? Great! Product teams collecting their own data? Even better! I finally had more bandwidth to tackle strategic initiatives.

But it wasn’t long before the cracks started showing. Teams got excited, but enthusiasm quickly turned into confusion, misinterpretation, and occasionally, chaos.

Democratization brings enormous potential, but it also introduces specific pitfalls, some that are obvious, and others you’ll only discover the hard way. Let’s break down the most frequent challenges into four clear categories. I’ll share exactly what these problems look like (so you can spot them early), along with real examples from my experience.

Quality Issues

Let’s start here, because quality is often the first place democratization breaks down. Remember, not everyone conducting research is trained or experienced. When research quality slips, insights become unreliable, and stakeholders may lose faith in the value of research altogether.

Poorly constructed research (bias, flawed methodologies)

Stakeholders designing surveys or interviews full of leading questions. For example, a product manager once created a survey where literally every question began with: “How excited would you be…?” Naturally, all answers were positive, but completely useless for decision-making.

Early warning signs to look out for:

• Stakeholders sending research scripts or surveys to participants without your review.

• Constant use of leading, closed-ended, or ambiguous questions.

• Overconfidence in their approach despite lack of formal research training.

Misinterpretation or overgeneralization of findings

A single positive comment from one usability participant suddenly becomes proof that “users love this feature.” Once, I saw an entire roadmap change direction based on a single, misinterpreted piece of feedback from a friend of the product manager.

Early warning signs to look out for:

• Reports or presentations where quotes are cherry-picked and findings feel suspiciously aligned to stakeholders’ initial beliefs.

• Sweeping conclusions based on small sample sizes like “Users universally prefer…”

Operational Issues

Even if the research itself is decent, operational issues can still cause headaches. When different teams run their own studies without clear documentation or coordination, chaos ensues, resources get wasted, and valuable insights disappear into black holes.

Inconsistent or incomplete documentation

Stakeholders conducting studies but never logging their insights anywhere. I’ve had moments of deja vu when two teams ran essentially identical research simply because no one documented the first team’s findings.

Early warning signs to look out for:

• Multiple teams are unaware of research others have already completed.

• Missing context when stakeholders share findings (“Where’s the original data for this claim?”).

Fragmented repositories or duplicated efforts

Research scattered across Slack threads, personal Notion pages, random Google Drive folders, or worse, buried in personal email inboxes. At one company, we discovered four separate research repositories existing simultaneously (all containing different research!).

Early warning signs to look out for:

• Stakeholders constantly asking, “Where can I find research on X?”

• Duplicate requests for similar research studies from different teams.

Ethical and Compliance Issues

These are the scariest because they can have serious legal and ethical consequences. Non-researchers often lack the training to understand the nuances of consent, data protection, or privacy regulations.

Mishandling of sensitive data or consent processes

Stakeholders recording video sessions without participants’ explicit consent, or worse, sharing sensitive participant data openly across Slack or email. I’ve personally had to step in and remind teams that recording without clear consent isn’t just unethical, it’s illegal.

Early warning signs to look out for:

• Stakeholders unsure how to phrase consent forms or handle participant questions about data usage.

• Unexpected use of unapproved recording or recruitment tools.

Privacy concerns and non-compliance with regulations

Teams unintentionally violating GDPR or other privacy regulations by storing identifiable data improperly or failing to anonymize sensitive information. I’ve found participants’ personal details casually pasted into public team channels. Yikes!

Early warning signs to look out for:

• Stakeholders asking basic questions about participant data storage or privacy (“Wait, how long should we keep this data?”).

• No centralized guidance or documentation around compliance and privacy.

Cultural and Organizational Issues

Finally, democratization issues aren’t always technical—they’re often about people and culture. Resistance and misunderstanding about the role and value of research can derail even the best-laid plans.

Resistance from stakeholders or teams

Teams who either dismiss democratized research entirely or, worse, actively undermine it. I’ve encountered stakeholders who insisted, “We’ve always made decisions without research, why bother now?”

Early warning signs to look out for:

• Teams consistently questioning the validity of democratized research findings.

• Minimal engagement with or outright avoidance of your training efforts.

Devaluing professional research roles

Stakeholders assuming anyone can do research (thus dismissing your expertise). Once, an executive confidently proclaimed, “Why do we need researchers at all if product managers can do interviews?”

Early warning signs to look out for:

• Reduced hiring budgets or stalled plans for growing the research team, justified by “democratization is handling it.”

• Researchers are asked less strategic questions and expected more often to simply “check work.”

Reading through these issues, you might be nodding vigorously because you’re already experiencing one (or all) of them. I promise you’re not alone. Democratization, like most things in user research, isn’t an all-or-nothing game. It’s a careful balancing act.

Now that we’ve identified the most common pitfalls, the next step is learning how to proactively monitor and respond to them quickly and effectively, minimizing disruption and maximizing value. We’ll dive deeply into this in the next sections, covering concrete strategies and frameworks you can implement immediately.

But first, take a moment. Reflect on your organization. Which of these issues resonate with you the most? Which can you already see emerging? Awareness is the first step towards effective action.

Establishing a Proactive Monitoring System

Democratizing research isn’t “set it and forget it.” I learned this lesson early on, mostly by ignoring it until small problems became big headaches. If you don’t regularly check on your democratized research model, quality can slip, small errors will grow, and teams might stop trusting research altogether.

Think about it like a garden. You wouldn’t plant seeds, walk away, and expect flowers to bloom perfectly months later, right? A good garden needs consistent attention, watering, pruning, checking for weeds. Similarly, democratized research needs constant care and monitoring.

Let’s dig deeper into practical, actionable ways you can set up an effective monitoring system that catches issues early before they spiral out of control.

Implement Regular Quality Audits

Regular quality audits are your first line of defense. They sound boring, I know, but trust me: you’ll be amazed (and maybe alarmed) at what you uncover.

Quarterly reviews of randomly selected democratized projects

You can’t audit everything, but periodic spot-checks help you see reality clearly—without rose-colored glasses. Doing this regularly means you’ll quickly spot patterns or repeated issues and can jump on them before they spread.

How I do this:

Once a quarter, randomly choose a handful of studies conducted by non-researchers. I pick studies of different types, surveys, usability tests, quick interviews, to get a full picture of what’s happening.

Questions I ask when auditing:

• Were research goals and hypotheses clearly defined?

• Was the participant recruitment unbiased and appropriate?

• Did stakeholders ask leading or biased questions? (Spoiler: they often do.)

• Were conclusions properly drawn from data, or were insights exaggerated and cherry-picked?

During one audit, I discovered a marketing team was using highly biased questions in their surveys, questions like, “How much better is this feature?” instead of neutral language. Catching this early allowed us to quickly retrain the team before it became a bigger issue.

Define clear quality metrics and review standards

You can’t measure quality without standards. Clearly defined metrics help stakeholders know exactly what’s expected and give you a fair way to judge quality.

Metrics I typically use:

• Participant quality: Are participants representative of our actual users, or just conveniently available friends and colleagues?

• Question quality: Are questions unbiased and open-ended, or are they designed to confirm pre-existing beliefs?

• Insight quality: Are insights supported by clear evidence, or are they vague conclusions without data to back them?

For example, I created a simple, transparent scorecard stakeholders could use to self-assess before submitting their findings. It forced stakeholders to be thoughtful about their approach, and audits became faster since basic quality improved dramatically.

Set Up Stakeholder Feedback Loops

Research democratization relies heavily on stakeholders’ willingness and ability to do good work. But stakeholders won’t always volunteer when they’re struggling—sometimes due to pride, confusion, or even embarrassment. So, it’s critical to proactively reach out and give them a safe, easy way to provide feedback.

Regular surveys and interviews to understand stakeholder challenges

Regular check-ins help surface problems stakeholders might never mention unprompted. You need clear visibility into their frustrations, struggles, and successes.

How I do this:

• Quick quarterly surveys asking about pain points, confidence levels, and the types of research they’re struggling with most.

• Short interviews or casual coffee chats to dive deeper into survey findings, clarifying ambiguous feedback.

I once discovered through a quick stakeholder survey that teams avoided our research repository because they found the tagging system confusing. This simple insight led to a clearer system that increased adoption and reduced duplicated work.

Implement an anonymous feedback channel

Not everyone feels comfortable openly sharing their struggles, especially if it feels critical of you or your team. An anonymous feedback option ensures honest, candid responses.

How I do this:

I use a simple Google Form, clearly labeled as anonymous, sent out monthly. I ask stakeholders questions like:

• “What part of the research process feels most challenging or unclear?”

• “Are there barriers preventing you from using the research repository effectively?”

For example, anonymous feedback once revealed stakeholders were hesitant to ask for help, fearing they’d seem incompetent. That led me to set up casual “office hours” to normalize asking for support, quickly solving that issue.

Use Data to Track Common Pitfalls

Tracking common pitfalls systematically helps you catch trends early and tackle root causes proactively rather than continuously putting out fires.

Patterns in methodology mistakes

Repeated mistakes indicate a systemic issue, usually either training gaps or unclear resources.

During quarterly audits, I categorize common methodology issues. If the same mistakes pop up repeatedly, like consistently biased questions, I know stakeholders need refresher training.

For example, I noticed stakeholders repeatedly misunderstood when to use open-ended vs. closed-ended questions. A simple, targeted training module completely turned this around, improving question quality across all future studies.

Frequent ethical oversights or repository usage issues

Ethical issues (like improper consent forms or privacy mistakes) aren’t just embarrassing, they’re serious risks. Catching these trends early is critical. Similarly, repository issues can massively undermine the value of your democratization program.

How I track this:

• Logging ethical oversights found during audits or stakeholder feedback sessions.

• Tracking repository issues: duplicated studies, untagged reports, or documents saved in personal drives instead of central repositories.

After noticing repeated confusion around participant consent forms, we created a simple, required training video specifically on consent and privacy. Issues dropped significantly after stakeholders had clearer guidance.

Establishing a proactive monitoring system takes work. But believe me, the payoff is huge. You’ll quickly move from firefighting mode, always scrambling, to proactive mode, where you anticipate problems before stakeholders even realize they’re having them.

Your stakeholders will appreciate clear guidance, support, and continuous improvements, and you’ll sleep better knowing your democratization model isn’t secretly falling apart behind the scenes.

Remember: democratized research is a powerful tool, but only if you’re consistently looking after its health. Do your future self (and your stakeholders) a favor by setting up a proactive monitoring system today.

Responding to Quality Issues

Let’s talk about something uncomfortable but inevitable. At some point, stakeholders conducting research will produce low-quality work. And it will make your researcher heart sink when you spot biased surveys or usability tests that lack even basic structure. Trust me, I’ve been there, probably more often than I care to admit.

While it’s tempting to panic or start pulling your hair out, what’s more effective (and sanity-saving) is having clear, actionable strategies ready to respond quickly and productively.

Here’s exactly how I tackle these challenges, complete with real-life strategies you can steal immediately.

Issue: Stakeholders Producing Low-Quality Research

Low-quality research isn’t just frustrating, it actively undermines the credibility and value of user research in your organization. Once stakeholders (or worse, leadership) start questioning the accuracy or value of insights, rebuilding that trust is painfully slow.

Here’s exactly what I recommend doing to prevent, and quickly respond to, quality issues:

Response Strategy #1: Implement Mandatory Review by Trained Researchers

A mandatory review acts as a clear gatekeeper, preventing poorly constructed research from ever reaching stakeholders or decision-makers. It gives your research team a chance to catch and correct mistakes before any damage is done. Here’s how to do it:

• Clearly communicate expectations. Let stakeholders know upfront that every survey, usability test plan, or research guide needs to be reviewed by a trained researcher before it goes live.

• Build an easy submission process. Create a simple, low-friction submission workflow (Google Form, Notion page, or Slack channel) to submit research for review.

• Define a realistic review timeline. Provide a transparent turnaround time (mine is usually around 2–3 days). Stakeholders know exactly when they’ll get feedback and plan accordingly.

We once had a marketing team write a customer satisfaction survey full of leading questions (“How much do you love this feature?”). Thankfully, our mandatory review caught it in time. Instead of panicking, we scheduled a quick 20-minute call, rewrote the questions together, and ended up with meaningful insights rather than biased fluff.

Response Strategy #2: Develop a “Research Quality Checklist” for Stakeholders

When stakeholders have clear criteria to measure their research against, quality dramatically improves, even before it hits your desk for review. It helps stakeholders internalize best practices and self-correct earlier in the process.

My “Research Quality Checklist” typically includes points like:

• Objective clarity: Are research goals clearly defined and focused?

• Bias check: Do questions avoid leading language, assumptions, or confirmation bias?

• Participant recruitment: Is the sample diverse, representative, and unbiased?

• Insight integrity: Are insights backed by direct evidence and clearly linked to the original research question?

I hand stakeholders this checklist upfront (and repeatedly remind them to use it!).

A design team I worked with was notorious for usability tests with ambiguous tasks. After introducing the checklist, they started explicitly defining clear objectives and scenarios for testing. Sessions became consistently productive, and I spent far less time rewriting their scripts.

Response Strategy #3: Offer Focused, Targeted Training Sessions Addressing Skills Gaps

When you see repeated quality issues, it’s usually because stakeholders simply don’t know better (or forgot your previous training). Addressing specific, targeted skill gaps in short, practical training sessions can completely transform research quality. You can do this by:

• Identifying skill gaps: During reviews, audits, or feedback, note exactly which mistakes appear repeatedly.

• Scheduling short, targeted sessions: Run focused, bite-sized workshops on topics like “Unbiased Survey Writing” or “Structuring Effective Usability Tests.”

• Providing clear, actionable templates: Always pair your training with ready-to-use templates or examples to reinforce what they’ve learned.

Recently, we recently noticed a high rate of biased questions in stakeholder surveys (think: “Why is this feature so great?”). To fix this, we held a 90-minute workshop specifically on unbiased question-writing, complete with hands-on exercises, clear templates, and concrete before-and-after examples. The next set of surveys we reviewed showed immediate improvement, with questions that produced genuinely insightful data.

Stakeholders doing research will always come with some degree of quality risk. It’s inevitable. But instead of despairing, you can prepare proactively with these clear, actionable response strategies:

1. Mandatory researcher reviews catch errors before they do damage.

2. Research quality checklists empower stakeholders to self-correct before issues arise.

3. Focused, targeted training sessions tackle recurring problems at the source.

In my experience, clearly addressing quality issues head-on, and calmly guiding stakeholders toward improvement, does wonders for building trust, respect, and long-term buy-in for research across your organization.

Responding to Operational and Documentation Issues

If you’ve democratized research even slightly, you’ve probably encountered this headache, a fragmented documentation, inconsistent reporting practices, and duplicated insights scattered across every possible tool your company uses. You know the drill, one team has their findings in a Slack thread, another in Notion, and a third stored them in a random Google Doc no one can find. Suddenly, your organization’s insights resemble a digital scavenger hunt rather than a reliable repository of knowledge.

I’ve been there (and if I’m honest, I might even have caused it once or twice). The good news is, it’s fixable if you take clear, actionable steps early.

Issue: Insights scattered across multiple systems, duplicated efforts, repository inefficiencies

When documentation gets fragmented, insights become unreliable—or worse, forgotten. Stakeholders waste precious time chasing down the same insights repeatedly, duplicating studies, or making decisions without the benefit of existing research. This doesn’t just hurt your credibility, it also wastes everyone’s time.

Response Strategy #1: Clearly define and communicate documentation requirements

Documentation chaos usually starts because people aren’t clear on exactly what’s expected of them. Having crystal-clear documentation requirements removes ambiguity and creates consistent practices across teams:

• Create a standardized reporting template. Provide a structured template everyone uses. Include clear sections for research objectives, methods, key findings, supporting evidence, and next steps. (I usually put mine in Notion or Airtable.)

• Document exactly where insights must live. Pick one central tool (Condens, Airtable, or even a dedicated Notion workspace) and explicitly mandate that all final insights must go there, no exceptions.

• Communicate repeatedly (and kindly). Share your documentation guidelines multiple times: in training, Slack announcements, team meetings, and onboarding sessions. Don’t assume stakeholders remember after seeing it once.

When my last organization faced insight chaos, we standardized all reports into an Airtable template with clear sections. After just a few weeks (and gentle reminders), everyone started reliably documenting insights in the same place, dramatically reducing confusion and duplication.

Response Strategy #2: Regularly audit repository use, emphasizing accountability

When stakeholders know documentation is being actively monitored, compliance skyrockets. Regular audits reveal who’s using the repository correctly, who needs extra help, and who might just need a polite reminder. Here’s how to run effective repository audits:

1. Schedule quarterly repository audits. Pick random samples of research documentation across teams and evaluate them for completeness, clarity, and proper storage.

2. Create a simple scoring rubric. Develop straightforward evaluation criteria (correctly documented objectives, clearly defined next steps, insights properly tagged).

3. Share audit results transparently. Present audit results openly and clearly, recognizing teams with excellent documentation, and offering practical, supportive feedback to those lagging.

We introduced quarterly repository audits at one company after finding insights scattered across Slack, Notion, and Google Drive. At first, it felt awkward, but after sharing the first audit results transparently (with plenty of positive shoutouts), stakeholders got competitive (in a good way) about improving their documentation. Within two quarters, compliance improved by over 70%.

Response Strategy #3: Consolidate insights in a centralized, accessible, and easy-to-use system

A centralized, easy-to-use repository removes friction, making it effortless for teams to store, find, and use insights. If using your documentation system feels like pulling teeth, stakeholders simply won’t do it. Make it easy, and they’ll flock to it. Here are some steps to consolidate effectively:

1. Pick one intuitive, flexible tool: Choose something that stakeholders genuinely like using. I really recommend tools like Condens for a repository.

2. Clearly structure and tag insights. Use a simple tagging system (by project, team, method, or persona) to make insights instantly discoverable.

3. Provide training and onboarding support. Hold quick, interactive onboarding sessions showing stakeholders exactly how to use your chosen repository tool (trust me—this 30-minute training pays dividends!).

I’ve successfully used Condens to centralize fragmented research. We ran quick onboarding sessions, developed a consistent tagging system (by project, research method, and audience), and stakeholders loved the ease of searching and sharing insights. The system quickly became indispensable, solving our fragmentation issue practically overnight.

Response Strategy #4: Appoint a dedicated research operations owner or coordinator

Having someone specifically accountable for research operations ensures that documentation and repositories don’t slip through the cracks as everyone’s “second job.” A dedicated owner actively manages the system, provides support, runs audits, and makes continuous improvements.

1. Clearly define responsibilities. Make sure the operations owner knows exactly what’s expected: managing documentation guidelines, conducting audits, onboarding new stakeholders, and troubleshooting problems.

2. Empower them to drive accountability. This person should regularly check in with stakeholders, offer support proactively, and gently hold teams accountable when they slip.

3. Set measurable KPIs. Metrics might include repository compliance rates, reduced duplication, or stakeholder satisfaction with documentation processes.

We assigned one senior researcher as our dedicated research ops coordinator for documentation. She actively supported stakeholders, ran the audits, and even held open “office hours” for documentation questions. Our compliance jumped almost immediately and stakeholders genuinely appreciated the dedicated support.

Scattered documentation and inefficient repositories don’t fix themselves. But with clear, supportive, and structured interventions, you can turn chaos into clarity:

• Define and communicate clear documentation requirements (think easy templates, simple instructions).

• Regularly audit repository usage to drive accountability (friendly reminders work wonders!).

• Consolidate your insights in a centralized, user-friendly system (the right tool makes compliance painless).

• Appoint someone specifically accountable for research operations (this isn’t a side hustle, give it dedicated attention).

By tackling these operational issues directly (but kindly), you’ll improve compliance, reduce duplication, and regain trust in the research process all while saving your own sanity.

Responding to Ethical and Compliance Issues

Ethics and compliance can feel like the least exciting part of user research, but if stakeholders mess it up, things can go downhill fast. Mishandled consent or poorly managed sensitive data isn’t just inconvenient; it can trigger severe regulatory issues, damage customer trust, and genuinely harm your organization’s reputation.

I’ve seen stakeholders accidentally skip consent because they didn’t fully understand the implications, or casually store sensitive participant data in random documents.

In fact, I messed up myself big time because I was rushing and had a very minor compliance issue when recruiting participants.

It happens more often than you’d think.

Issue: Stakeholders mishandling consent or sensitive user data

When consent and data handling slip through the cracks, your organization can quickly find itself facing legal issues or, at best, seriously damaged trust with participants. Ethical missteps can even lead leadership to question whether democratization was a good idea in the first place. We want to avoid this scenario completely.

Here’s exactly how you can make sure ethical standards stay airtight and actionable:

Response Strategy #1: Require explicit ethical training for anyone conducting research

Most ethical mistakes happen simply because stakeholders don’t know what they don’t know. Clear, explicit ethical training ensures they fully understand their responsibilities, without making ethics feel scary or bureaucratic. Here is how to make ethical training actionable and practical:

• Make it short, clear, and mandatory. Run a straightforward 1–2 hour training that covers participant consent, data protection basics, and the key dos and don’ts of ethical research.

• Incorporate real-life scenarios. Use concrete examples and scenarios (ideally from your own organization or similar ones) to highlight common mistakes and exactly how to avoid them.

• Include an interactive quiz or knowledge check. Ensure stakeholders genuinely grasp the content with a quick quiz at the end. No stress, but it reinforces the essentials.

At my previous company, we rolled out a simple mandatory ethics training module with practical scenarios (“You recorded a usability test—where can you store the recording?”). Stakeholders quickly understood exactly what they could and couldn’t do, and ethical mistakes dropped sharply.

Response Strategy #2: Establish a dedicated compliance checkpoint in research workflow

Embedding a compliance checkpoint directly into your research workflow ensures ethical considerations aren’t forgotten in the rush to launch research. It puts ethics front and center at exactly the right moment. Here are some steps you can follow:

1. Build it into your research process. Clearly mark a compliance checkpoint before any research goes live, this could be a checkbox in your research approval form or a step in your research tool’s workflow.

2. Provide a simple compliance checklist. Include essential items like: consent form completed, sensitive data storage identified, participant anonymity measures in place.

3. Have clear escalation paths. Clearly communicate who stakeholders should reach out to if they’re unsure about compliance (typically you or your designated compliance owner).

For example, I introduced a mandatory “compliance check” step in our research approval workflow. Stakeholders simply couldn’t launch studies without confirming that they’d reviewed the compliance checklist. It only took an extra few minutes, but compliance rates soared immediately.

Response Strategy #3: Assign ethics reviews for all research involving sensitive data

Sensitive data, like health records, financial information, or private conversations, requires special handling. An explicit ethics review ensures risks are identified early, avoiding serious missteps. Here’s how to run one:

1. Clearly define what counts as sensitive data. Explicitly state categories (health data, financial information, personally identifiable information, etc.) that trigger an ethics review.

2. Create a quick ethics-review template. Include straightforward questions stakeholders must answer questions like: “How is data anonymized?” “Where will data be stored?” “Who can access it?”

3. Appoint an ethics review point-person. Designate someone trained in ethical practices who stakeholders can approach for quick ethics checks. This could be you or another senior researcher.

Response Strategy #4: Clearly document consent guidelines in easily accessible formats

If your consent guidelines are buried in dense documents or scattered in multiple locations, stakeholders simply won’t use them. Accessible, clearly documented guidelines make ethical compliance effortless. You can do this by:

• Creating simple consent form templates. Provide easy-to-use, clearly worded templates stakeholders can quickly adapt for their studies.

• Document exactly how and where to store consent: Give clear instructions about where stakeholders should keep consent forms.

• Make guidelines easily findable. Store ethical documentation prominently in your centralized research repository (Notion, Airtable, Condens), and pin it in Slack or internal knowledge tools.

At one org, we noticed incomplete consent forms happening frequently. We created simple consent-form templates stakeholders could easily customize, clearly communicated exactly where to store these forms (in a secured folder), and pinned these instructions in Slack. Compliance issues drastically reduced.

Ethical research isn’t just about rules, it’s about trust. By proactively embedding these clear, actionable steps into your democratized research workflow, you protect your organization, empower your stakeholders, and elevate the overall credibility of user research.

Responding to Cultural and Organizational Issues

User research democratization can quickly become contentious if stakeholders feel uneasy, resistant, or worried about the value of professional researchers diminishing. You may find yourself fielding awkward comments like, “So, anyone can do user research now?” or even dealing with stakeholders quietly conducting rogue studies out of misunderstanding or mistrust.

I’ve personally experienced team members and researchers who were genuinely anxious that democratizing research meant devaluing their hard-earned expertise. It’s a valid concern. But these cultural challenges are solvable if you’re proactive, transparent, and empathetic from the start.

Issue: Resistance from teams or concerns over the devaluation of UX researchers

Resistance isn’t just annoying, it can seriously derail your democratization efforts. If your teams don’t fully understand or support the democratization model, you’re setting yourself up for friction, confusion, and mistrust. People may become protective over their roles, defensive about expertise, or feel threatened. (Not a fun scenario.)

Let’s dive into clear, actionable strategies to prevent (or quickly fix) these cultural challenges.

Response Strategy #1: Clearly communicate the role and value of professional researchers

The root of resistance often comes down to misunderstanding or fear about roles changing. Clearly defining the ongoing critical role of professional researchers ensures everyone feels secure, respected, and confident about their place in the new model. Here are some ways to do that:

• Schedule an “All-hands” or team-wide meeting. Clearly explain the democratization strategy, emphasizing the unique skills, deep expertise, and value professional researchers bring (generative research, complex studies, research synthesis).

• Create a simple visual or diagram (use a slide, Miro, or Notion). Illustrate clearly what stays researcher-led vs. what stakeholders can lead—make this easily shareable.

• Send regular updates (monthly or quarterly emails/Slack posts). Reinforce your researchers’ critical role through clear examples, celebrating their deeper research contributions and impact.

When I first introduced democratization in my team, some researchers expressed concern about their roles. I immediately scheduled a short session clearly articulating researchers’ continuing responsibilities, highlighting strategic research, synthesis, and generative studies. Resistance immediately softened.

Response Strategy #2: Reinforce the complementary nature of democratized and dedicated research efforts

Stakeholders often worry democratization means professional research is less valuable. Clarifying how democratized research complements (rather than replaces) dedicated researchers ensures everyone sees democratization as collaboration, not competition. Some steps on how to do this include:

• Running interactive training sessions. Pair researchers and stakeholders together to illustrate how professional researchers add value by mentoring, reviewing, and guiding research quality.

• Highlighting concrete examples of collaboration. Regularly showcase successful case studies where democratized research fed into, and was improved by, professional researcher insights.

• Implementing regular pairing or mentorship sessions. Create structured opportunities for researchers and stakeholders to collaborate regularly (office hours, research pairing), reinforcing the complementary relationship.

At one org, to reduce friction, we set up weekly “Research Office Hours,” explicitly pairing researchers with stakeholders. Stakeholders quickly saw how professional researchers helped deepen insights, and researchers felt valued for their expertise.

Response Strategy #3: Showcase successful democratization examples internally

Resistance often stems from skepticism or uncertainty. Showing successful democratized research examples within your organization provides proof democratization works and can win skeptical teams over quickly:

1. Start a monthly democratization showcase. Briefly highlight one or two successful democratized studies in a short monthly update (email, Slack, newsletter, or Condens).

2. Ask stakeholders to share their own experiences. Invite stakeholders who’ve successfully run studies to speak briefly at team meetings or research gatherings about their positive experiences.

3. Create a democratization “wins” page. Use Notion, Condens, or another internal tool to collect examples of successful democratized studies, clearly summarizing outcomes and stakeholder testimonials.

We created a monthly Slack thread called “Democratization Wins” where stakeholders shared their successful usability tests and how professional researchers improved their work. Skeptical teams quickly became more open-minded.

Response Strategy #4: Set clear boundaries around what remains researcher-led and what is democratized

Ambiguity creates anxiety. Clearly defined boundaries reassure researchers that their expertise isn’t being replaced and help stakeholders feel clear about exactly where their responsibilities begin and end. Here are some boundaries to try:

• Create and distribute a simple one-pager or decision tree. Explicitly outline exactly which studies stakeholders can lead (usability tests, surveys) and those strictly researcher-led (generative, strategic studies).

• Communicate boundaries clearly and repeatedly. Reinforce these boundaries in your trainings, during office hours, and via regular communications.

• Include clear escalation paths. Clearly state who stakeholders should approach if they are unsure if a study should be researcher-led.

The key to addressing cultural issues is proactive transparency. With clear communication, consistent reinforcement, and tangible examples, you’ll quickly move your stakeholders from resistant to supportive, strengthening your democratization efforts and your organization’s trust in user research.

Creating an Issue Escalation and Resolution Framework

At some point during user research democratization, things will inevitably go wrong. Maybe stakeholders release a biased survey, sensitive data gets mishandled, or critical findings get misinterpreted, causing confusion across teams.

When these issues arise, your response matters—a lot. It not only influences the immediate problem but also sets a precedent for how seriously your organization takes user research and its credibility.

Having an issue escalation and resolution framework in place might sound overly corporate or bureaucratic. This structure will save you from confusion, anxiety, and constant firefighting down the line.

Step 1: Establish Clear Escalation Paths

When something goes wrong, stakeholders should know exactly who to contact, who will handle it, and how quickly they’ll hear back. Without this clarity, issues get lost, ignored, or handled inconsistently. Here’s how to set this up:

1. Define severity clearly and simply. Start by categorizing issues into three easy-to-remember groups:

   1. Minor: Small mistakes with limited impact (like a single biased question on a usability test).

   2. Major: Issues happening repeatedly or those seriously affecting decisions (stakeholders repeatedly misunderstanding findings).

   3. Critical: Any ethical or compliance violations (like missing consent forms or privacy breaches).

2. Identify clear ownership. Clearly assign who’s responsible at each level, for example:

   1. Minor issues → Research operations coordinator (resolved in 1–2 days)

   2. Major issues → Senior or Lead UX Researcher (response within one day, thorough follow-up within a week)

   3. Critical issues → Head of Research or Data Compliance Lead (immediate resolution within hours)

3. Communicate this widely (and repeatedly). Send regular reminders via Slack, email, or wherever stakeholders engage most. Outline the severity levels, who’s responsible, and how quickly issues will be addressed.

Step 2: Set Clear Criteria for Escalating Issues

Your stakeholders aren’t mind-readers. If they aren’t clear on when to escalate an issue, important problems may go unnoticed. Avoid ambiguity by clearly defining when something must be escalated:

1. Document specific triggers that require escalation clearly. Here are a few examples of how you could define triggers:

   1. Ethical or consent violations: Immediately escalate (critical)

   2. Repeated research quality issues (e.g., consistently poor survey design after multiple trainings): Major escalation

   3. One-time, minor methodological mistakes (e.g., single instance of a poorly phrased question): Minor escalation

2. Give concrete examples to stakeholders. Say something clear and relatable, such as:

   1. “If you find that participant consent forms were not completed correctly, escalate immediately as a critical issue. If you spot biased questions showing up repeatedly in surveys after multiple training sessions, escalate as a major issue.”

3. Reinforce escalation criteria during training. Explicitly discuss escalation processes during onboarding and refresher sessions so stakeholders know exactly when to act.

Step 3: Maintain Transparency Throughout the Escalation Process

People get anxious when they don’t know what’s happening. Transparency about what issues have come up, how you’re responding, and what you’re doing to prevent them is essential to building trust in the research process. Here’s how to put this into practice:

1. Set up a simple, transparent tracking method. This could be a Google Sheet, Airtable, or Notion page where everyone sees:

   1. A brief description of each issue

   2. Severity level and who’s handling it

   3. Current status and how it was resolved

   4. Preventative actions taken

2. Regularly communicate back to stakeholders. Monthly (or bi-monthly), share brief, plain-language summaries. For example:

   1. “Last month, we encountered two critical ethical issues around participant consent. We quickly resolved this by requiring mandatory ethics training for anyone running research. We also saw recurring issues with survey biases, so we’ve scheduled refresher training sessions.”

3. Discuss openly during quarterly research meetings. Use quarterly meetings as opportunities to talk openly about challenges and lessons learned. This reinforces accountability and a healthy research culture.

Your escalation framework doesn’t need to be complex, it just needs clarity. By clearly defining severity levels, assigning clear ownership, setting explicit escalation criteria, and maintaining full transparency, you’ll handle democratization issues proactively, calmly, and effectively, keeping user research valuable, credible, and respected across your organization.

Communicating Issues and Responses Internally

Communicating clearly about issues that crop up is vital. However, no one enjoys receiving negative news, especially when it could reflect badly on their team or their work. How you communicate these issues matters a lot. Poorly handled communication can create resistance or tension; great communication turns these moments into learning opportunities and builds trust.

Here’s how to communicate issues internally clearly, constructively, and actionably (without hurting anyone’s feelings or wasting their time).

Always Frame Issues Constructively (Opportunities vs. Failures)

No one likes hearing their project has issues, and calling out mistakes can easily make people defensive or demoralized. Instead, present challenges as opportunities for improvement or learning. This shifts the conversation from blame to growth. Here are some tips I use:

• Avoid negative language.

  • Instead of:“This survey was biased and unusable,”

  • Try “We spotted an opportunity to make our surveys clearer and more neutral to ensure high-quality insights.”

• Always include the solution alongside the issue.

  • Instead of “Participants weren’t properly consented, this is unacceptable,”

  • Try “We noticed a gap in consent processes. Let’s use this as an opportunity to clarify our guidelines, implement quick training refreshers, and avoid future issues.”

Highlight Examples Where Issues Were Successfully Addressed

People love stories. Rather than only pointing out where things have gone wrong, include clear, concrete examples where your teams successfully resolved an issue. This builds confidence and reinforces positive behaviors internally. Here are some ways to do this:

• Weekly or monthly success stories. Briefly share stories in meetings, Slack, or newsletters:

  • “Last month, the product team noticed repeated bias in surveys. After a quick training session, they wrote an unbiased survey that gave clear, actionable insights, directly leading to improved user experience. Great job!”

• Personalized shoutouts. Recognize individuals publicly (always check first if they’re comfortable):

  • “Huge thanks to Sarah, after attending the refresher on survey design, her latest survey provided some of the clearest data we’ve seen yet!”

This balances the communication about challenges with recognition, keeping people motivated rather than discouraged.

Use Clear, Consistent Language Across All Communications

Consistency builds trust and clarity. If your communication style or language is all over the place, people get confused. Keep things clear, consistent, and easy to understand so everyone knows exactly what you’re talking about each time.

1. Create a simple glossary or communication guide. Outline terms clearly, such as “biased questions,” “ethical escalation,” and “critical issues,” and always use these consistently in emails, Slack, or meetings.

2. Use structured communication templates. For example, a short, clear message structure for issues might look like this:

   1. Issue Identified: (Brief description in neutral, factual language)

   2. Opportunity: (Positive framing of issue as an improvement opportunity)

   3. Immediate Actions: (Exactly what’s being done right away)

   4. Next Steps: (Any follow-up training, check-ins, or audits planned)

Example of a short internal communication:

Issue Identified:

Consent forms were incomplete on three recent user interviews.

Opportunity:

Great chance to refresh our team’s awareness on consent guidelines to improve data compliance.

Immediate Actions:

We’ve scheduled a brief, focused training for next week on consent processes.

Next Steps:

Compliance checks will be reinforced to prevent recurrence. Any questions—reach out directly!

Keep Regular Updates Short and Actionable

Your stakeholders are busy. Long, drawn-out emails or Slack messages won’t get read thoroughly. Short, actionable messages are far more effective.

• Use bullet points instead of paragraphs. People skim, so bullet points grab attention: Instead of “We noticed multiple issues with biased questions in recent surveys, and it’s essential that we address these issues quickly to ensure our data remains valid and trustworthy…”

• Try

  • Issue: Recent surveys have biased questions.

  • Solution: Immediate refresher training this Friday at 11am.

  • Action: RSVP here (link) and attend live or watch the recording by end-of-day Monday.

• End each message with a clear action or call to action. For example, “Action required: Attend the training session or watch the recording by next week.”

This approach ensures your messages drive immediate, helpful actions, rather than being ignored or postponed.

Here’s how you might combine all of the above into one clear, positive, actionable message:

Quick Update: Improving Survey Quality

Issue:

We recently spotted biased questions in some stakeholder surveys, which limits the accuracy of our findings.

Opportunity:

This is a great chance for everyone to brush up on survey best practices and improve data quality together!

What’s happening next:

• A quick, practical survey design workshop is scheduled this Thursday at 3 pm (RSVP here).

• We’ve added clearer templates to our documentation (available here).

• Shoutout to Alex’s team, after attending this session last quarter, their recent surveys have been excellent!

Action:

Please RSVP and attend the session or watch the recording by the end of the week. Any questions, Slack me!

Communication around democratization issues should never be scary or anxiety-inducing. When you frame issues constructively, celebrate successes, keep your language clear, and communicate actionably and briefly, your team will see research democratization as a continuous improvement process, one they’re excited to be a part of, rather than afraid of getting wrong.

Start small, stay consistent, and keep the tone positive. It really makes all the difference.

Democratization Issues Are Normal

If you’re feeling overwhelmed by all these potential democratization issues, take a deep breath. Encountering problems when democratizing user research isn’t just normal, it’s expected. Even the most thoughtfully built frameworks hit snags along the way. The difference between successful democratization and a messy situation is proactively managing these bumps rather than letting them spiral.

Expect Issues

First off, normalize the idea that democratization won’t be perfect from day one. Stakeholders will inevitably write biased surveys, repositories might get messy, and ethical slip-ups could occur. These are not failures—just signals you need clearer guidance, training, or oversight.

• Remind yourself (and your stakeholders!) frequently that issues are learning opportunities, not disasters.

• Have your escalation and response frameworks clearly documented and ready to go, so you’re never caught off-guard.

Use Clear Governance and Proactive Monitoring

A clear governance structure is like the scaffolding around your democratization efforts. It holds everything steady. Regularly checking in on your democratized research through audits, feedback loops, and clear checkpoints ensures your framework stays healthy and credible.

• Set up quarterly quality audits and stakeholder feedback loops immediately.

• Publish your governance framework widely so everyone knows exactly how things work and how they can quickly flag or resolve issues.

Targeted Responses Solve Problems

When issues arise, don’t just react randomly—be intentional. Having specific strategies to address different types of problems (quality, operational, ethical, cultural) makes your responses faster, clearer, and more effective.

• Create easy-to-follow response plans for each type of issue we discussed:

  • Quality: Quick checklists, targeted training refreshers, mandatory reviews.

  • Operational: Centralized, clearly-documented repositories, dedicated research ops oversight.

  • Ethical: Simple templates, explicit consent guidelines, mandatory ethical training, and compliance checkpoints.

  • Cultural: Clear boundaries between democratized and researcher-led studies, regular celebration of successes, reinforcing the value of professional research roles.

Continuous Improvement Is Not Optional

Democratization is never “done.” It’s a constantly evolving process. Regularly revisiting your approach and adjusting your strategy keeps your organization sharp, credible, and effective.

• Schedule regular review checkpoints at least quarterly to reassess how your democratization model is performing.

• Create an easy way for stakeholders to give ongoing feedback—anonymous surveys or open Slack channels—so you know exactly where to focus improvement efforts.

Responding to democratization issues doesn’t mean something’s gone wrong, it means you’re doing democratization right. Every organization faces these challenges, but the ones that thrive are proactive, clear, and structured.

Democratization issues can be like weeds in a garden, inevitable, but manageable if you consistently check, prune, and nurture. By clearly communicating your plans, proactively monitoring your processes, and positively addressing challenges, you’ll keep democratization growing healthy and strong.

Now, go tackle democratization confidently. You’ve got this.

Stop piecing it together. Start leading the work.

The Everything UXR Bundle is for researchers who are tired of duct-taping free templates and second-guessing what good looks like.

You get my complete set of toolkits, templates, and strategy guides. used by teams across Google, Spotify, , to run credible research, influence decisions, and actually grow in your role.

It’s built to save you time, raise your game, and make you the person people turn to.

→ Save 140+ hours a year with ready-to-use templates and frameworks

→ Boost productivity by 40% with tools that cut admin and sharpen your focus

→ Increase research adoption by 50% through clearer, faster, more strategic delivery

Grab the Everything UXR Bundle

Stay curious,

Nikki

If you want to see everything I post, subscribe below!

Subscribe now

This is a series on user research democratization — since this is a tough topic, there was way too much for one article. I will be writing this series and posting it over the next weeks and will edit this as I add to the series so you can easily navigate the different parts.

• Part 1: The Complex Landscape of Research Democratization (Free)

• Part 2: A Framework for Responsible Research Democratization (Paid)

• Part 4: Responding to UXR Democratization Issues (Free)

Stop piecing it together. Start leading the work.

The Everything UXR Bundle is for researchers who are tired of duct-taping free templates and second-guessing what good looks like.

You get my complete set of toolkits, templates, and strategy guides. used by teams across Google, Spotify, , to run credible research, influence decisions, and actually grow in your role.

It’s built to save you time, raise your game, and make you the person people turn to.

→ Save 140+ hours a year with ready-to-use templates and frameworks

→ Boost productivity by 40% with tools that cut admin and sharpen your focus

→ Increase research adoption by 50% through clearer, faster, more strategic delivery

Grab the Everything UXR Bundle

Scaling Research Without Sacrificing Rigor

Research democratization is not a one-size-fits-all solution. What works for one company might fail in another due to differences in team size, research maturity, leadership buy-in, and decision-making culture. Instead of adopting a democratization model blindly, your first step should be research on your own organization.

This chapter has outlined multiple approaches to research democratization, from fully decentralized models to research-led approaches with controlled access. But choosing the right approach requires an honest evaluation of your company’s unique needs, challenges, and research maturity.

This is where your own research skills come into play. Before deciding how to scale research within your organization, take time to assess your current environment, define your goals, and determine the level of structure and oversight required to ensure success.

Assess the Current State of Research in Your Organization

To scale research without sacrificing rigor, you first need a comprehensive understanding of how research currently functions within your organization. Without a clear baseline, democratization efforts risk becoming chaotic, misaligned, or ineffective. Don’t skip this step! We do this:

• To identify exactly who is conducting research.

• To understand the types of research being performed.

• To find bottlenecks preventing effective research.

• To gauge how leadership values research.

• To document how research insights are shared and consumed.

Let’s dive into how to assess the current state.

1. Map Out Current Research Roles and Responsibilities

Objective: Clarify exactly who is conducting research, formally or informally.

Steps:

1. List all individuals conducting research regularly, including:

   1. Trained researchers (User Researchers, UX Researchers, etc.)

   2. Designers

   3. Product Managers

   4. Marketers

   5. Engineers

   6. Customer Support or Success Teams

2. Determine the frequency with which each role performs research:

   1. Is research part of their job description, or are they doing it informally?

   2. How frequently do non-researchers independently initiate studies?

2. Inventory Types of Research Currently Conducted

Objective: Understand what research methods are being used and by whom.

Steps:

1. Catalog recent research projects over the last 3-6 months.

2. Categorize these by research type:

   1. Usability testing (quick tests, prototype evaluations)

   2. Surveys (customer satisfaction, feedback)

   3. Interviews (generative or evaluative)

   4. Analytics reviews (product usage analysis)

   5. Generative or strategic studies (exploratory, opportunity-focused research)

3. Highlight gaps between desired and actual types of research performed.

3. Identify Research Bottlenecks and Pain Points

Objective: Determine the obstacles preventing effective and timely research.

Steps:

1. Conduct stakeholder interviews or surveys asking:

   1. “How often are you delayed by waiting for research results?”

   2. “Have you ever skipped research due to lack of availability?”

   3. “How often do you have to conduct research on your own without support?”

2. Quantify these pain points if possible (“70% of Product Managers skip research due to long wait times”).

Example survey question (with rating scale):

“On a scale of 1-5, how often do you find research availability a blocker for timely decisions?”

(1 = Never, 5 = Always)

Example finding:

“80% of Product Managers rated research availability as 4 or higher, indicating significant delays.”

4. Evaluate Leadership’s Attitude Toward Research

Objective: Assess how research is valued by leaders and decision-makers.

Steps:

1. Conduct targeted leadership interviews or distribute a leadership-focused survey. Ask clear, pointed questions such as:

   1. “Do you consider research essential, helpful, or optional for decision-making?”

   2. “Can you provide examples of recent decisions influenced by research?”

   3. “How much are you willing to invest in research resources and training?”

2. Analyze responses to determine if leadership views research as:

   1. A critical component

   2. An occasional input

   3. A luxury or nice-to-have

Example question:

“Describe a recent instance where research directly impacted your decision-making.”

Example finding:

“We delayed launching the new pricing model until the UX team conducted surveys—research is crucial for big decisions like pricing.”

5. Assess How Research Insights Are Currently Shared and Stored

Objective: Understand how research insights are documented and made accessible.

Steps:

1. Identify all locations where research insights currently live:

   1. Centralized (Dovetail, Airtable, Confluence)

   2. Decentralized (Google Drive folders, Slack, emails)

2. Check how consistently insights are documented:

   1. Do insights consistently include the research question, methods, results, and actionable recommendations?

3. Evaluate accessibility and discoverability:

   1. Are insights easy to find by people across the organization?

   2. How often do stakeholders complain about not finding past research?

6. Summarize Your Findings Into a Clear Research Landscape Report

Objective: Create a succinct, actionable summary highlighting gaps, strengths, and weaknesses.

Suggested structure:

• Current research roles:

  • Who’s conducting research (trained vs. informal)?

• Research types in use:

  • Methods commonly and rarely used.

• Identified bottlenecks:

  • Delays in conducting or accessing research.

• Leadership alignment:

  • How critical is research viewed by leadership?

• Research documentation & sharing:

  • Current status of knowledge management and accessibility.

Example:

“Research is primarily done by one full-time UX researcher, supported informally by designers and PMs. Usability testing is frequent, but generative research is nonexistent. Teams often skip research due to delays, and leadership sees it as important but secondary. Documentation is decentralized, causing frequent duplication and wasted efforts.”

Define Your Organization’s Research Needs and Risks

Not all organizations require the same level of research rigor, nor can they accept the same level of risk. Clearly understanding your organization’s specific needs and risk tolerance is essential to creating a democratization model that is both effective and safe. This step is necessary to:

• Ensure the democratization model aligns with your organization’s specific risk and rigor requirements.

• Prevent costly errors resulting from inappropriate levels of oversight.

• Leverage existing skills within your organization efficiently.

1. Determine the Level of Research Rigor Required

Research rigor refers to the quality standards and methodological thoroughness expected within your organization.

Steps:

1. Classify decision types and their consequences. List recent or upcoming decisions influenced by research. Categorize these by the impact and risks involved.

2. Categorize the decisions into tiers of required rigor:

   1. High-Rigor: Decisions have significant financial, legal, or safety implications.

   2. Medium-Rigor: Decisions impact user satisfaction, retention, or moderate financial outcomes.

   3. Low-Rigor: Decisions are incremental, reversible, or experimental.

Prompting questions:

• What kinds of decisions does your organization regularly face?

• What is the worst-case scenario if research for these decisions is inaccurate or incomplete?

• Can you group your decisions into categories based on the potential risk or consequence?

2. Clarify Your Organization’s Risk Tolerance

Risk tolerance defines how much uncertainty or potential harm your organization is willing to accept as it expands research responsibilities.

Steps:

1. Conduct internal interviews or workshops to gauge comfort with risk:

   1. Ask stakeholders to rate their tolerance for potential research errors (low, medium, high).

   2. Discuss potential consequences openly and document responses.

2. Create a risk assessment matrix to visualize tolerance clearly.

Prompting questions:

• How comfortable is leadership with research findings from non-researchers driving key decisions?

• What types of errors or biases can your organization afford, and what is completely unacceptable?

• Which areas (finance, regulatory, health) require the strictest oversight, and which can afford some flexibility?

3. Evaluate Existing Research Skills in Your Organization

Understanding the research skills and experience within your organization is essential for deciding how much oversight or training you’ll need to implement.

Steps:

1. Create an inventory of current research skills among non-research stakeholders.

2. Use surveys or interviews to capture their research experience.

3. Categorize teams by experience (High, Medium, Low).

4. Assess the gap between current skills and desired research rigor levels.

Prompting questions:

• Do your product or design teams have formal research training?

• Are there team members regularly conducting interviews, usability tests, or surveys without oversight?

• Which teams consistently produce reliable insights, and which require significant researcher intervention?

Identify the Right Democratization Model for Your Context

Selecting the appropriate democratization model is critical. The right model enables your organization to effectively scale research without sacrificing quality, credibility, or reliability. Using insights gathered from assessing your current state (Step 1) and defining your organization’s research needs and risks (Step 2), follow the guide below to pinpoint exactly which model aligns best with your organization’s unique circumstances.

If your organization has a small research team supporting many product teams:

Read more

—

Zack is a mixed-methods researcher who transitioned from managing a restaurant pre-pandemic to becoming a UX researcher. Being homeschooled from an early age sparked a deep curiosity for human behavior and unconventional problem-solving. With a unique background, including a bachelor’s degree in film production, several associate degrees, he brings creative techniques and innovative methodologies to his work, delivering actionable insights that empower stakeholders to make confident decisions.

Zack led generative research and ideation that resulted in real estate's first AI-driven search experience at Flyhomes, addressing pain points that plagued traditional search methods for over a decade. Passionate about collaboration, he believes it’s the key to creating exceptional products, and services. As a long-form improviser, he applies a “yes, and” mindset to facilitate ideation sessions with diverse stakeholders, ensuring research leads to meaningful outcomes.

In our conversation, we discuss:

• Zack’s shift from running a restaurant to leading UX research, and how that background shaped his curiosity.

• The difference between hitting deadlines and creating meaningful outcomes across departments.

• What it takes to keep asking hard questions during a study, not just at the beginning.

• Step-by-step ways to connect with teams like sales or marketing, even when they’ve never heard of UX research.

• How to use short videos, emotional storytelling, and collaborative workshops to get research noticed and used.

Some takeaways:

1. Research isn’t just for product and design. Zack treats UX like a dartboard with many targets. Impact grows when researchers map who else touches the user journey and pull those people in from the start. Sales, support, marketing, leadership; each group brings new context and different blind spots.

2. Ask tough questions even when the project is underway. When Zack senses something is off, he pauses. He isn’t afraid to bring up pivots, gaps, or flawed assumptions mid-way through a study. That level of care helps avoid wasted effort later, and teams usually respect the honesty when it’s framed around shared goals.

3. Start with a small ask when reaching out. Zack sends a quick message before booking meetings. His script focuses on what the other person is working toward and how research might support that. Once a relationship forms, it’s easier to loop them in during planning or synthesis.

4. Workshops land better with the right mix of people. Instead of relying on leadership alone, Zack invites people from across levels and functions to join ideation. Groups merge ideas step-by-step until everyone has shaped the outcome. That approach often leads to ideas that reflect both the big picture and day-to-day realities.

5. Make insights feel real. Zack uses breakup letter prompts and short interview videos to get decision-makers to stop, feel, and act. A one-minute clip where ten customers echo the same pain point can trigger more change than a research report ever could.

Where to find Zack:

• LinkedIn

Stop piecing it together. Start leading the work.

The Everything UXR Bundle is for researchers who are tired of duct-taping free templates and second-guessing what good looks like.

You get my complete set of toolkits, templates, and strategy guides. used by teams across Google, Spotify, , to run credible research, influence decisions, and actually grow in your role.

It’s built to save you time, raise your game, and make you the person people turn to.

→ Save 140+ hours a year with ready-to-use templates and frameworks

→ Boost productivity by 40% with tools that cut admin and sharpen your focus

→ Increase research adoption by 50% through clearer, faster, more strategic delivery

Grab the Everything UXR Bundle

Interested in sponsoring the podcast?

Interested in sponsoring or advertising on this podcast? I’m always looking to partner with brands and businesses that align with my audience. Book a call or email me at nikki@userresearchacademy.com to learn more about sponsorship opportunities!

The views and opinions expressed by the guests on this podcast are their own and do not necessarily reflect the views, positions, or policies of the host, the podcast, or any affiliated organizations or sponsors.

If you want to see everything I post, subscribe below!

Subscribe now

This is a series on user research democratization — since this is a tough topic, there was way too much for one article. I will be writing this series and posting it over the next weeks and will edit this as I add to the series so you can easily navigate the different parts.

• Part 1: The Complex Landscape of Research Democratization (Free)

• Part 3: Scaling Research Without Sacrificing Rigor (Paid)

• Part 4: Responding to UXR Democratization Issues (Free)

Stop piecing it together. Start leading the work.

The Everything UXR Bundle is for researchers who are tired of duct-taping free templates and second-guessing what good looks like.

You get my complete set of toolkits, templates, and strategy guides. used by teams across Google, Spotify, , to run credible research, influence decisions, and actually grow in your role.

It’s built to save you time, raise your game, and make you the person people turn to—not around.

→ Save 140+ hours a year with ready-to-use templates and frameworks

→ Boost productivity by 40% with tools that cut admin and sharpen your focus

→ Increase research adoption by 50% through clearer, faster, more strategic delivery

Grab the Everything UXR Bundle

The Framework for Responsible Research Democratization

Scaling research while maintaining rigor is not a simple process. Without structure, democratization can result in misleading insights, ethical missteps, and wasted effort. However, when implemented correctly, it empowers teams to make user-centered decisions while ensuring that research retains its credibility and influence.

This framework is designed to help research leaders establish a structured, effective, and scalable democratization model, one that enables non-researchers to contribute to research without compromising quality.

Step 1: Define What Can and Cannot Be Democratized

One of the biggest mistakes in research democratization is assuming that all research methods can (or should) be conducted by non-researchers. That is not the case.

A successful framework begins with clear definitions of what research activities can be democratized and what must remain with trained researchers. This prevents low-quality research from being used in high-stakes decision-making and ensures that non-researchers are only conducting studies that fit their skill set.

Create a Categorization System for Research Methods

Break research activities into four tiers:

1. Fully Democratized – Can be run by non-researchers with minimal oversight.

2. Democratized with Oversight – Can be conducted by non-researchers, but requires a trained researcher’s review.

3. Guided Research – Non-researchers can be involved, but a trained researcher must lead the study.

4. Restricted to Researchers – Must be conducted exclusively by trained researchers.

Create a Decision Framework for Stakeholders

Once research categories are defined, build a decision tree that helps stakeholders determine:

• When they can conduct research independently.

• When they need to partner with a researcher.

• When they need to escalate to a research team.

For example:

• Does this research involve sensitive user data or compliance risks? → If yes, it must be conducted by a trained researcher.

• Is this a usability test for a minor UI update? → If yes, a trained non-researcher can conduct it following a structured template.

• Is this a strategic or generative study exploring unmet needs? → If yes, it must be conducted by a research professional.

Having a clear framework removes ambiguity and prevents research from being misused or diluted.

Step 2: Create Clear Guidelines and Guardrails

Without clear guidelines, research democratization can quickly spiral into inconsistent methods, poor-quality data, and confusion across teams.

1. Develop Standardized Research Protocols

To ensure consistency, create a set of research protocols that all teams must follow. These should include:

1. Usability Testing Guides – Pre-written usability testing scripts, rubrics for evaluating responses, and success metrics.

2. Survey Templates – Guidelines on how to write unbiased survey questions and analyze responses correctly.

3. Participant Recruitment Best Practices – Prevents teams from relying on biased, unrepresentative samples (only interviewing internal employees).

4. Data Storage and Handling Policies – Ensures that participant privacy and legal compliance are followed.

2. Implement Pre-Approved Research Templates

Rather than letting teams design research studies from scratch, provide pre-approved templates that ensure structured, repeatable processes. For example, a usability test template might include:

• Scripted introduction to ensure consistency in test facilitation.

• Pre-written, unbiased tasks for participants.

• A standardized results sheet to ensure that findings are logged consistently.

Templates help prevent ad-hoc, low-quality research from creeping into the organization.

3. Build Research Governance into the Process

• Require all studies to be logged in a central repository before they are conducted.

• Assign a researcher to review methodologies for any study run by non-researchers.

• Create a decision tree for ethical considerations, ensuring that sensitive studies are escalated appropriately.

By creating strong governance from the start, research democratization remains structured, not chaotic.

Step 3: Provide Training and Ongoing Support

Training is not optional in research democratization. It is the foundation that determines whether non-researchers will conduct studies that actually improve decision-making or introduce flawed, misleading insights into the organization.

Without training, democratization does not scale research, it scales bad research. Untrained stakeholders may run usability tests with leading questions, interpret survey data incorrectly, or unknowingly introduce bias into their studies. Worse, they may present their findings with false confidence, leading to major business or product decisions being made on inaccurate or incomplete data.

Many organizations make the mistake of treating research training as a one-time event—a workshop, a few documentation pages, or an online course. But research is a skill that requires reinforcement, practice, and feedback. Even experienced researchers continually refine their craft.

For democratization to be effective, organizations need to establish an ongoing, structured training system that aligns with the level of research responsibilities stakeholders will have.

1. Build a Tiered Training Program

Not every stakeholder needs the same level of research expertise. The goal of training is not to turn product managers or designers into full-fledged researchers, it’s to ensure that they have enough knowledge to conduct certain types of research effectively while knowing when to escalate more complex studies. A tiered approach ensures that training is scalable, relevant, and structured.

Level 1: Research Awareness (Mandatory for All Stakeholders Involved in Research)

This is the foundational level for anyone conducting or relying on research insights. It is designed to ensure that all stakeholders understand the purpose of research, when it is appropriate for them to conduct studies, and when they need to escalate to a trained researcher. Topics covered:

• Bias Awareness and Mitigation – How to recognize and reduce bias in research questions, participant selection, and interpretation of results.

• When to Conduct Research vs. When to Escalate – A clear decision framework for determining whether a study should be owned by a researcher or if it can be conducted by a non-researcher.

• Ethical Considerations in Research – Understanding participant consent, privacy requirements, and ethical issues related to data collection and storage.

• How Research Fits Into the Organization – The role of research in decision-making and how democratized research should feed into the broader research ecosystem.

This training should be a required baseline for anyone involved in research—no exceptions.

Level 2: Basic Research Training (For Those Conducting Tactical Studies)

This level is for stakeholders who will be running their own research studies, such as product managers, designers, or marketers conducting usability tests or small-scale surveys. Topics covered:

• How to Conduct Usability Testing – Structuring usability tests, avoiding leading questions, and synthesizing findings.

• Survey Design Best Practices – Writing unbiased questions, selecting appropriate response formats, and analyzing survey data responsibly.

• Basic Interviewing Skills – When and how to ask open-ended vs. closed-ended questions, active listening techniques, and how to probe deeper without leading.

• How to Synthesize Findings Responsibly – Avoiding cherry-picking data, recognizing patterns, and presenting insights objectively.

At this level, stakeholders should still have oversight from researchers, but they can conduct certain studies independently with structured templates and review processes in place.

Level 3: Advanced Research Training (Optional for Stakeholders Seeking Deeper Expertise)

This level is not required for most democratized research participants but can be beneficial for stakeholders who want to develop more advanced research skills and greater autonomy. Examples of who might pursue this level:

• Senior designers who frequently run complex usability studies.

• Product leaders who want to deeply integrate research into their strategy.

• Marketers conducting ongoing customer insights research.

Topics covered:

• Advanced Interviewing Techniques – Learning how to facilitate in-depth qualitative research, including Jobs-to-Be-Done (JTBD) interviews.

• Behavioral Data Analysis – How to connect qualitative insights with analytics data for a more comprehensive understanding of user behavior.

• Longitudinal and Diary Studies – How to structure longer-term research that tracks user behavior over time.

• How to Lead Research Synthesis and Workshops – Training on how to facilitate research readouts and stakeholder engagement sessions.

Stakeholders at this level may require less oversight for certain research types, but they should still have their work peer-reviewed by professional researchers.

2. Set Up Ongoing Research Mentorship and Coaching

Training is only effective if it is reinforced through practice, feedback, and ongoing support. Organizations that simply provide training sessions but fail to offer continuous coaching often find that:

• Stakeholders forget key research principles over time.

• Poor research practices start creeping back in.

• Teams still struggle with synthesizing and interpreting insights correctly.

A structured mentorship and support system ensures that research remains high quality over time and that non-researchers have access to expert guidance when needed.

1. Office Hours with Researchers

Setting up weekly or bi-weekly office hours allows non-researchers to:

• Get feedback on their research plans before launching a study.

• Ask questions about synthesis and reporting.

• Discuss challenges or uncertainties they’re facing in their research.

This system creates a structured yet flexible way for researchers to provide ongoing guidance without needing to hand-hold every study.

2. Research Coaching Programs

Some organizations may benefit from a formal coaching program, where trained researchers mentor non-researchers through their first few studies. A structured coaching model might look like this:

1. Observation Phase – The non-researcher shadows a researcher conducting a study, taking notes on best practices.

2. Co-Facilitation Phase – The non-researcher conducts part of a study under the guidance of a researcher.

3. Supervised Execution – The non-researcher conducts a full study independently, with a researcher reviewing their work and providing feedback.

4. Independent Research with Oversight – The non-researcher is approved to conduct select studies on their own but still submits research plans and synthesis for review.

This gradual introduction to conducting research ensures that stakeholders build real skills rather than diving in with little preparation.

3. Quality Review Check-Ins

To maintain consistency, all democratized research should be subject to regular quality reviews. This includes:

• Pre-study reviews – A researcher approves study designs before they begin.

• Post-study reviews – Researchers check that findings are synthesized correctly and insights are actionable.

• Quarterly audits – Reviewing all democratized research to identify trends, common mistakes, and areas for additional training.

These regular check-ins act as a safety net, ensuring that non-researchers remain aligned with best practices and that the research function maintains credibility.

Step 4: Establish a Centralized Research Repository

Read more

If you want to see everything I post, subscribe below!

Subscribe now

This is a series on user research democratization — since this is a tough topic, there was way too much for one article. I will be writing this series and posting it over the next weeks and will edit this as I add to the series so you can easily navigate the different parts.

• Part 2: A Framework for Responsible Research Democratization (Paid)

• Part 3: Scaling Research Without Sacrificing Rigor (Paid)

• Part 4: Responding to UXR Democratization Issues (Free)

Stop piecing it together. Start leading the work.

The Everything UXR Bundle is for researchers who are tired of duct-taping free templates and second-guessing what good looks like.

You get my complete set of toolkits, templates, and strategy guides. used by teams across Google, Spotify, , to run credible research, influence decisions, and actually grow in your role.

It’s built to save you time, raise your game, and make you the person people turn to.

→ Save 140+ hours a year with ready-to-use templates and frameworks

→ Boost productivity by 40% with tools that cut admin and sharpen your focus

→ Increase research adoption by 50% through clearer, faster, more strategic delivery

Grab the Everything UXR Bundle

The Complex Landscape of Research Democratization

User research is at an inflection point. Demand for research insights is growing exponentially, but research teams remain small. This imbalance forces organizations to explore democratization, enabling non-researchers to conduct research.

At its best, democratization scales insights, increases research buy-in, and enhances customer-centricity across an organization. At its worst, it leads to poor-quality research, biased data, and diluted research rigor. For researchers, democratization can feel like a double-edged sword: it helps meet demand, but it can also erode the depth and expertise of the field if done poorly.

The Growing Demand for Research Across Organizations

User research has expanded beyond the traditional UX and product development lifecycle. Today, research is needed for:

• Product strategy – Understanding user needs before features are even conceptualized.

• Marketing validation – Ensuring messaging aligns with real customer pain points.

• Customer support optimization – Identifying friction points that lead to high support ticket volumes.

• Business decision-making – Using research to inform investment, expansion, and prioritization.

As research extends into these diverse functions, the traditional researcher-to-team ratio has become unsustainable. Many researchers find themselves spread too thin, juggling too many projects with too few resources. In some cases, researchers must reject critical research requests simply because they don’t have the bandwidth. This leads to frustration among stakeholders who feel they lack access to the insights they need.

Additionally, many researchers face the dilemma of either being a solo UXR or small team of researchers trying to take care of multiple teams (I was once working across 10 teams), foundational processes, ops, and maintaining a research framework.

However, research teams haven’t scaled at the same rate as demand. According to Maze’s 2023 Continuous Research Report, 64% of companies now have a democratized research culture to cope with increasing research requests. Yet, research bandwidth remains a major challenge:

This imbalance is what drives the need for democratization but, without structure, it can create chaos rather than efficiency.

The Growing Desire from Non-Researchers to Engage in Research

It’s not just research teams feeling the pressure; stakeholders themselves are becoming more eager to engage with user insights. Product managers, designers, and even marketing teams want direct access to users. They see the value in speaking with customers, testing hypotheses, and gathering feedback.

This shift is largely positive. When more people across an organization have a user-centric mindset, better decisions are made. However, without structure, this enthusiasm can lead to problems:

• Biased research – Without training, non-researchers may unconsciously lead participants toward desired answers.

• Unethical practices – Mishandling of participant consent, privacy, and data security.

• Poor research methodologies – Relying on convenience sampling, asking leading questions, or misinterpreting results.

A 2023 industry survey found that 73% of UX researchers reported spending significant time correcting or guiding poorly conducted research by non-researchers. This often happens because non-researchers unknowingly introduce confirmation bias, leading questions, and flawed synthesis.

The Risks and Rewards of Democratizing Research

Like many trends in UX and product development, democratization is neither inherently good nor bad, it depends entirely on how it is implemented.

Potential Benefits of Democratization:

1. Scalability – More research gets done without overburdening researchers.

2. Stakeholder Buy-in – Teams feel more ownership of insights, increasing the likelihood of acting on findings.

3. Faster Decision-Making – Teams don’t have to wait weeks or months for research results.

4. User-Centric Culture – More teams engaging with research can help embed user thinking into company culture.

Potential Risks of Democratization:

1. Compromised Research Quality – Without structure, teams may conduct poorly designed studies, leading to misleading conclusions.

2. Research Fragmentation – Multiple teams running isolated studies without alignment, leading to duplicated work and inconsistent data.

3. Undermining the Value of Research – If anyone can “do research,” the expertise of trained researchers may be devalued.

4. Ethical Concerns – Improper consent collection, storing sensitive data insecurely, or asking questions that could cause harm.

In a survey done by User Interviews, participants rated their feelings about democratization on a scale from 1 (very concerned/dissatisfied) to 5 (very excited/satisfied). On average, participants rated their feelings a 2.95 out of 5—just below neutral. Sentiment toward democratization was lowest among UXRs, who gave an average rating of 2.84.

The key to democratization is finding the right balance by enabling access to research while ensuring rigor and ethical responsibility.

A Personal Reflection

I’ll never forget the first time I experienced the impact of ungoverned research democratization. At one company, a well-intentioned product manager decided to run their own customer interviews. They were frustrated that the research team couldn’t prioritize their request, so they took matters into their own hands.

On the surface, it seemed great, my stakeholders were taking initiative. But when they presented their findings, I quickly realized the data was riddled with issues:

• They had only interviewed three participants, all of whom were personal contacts.

• The questions were leading, designed to confirm the PM’s assumptions rather than uncover real insights.

• They had misinterpreted responses, turning neutral feedback into positive validation.

As a result, they advocated for a product change that was completely misaligned with actual user needs. It wasn’t until months later, after launch failure, that the team realized their mistake.

This experience solidified my belief that democratization without structure is dangerous. However, the opposite extreme—gatekeeping research—also isn’t the answer. If research teams hoard insights, they risk becoming bottlenecks and alienating stakeholders.

Defining Democratization in a Research Context

At its simplest, research democratization is the process of making research more accessible beyond the UX research team. It allows product managers, designers, marketers, customer support teams, and even engineers to engage with research, conduct studies, and apply insights. But accessibility doesn’t mean a free-for-all, it requires structure, training, and well-defined boundaries.

Nielsen Norman Group has called this ‘Democratization 2.0’ where research is distributed but carefully guided through training, templates, governance, and tiered research access.

For democratization to work, it must be intentional. It’s not about handing research tools to anyone who wants them. It’s about equipping the right people with the right skills to conduct the right kinds of research under the right conditions.

What Democratization Looks Like in Practice

A well-structured approach to research democratization includes:

• Training and education – Non-researchers need to be taught not just how to conduct research but how to recognize its limitations, avoid bias, and synthesize insights properly.

• Clear guidelines on who can conduct what research – Not all research should be democratized. Simple usability tests? Yes. Complex generative studies? No.

• Templates and frameworks – Providing standardized interview guides, usability testing scripts, and survey templates reduces the likelihood of poorly designed studies.

• A review and oversight process – Researchers should act as coaches and advisors, ensuring studies are structured correctly and that findings are interpreted responsibly.

• A centralized research repository – Without a system for documenting and sharing insights, research efforts become fragmented, leading to duplication and inconsistencies.

At one company, we introduced a tiered democratization system to balance access with quality control:

• Product managers and designers were trained to run usability tests using a structured process. They had to submit a research plan before running any sessions, and a researcher reviewed their findings before they were shared.

• Marketing and customer success teams were given access to pre-approved survey templates but needed a researcher’s sign-off before launching a survey.

• All generative and exploratory research remained the responsibility of trained researchers, ensuring foundational insights were handled by those with the expertise to do them properly.

This system allowed the research team to focus on high-impact projects while enabling stakeholders to conduct low-risk research on their own. It wasn’t about giving away research, it was about scaling it responsibly.

Common Misconceptions About Democratization

Much of the resistance to research democratization comes from misunderstanding what it actually entails. Let’s break down the biggest misconceptions.

Misconception #1: “Democratization means replacing researchers.”

One of the most common fears among researchers is that democratization is a thinly veiled cost-cutting measure, a way for companies to avoid hiring or retaining research talent. The reality is, if democratization is implemented as a replacement for researchers, it will fail. Research quality will drop, teams will make decisions based on incomplete or biased findings, and the organization will ultimately feel the consequences in lost revenue, increased churn, or misguided product investments.

Democratization should extend the impact of research, not eliminate the need for researchers. When stakeholders conduct basic research, it frees up researchers to focus on deeper, more complex studies—the kind that require a trained researcher’s skill set.

A responsible approach to democratization: A product team struggling with usability issues trained designers to run usability tests using a pre-approved script. However, researchers still guided the study setup, reviewed findings, and ensured insights were properly synthesized. This allowed research to happen faster while maintaining quality.

A dangerous approach to democratization: An organization decided researchers weren’t needed because product managers could “just talk to users.” Without training or structure, these conversations were riddled with leading questions, incorrect assumptions, and cherry-picked data that confirmed pre-existing biases. The result? A product launch based on faulty insights, leading to poor adoption and wasted development time.

Misconception #2: “Anyone can do research well.”

It’s tempting to think that research is just about asking people questions. After all, everyone talks to users in some capacity, doesn’t that mean anyone can conduct research? Not exactly. Good research requires more than just talking to customers. It involves:

• Knowing how to frame a study to uncover real insights, not just confirm assumptions.

• Asking the right kinds of questions—ones that don’t lead or bias participants.

• Understanding how to analyze responses in a way that reflects true patterns, not just individual anecdotes.

• Recognizing the limits of what a given method can tell you.

I once worked with a marketing team that wanted to “validate” a new pricing strategy by running a customer survey. When I reviewed their draft, I found that nearly every question was leading: “Would you be excited to see this new lower price?” “How much better is this compared to what we had before?” The survey was structured in a way that guaranteed positive responses, and they nearly made a major pricing change based on biased data.

The solution isn’t to ban stakeholders from doing research, it’s to train them on how to do it properly and put safeguards in place.

A balanced approach: Educate non-researchers about common biases, provide pre-approved templates, and have researchers review research plans before launch.

A risky approach: Assume that because someone understands their product, they automatically understand how to conduct valid research.

The Spectrum of Research Democratization

Not all organizations take the same approach to democratization. There’s a spectrum, ranging from tightly controlled research to fully open, self-directed studies.

1. No Democratization:

   1. Research is conducted solely by dedicated UX researchers.

   2. Insights are centralized but often bottlenecked by research bandwidth.

   3. Teams rely entirely on the research team for user insights.

2. Partial Democratization:

   1. Non-researchers conduct some research but within a structured framework.

   2. Usability tests, surveys, and small-scale studies can be run by trained stakeholders.

   3. Researchers maintain oversight and provide guidance.

3. Full Democratization:

   1. Research is open to everyone with minimal oversight.

   2. Teams run studies independently, without researcher involvement.

   3. Insights are often fragmented, with no centralized knowledge base.

   4. Without strong governance, this approach usually leads to unreliable data and misalignment across teams.

Most organizations benefit from structured, partial democratization. It allows research to scale while maintaining rigor.

The Case for Democratizing Research

Democratizing research isn’t just about efficiency, it’s about survival. The landscape of product development moves at an unforgiving pace. Decisions are being made constantly, whether research has informed them or not. Research teams, however, rarely scale at the same speed as their organizations. While demand for research has skyrocketed, the number of dedicated researchers often remains stagnant.

This gap has forced research leaders to rethink traditional models. If a research team can’t directly support every initiative, how can research still be embedded in decision-making across an organization? The answer, for many, has been some form of research democratization—empowering non-researchers with the tools, training, and guardrails to conduct research on their own.

Done correctly, this creates a system where research isn’t just something that happens within the confines of a UX research team. It becomes part of how the organization operates. It allows for more user-centered decisions at scale, better alignment across teams, and an overall stronger connection to customer needs.

But before getting into how to democratize research effectively, it’s important to understand why this shift is happening and what’s at stake.

The Need for Scale

Most research teams face an impossible task: meeting an increasing demand for research with limited resources.

• A single researcher might be responsible for supporting five to ten product teams, each with multiple ongoing projects.

• Companies are making huge strategic bets on product roadmaps, go-to-market strategies, and design decisions, but often without the research capacity to inform them properly.

• Many research teams spend their time prioritizing projects rather than conducting research, meaning valuable but lower-priority questions go unanswered.

I’ve seen this firsthand. In one company, I was the only researcher supporting seven product teams. There were simply not enough hours in the day to conduct research on every feature, design iteration, or customer pain point that needed attention. No matter how well we prioritized, important questions were left unanswered.

At the same time, my colleagues—product managers, designers, and marketers—were desperate for insights. They wanted to understand users, but without access to a researcher, they were forced to rely on assumptions or whatever anecdotal evidence they could gather on their own.

This is the core problem democratization attempts to solve. If every research question has to go through an overburdened research team, insights become a bottleneck. But if teams are enabled to conduct certain types of research themselves, more questions get answered, and research scales alongside the company.

The key is to ensure this doesn’t lead to a free-for-all where bad research does more harm than good.

The Benefit of Increased Empathy

One of the most overlooked benefits of democratization is how it transforms the way teams think about users.

Research isn’t just about gathering insights; it’s about changing perspectives. When product managers, designers, or marketers engage directly with users, it fundamentally shifts how they approach their work. They start making decisions based on what they’ve heard and seen, not just what they assume.

• A designer who watches users struggle through an onboarding flow will never unsee those frustrations. Instead of relying on second-hand reports, they will instinctively advocate for a better experience.

• A product manager who sits in on user interviews stops thinking about features in isolation and starts seeing the bigger picture—the messy, real-world contexts in which customers actually interact with their product.

• A marketing team that tests messaging directly with users will refine their approach based on evidence, not just gut feeling.

I once worked with a product manager who, before engaging in research, had a firm belief that customers wanted more customization options. He pushed hard for this, confident that flexibility was the key to retention. But after sitting in on just three customer interviews, he completely changed his mind. Customers didn’t want more customization; they were overwhelmed by the complexity of the product and wanted simpler, more guided experiences.

That shift in thinking didn’t come from a research report, it came from direct engagement with users. That’s the power of democratization.

When more people in an organization interact with customers, it builds a culture of customer empathy, where decisions are made with a deeper understanding of real user needs.

However, this benefit only materializes when teams are engaging with research in the right way. Without structure, direct engagement can just as easily reinforce biases rather than challenge them. That’s why a thoughtful approach to democratization is critical.

Faster Decision-Making

Speed matters. In fast-moving companies, decisions are made quickly, often without research, simply because waiting weeks for insights isn’t an option.

• Product teams are pressured to ship. They can’t always afford to wait for a dedicated researcher to become available.

• Executives expect quick answers. Delays in research can sometimes mean the difference between launching a feature and missing a market opportunity.

• Customer expectations are evolving constantly. The faster a company can learn, the faster it can adapt.

Democratization, when done well, allows teams to validate assumptions quickly, reducing the risk of making costly missteps. For example:

• A design team that has been trained to conduct usability testing can validate whether a new checkout flow is intuitive in days, not weeks.

• A product team with access to survey tools can gather user sentiment data before launching a feature, ensuring they’re not blindsided by poor reception.

• A marketing team can test messaging with real users before committing to a campaign, avoiding misalignment with customer expectations.

By giving teams the ability to get user feedback quickly, democratization reduces reliance on guesswork. However, the key here is ensuring that teams know when to move fast and when to slow down. Not all research can or should be done quickly. Usability tests and surveys? These can often be done efficiently. Generative research or behavioral studies? These require more time and expertise.

Without a clear framework for what research should be democratized and what should remain within a dedicated research team, organizations risk prioritizing speed over accuracy—which can lead to even bigger problems down the road.

The Risks and Challenges of Research Democratization

Research democratization, if structured well, can expand an organization’s ability to incorporate user insights into decision-making. But when done poorly—or without enough oversight—it can introduce serious risks that undermine the credibility of research altogether.

Scaling research across non-researchers means reducing barriers to participation, but without guardrails, it also increases the likelihood of biased findings, ethical missteps, and fragmented efforts that don’t drive meaningful change.

Quality Control Issues

One of the most immediate risks of democratization is a decline in research quality. When individuals without formal training in research conduct studies, common methodological mistakes can creep in, sometimes with significant consequences for product and business decisions.

In a study of research democratization practices, 73% of UX researchers reported spending significant time correcting or guiding poorly conducted research by non-researchers. This often happens because non-researchers unknowingly introduce confirmation bias, leading questions, and flawed synthesis. One research leader shared that democratization without guardrails turned research into a ‘game of telephone’—insights became increasingly distorted as non-researchers misinterpreted findings, leading to misguided product decisions.

1. Risks of Biased Research, Leading Questions, and Poor Methodology

Non-researchers often approach research with the best of intentions, but without training, they can unintentionally introduce bias at every stage of the process:

• Confirmation bias – Asking questions designed to validate existing assumptions rather than uncovering new insights.

• Leading questions – Steering users toward certain responses rather than letting them express their true thoughts.

• Poor sampling – Interviewing a narrow or unrepresentative set of users, leading to skewed conclusions.

• Flawed synthesis – Cherry-picking insights that align with stakeholder preferences rather than accurately reflecting patterns in the data.

At one company, a product team wanted to “validate” a new feature idea. Since the research team was at capacity, a product manager ran a quick round of interviews. But instead of an open-ended discovery study, they asked leading questions like, “Wouldn’t you find this feature helpful?” Predictably, most users responded positively.

The team took this as a green light to move forward, investing months of development resources. After launch, usage was almost nonexistent—because while users agreed in interviews, their actual behavior told a different story. The issue wasn’t the idea itself, but the flawed research approach that had given them false confidence.

2. The Danger of Superficial or Cherry-Picked Insights

Without proper synthesis, research findings can become over-simplified, misinterpreted, or cherry-picked to support pre-existing ideas. Teams conducting their own research may:

• Over-rely on a few strong opinions, mistaking them for broad trends.

• Ignore conflicting feedback that doesn’t align with their preferred narrative.

• Mistake usability issues for lack of user interest, discarding features too quickly.

A marketing team wanted to refine its messaging and conducted a quick user survey. Most responses were positive, leading them to assume their messaging was strong. But when a researcher later reviewed the data, they found that negative feedback had been dismissed as “outliers.”

In reality, those “outliers” represented a critical segment of potential customers who found the messaging unclear. Because this nuance had been ignored, the company missed an opportunity to improve conversion rates.

Ethical Concerns

User research involves handling people’s personal data, stories, and behaviors. When research is democratized, it’s critical to ensure that ethical best practices aren’t compromised.

1. Consent, Privacy, and Proper Handling of Sensitive Data

When non-researchers conduct studies, they may not fully understand data protection laws or consent protocols. Common mistakes include:

• Failing to obtain proper consent before recording or storing user data.

• Not anonymizing sensitive information, increasing the risk of privacy violations.

• Misusing user data beyond the scope of consent, which can lead to legal repercussions.

A designer I worked with ran an unmoderated usability test using a third-party tool but forgot to include a consent disclaimer. Participants were unaware their sessions were being recorded, violating privacy policies. This led to a compliance issue that required removing all collected data, wasting weeks of work.

2. The Risk of Manipulating Research to Confirm Pre-Existing Biases

Research can be weaponized. When stakeholders conduct their own studies, there’s a risk that they will design the research to confirm what they already want to believe. This can lead to:

• Over-reliance on supportive data while ignoring conflicting insights.

• Framing research questions in ways that guarantee a preferred outcome.

• Misrepresenting insights to push a particular agenda.

An executive wanted to push a new subscription model and asked for research to support the decision. Instead of conducting an unbiased study, they only surveyed customers who had previously expressed interest in subscriptions. The results? A misleadingly high approval rate that didn’t reflect the broader customer base.

When the new model launched, churn increased dramatically because the real majority of customers had never been considered in the research.

Undermining the Value of Professional Research

One of the most contentious risks of research democratization is the fear that it diminishes the role and expertise of trained researchers. As more non-researchers take on research tasks, there’s a real concern that leadership will begin to deprioritize the need for dedicated research professionals altogether.

When organizations assume that “anyone can do research,” they often fail to recognize the depth of expertise required to conduct meaningful, unbiased, and methodologically sound studies. This can lead to fewer dedicated research hires, underfunded research teams, and a loss of credibility for research as a discipline.

But this problem doesn’t emerge overnight. It often starts subtly by shifting responsibilities away from researchers and making research a distributed, secondary task rather than a core business function. If this shift goes unchallenged, researchers can quickly find themselves fighting for relevance rather than driving strategic impact.

How Democratization Can Devalue Research Roles

Democratization, when unchecked, can lead to a misunderstanding of research as a profession. Instead of being seen as a specialized discipline requiring training, rigor, and experience, research is sometimes reduced to a simple task that anyone with access to a survey tool or a scheduling link can handle. There are a few ways this devaluation takes shape:

1. The Erosion of Research Credibility

When non-researchers conduct studies without proper training, they often produce flawed, biased, or misleading insights. These insights, if used to inform decisions, can lead to failed product launches, wasted development resources, or misaligned marketing strategies.

However, when these failures happen, the blame doesn’t always fall where it should. Instead of acknowledging that the methodology was flawed, teams may conclude that research itself isn’t valuable or that it doesn’t lead to actionable insights.

Over time, this weakens the perception of research within an organization. Instead of being seen as a critical function, research becomes an optional, nice-to-have activity that doesn’t always justify investment.

At one company, product managers were given the freedom to conduct their own research. Over time, they ran dozens of studies, but because they lacked training, their insights were inconsistent, biased, and often contradicted each other.

Executives began questioning the value of research altogether. “Why are we spending time on this if every study seems to say something different?” they asked. Instead of realizing that the issue was the lack of research rigor, they assumed that research itself wasn’t producing useful outcomes.

2. The Shift from Research as a Discipline to Research as an Admin Task

When democratization isn’t structured properly, research risks being reduced to a tactical, administrative function rather than a strategic discipline.

Instead of being valued for their critical thinking, synthesis, and ability to uncover deep insights, researchers may find themselves relegated to checking survey drafts, reviewing discussion guides, or approving stakeholder-run studies. This shift has serious long-term consequences:

• Researchers lose their influence in shaping business and product strategy.

• The organization stops seeing research as a driver of innovation and only values it for usability testing and validation.

• Research teams become service providers rather than thought leaders.

A UX research team at a large company started a democratization initiative that allowed product managers and designers to run usability tests. Over time, stakeholders became accustomed to doing their own research and started relying less on the research team.

Eventually, leadership began questioning the need for a dedicated research function at all. “If product teams can do their own research, why do we need a full research team?”

Instead of scaling research, democratization led to the gradual defunding of the research department, reducing it to a small oversight function rather than a core driver of decision-making.

3. The Budget and Hiring Freeze Effect

One of the most polarizing debates in research democratization is whether it threatens the job security of UX researchers. In a 2023 survey, 7% of researchers explicitly linked democratization to layoffs or role reductions. Some companies, after implementing democratization, froze research hiring or shifted research into hybrid roles rather than dedicated teams. However, research leaders argue that structured democratization should enhance, not replace, UX researchers. The key distinction is ensuring researchers own complex studies while enabling non-researchers to contribute within predefined boundaries.

When leadership perceives that research is happening without dedicated researchers, they may start questioning the need to invest in research at all. This can result in:

• Reduced budgets for research tools, participant recruitment, and training.

• Hiring freezes for research roles, even when the demand for insights remains high.

• Reallocation of research responsibilities to non-researchers, leading to burnout and ineffective studies.

This often happens gradually. At first, democratization is seen as a way to scale research—but without careful structuring, it can quickly lead to justification for cost-cutting.

At one startup, researchers trained designers to conduct usability tests. Initially, this helped the research team focus on generative studies. However, when budget season rolled around, leadership pointed to the success of democratization as a reason not to hire additional researchers.

Within a year, the research team was stretched even thinner, and designers—who were supposed to be running only tactical usability tests—were now expected to handle all product research. The result? A research culture built on speed, not depth, with major gaps in insight quality.

How to Protect the Value of Research While Scaling Access

If democratization is necessary, researchers must take an active role in shaping its implementation rather than passively accepting it. Here’s how to do that:

1. Define the boundaries of democratized research

   1. Be clear about what types of research can and cannot be democratized.

   2. Ensure that high-risk, high-impact research remains with trained researchers.

2. Establish research standards and oversight

   1. Create a research framework with clear guidelines for methodology, synthesis, and reporting.

   2. Require peer reviews and quality checks before insights are shared.

3. Position research as a strategic partner, not just a service

   1. Proactively contribute to decision-making conversations, not just research execution.

   2. Show how research can drive innovation, reduce business risk, and uncover opportunities that teams hadn’t considered.

4. Continuously advocate for research expertise

   1. Educate leadership on the depth and complexity of research.

   2. Track and report the impact of research on business outcomes, so it’s clear why dedicated researchers are still essential.

When and How to Democratize Research Responsibly

Democratizing research isn’t an all-or-nothing decision. Done well, it can scale research efforts, integrate user insights across an organization, and build a stronger culture of customer empathy. Done poorly, it can introduce bias, lead to poor decision-making, and undermine the credibility of research as a function.

The key to responsible democratization isn’t just who conducts research, but how, when, and under what conditions. This section breaks down the circumstances in which democratization makes sense, when it doesn’t, and how to ensure that research remains rigorous even as it becomes more widely distributed.

When Should Research Be Democratized?

Democratization works best when it’s filling a gap, not replacing expertise. In the right contexts, it can help teams make better, faster, and more user-centered decisions while allowing researchers to focus on high-value work. Here are the conditions that make democratization beneficial:

1. When Research Demand Exceeds Researcher Capacity

Research teams—especially in growing organizations—are often stretched thin. The number of product teams, marketing initiatives, and business strategies that could benefit from research far outweighs the available researcher capacity. In these situations, democratization allows research to scale beyond the limitations of a small team.

However, this does not mean handing over all research responsibilities to non-researchers. Instead, it means creating a system where smaller, tactical studies can be owned by trained stakeholders, freeing researchers to focus on more complex, high-impact work. Without this structure, research functions become bottlenecks, delaying projects and forcing teams to make decisions based on assumptions rather than data.

To manage this well, researchers should define the types of studies stakeholders can conduct and establish guidelines for when their involvement is required. This ensures that research demand is met without compromising quality or overwhelming the research team.

2. When Teams Need Quick, Low-Risk Insights

There are times when teams need immediate feedback on relatively small decisions—such as refining copy on a landing page, testing a minor UI change, or gauging user reactions to a new feature layout. These types of research questions are not deeply exploratory and do not require advanced methodologies, making them ideal for democratization.

But even these quick-turnaround studies need guardrails to ensure findings are still meaningful. Without structure, teams may conduct rushed, poorly designed research that introduces more noise than clarity. For democratization to work in these cases, organizations need:

• Pre-approved templates and research guides to ensure consistency.

• Baseline training on research bias and question framing to avoid leading questions or faulty assumptions.

• Access to a repository of past research so that teams don’t conduct unnecessary studies when existing data already holds the answer.

By putting these supports in place, teams can run research without reinventing the wheel or making common mistakes that undermine their findings.

3. When Non-Researchers Are Trained and Supported

One of the biggest mistakes organizations make with democratization is assuming that anyone can do research effectively without training. In reality, even seemingly simple methods—such as usability testing or surveys—can introduce bias or misinterpretation when not handled correctly.

For democratization to succeed, non-researchers must be properly trained in research fundamentals. This doesn’t mean turning them into full-fledged researchers, but rather ensuring they have enough knowledge to avoid common mistakes and recognize when they need additional support. Training should include:

• How to ask unbiased questions and avoid leading participants.

• How to recruit representative samples rather than relying on convenience sampling.

• How to synthesize findings in a way that reflects patterns rather than isolated opinions.

• How to understand ethical considerations, such as participant consent and data handling.

Beyond training, ongoing support is necessary. Research should not be a one-time training session that leaves stakeholders on their own. Researchers should act as mentors, reviewing research plans, helping synthesize findings, and ensuring that non-researchers have the support they need to conduct meaningful studies.

4. When Research Rigor is Maintained Through Structured Oversight

Democratization should never mean unstructured or uncontrolled research. While it allows for more people to participate in research, it should still operate within a defined system that ensures research quality remains high. This requires clear oversight mechanisms, including:

• A standardized research review process where trained researchers sign off on study designs before they are executed.

• A centralized research repository where all findings are logged and cross-referenced to prevent duplication and inconsistencies.

• Regular research audits to evaluate the quality of democratized studies and refine processes over time.

Without these structures, research can become fragmented, inconsistent, and difficult to trust—leading to decisions being made based on unreliable data.

When Should Research NOT Be Democratized?

Just as there are times when democratization is beneficial, there are also clear situations where research should remain exclusively within the domain of trained researchers. These tend to be higher-risk studies where poor execution can have serious consequences.

1. When the Study Requires Advanced Methodologies

Some research methods are simply too complex to be handled by non-researchers. These include:

• Generative research that explores unmet needs and uncovers new opportunities.

• Behavioral research that requires deep observation over time.

• Mixed-method studies that involve advanced synthesis across qualitative and quantitative data.

These methods require expertise in study design, recruitment, analysis, and synthesis to ensure findings are valid, reliable, and actionable. Handing them over to non-researchers can lead to inaccurate conclusions that derail business strategies.

2. When Biases Could Significantly Distort Findings

All research contains some level of bias, but certain situations make it especially difficult to remove. If the person conducting the research has a vested interest in the outcome, there is a high risk of unintentional—or even deliberate—bias shaping the results.

For example, if a product manager is testing their own feature, they may subconsciously lead users toward positive feedback or ignore negative comments that challenge their assumptions.

In cases like these, research should be handled by an independent researcher who can approach the study with neutrality and objectivity.

3. When Ethical or Privacy Concerns Exist

Studies that involve sensitive topics, vulnerable populations, or legally protected data require a high level of ethical oversight. If non-researchers are not trained in research ethics, they may unknowingly:

• Fail to obtain proper consent before recording user data.

• Collect and store sensitive data in ways that violate privacy regulations.

• Ask questions that unintentionally cause harm or distress to participants.

For any study that involves healthcare, finance, children, or legally protected information, research should be conducted only by trained professionals who understand compliance, consent, and ethical risk mitigation.

Scaling Research Without Losing Rigor

Research democratization is a reality for many organizations, and it’s clear that it is not inherently good or bad—it depends entirely on how it is executed. When structured effectively, democratization enables faster, more user-informed decision-making without sacrificing research integrity. However, without proper governance, it risks lowering research quality, fragmenting insights, and reducing the perceived value of dedicated research teams.

The key takeaway from this first part of the series is this: Democratization is not an all-or-nothing approach.Organizations that find success with it strike a balance between empowerment and oversight—providing stakeholders with the tools and training they need while ensuring researchers maintain quality control.

In the next part of this series, we’ll explore specific frameworks and methodologies that enable responsible democratization, including:

1. A framework for responsible research democratization

2. Scaling research without losing rigor

3. Responding to democratization issues

Stay tuned, and if you want to ensure you don’t miss the next part of the series, subscribe for updates!

Subscribe now

Stop piecing it together. Start leading the work.

The Everything UXR Bundle is for researchers who are tired of duct-taping free templates and second-guessing what good looks like.

You get my complete set of toolkits, templates, and strategy guides. used by teams across Google, Spotify, , to run credible research, influence decisions, and actually grow in your role.

It’s built to save you time, raise your game, and make you the person people turn to.

→ Save 140+ hours a year with ready-to-use templates and frameworks

→ Boost productivity by 40% with tools that cut admin and sharpen your focus

→ Increase research adoption by 50% through clearer, faster, more strategic delivery

Grab the Everything UXR Bundle

Stay curious,

Nikki

If you want to see everything I post, subscribe below!

Subscribe now

Hello curious human

User research is often viewed as a practice that uncovers insights to enhance user experiences. While this is true, the role of a user researcher goes far beyond usability testing and interview synthesis. Strategic thinking and business acumen are critical to ensuring research has a tangible impact on an organization’s goals.

Without aligning research efforts with business objectives, insights risk becoming unused documents that never drive action. To make an impact, user researchers need to bridge the gap between research and business strategy, effectively positioning themselves as catalysts for innovation and growth.

If you’ve ever struggled with proving the value of your work or gaining stakeholder buy-in, understanding why and how research supports business growth is the key to unlocking new opportunities.

Strategic user researchers move beyond traditional roles of collecting insights and instead become active contributors to product development, customer success, and revenue growth.

This is exactly why I created the Impact Membership—to help user researchers like you align your efforts with business goals and position themselves as strategic leaders. Through the membership, you’ll gain the skills, mentorship, and tools needed to amplify your impact.

Let’s break down why developing a business-first mindset is critical for user researchers.

Influencing product and business decisions

User research is not just about uncovering insights—it’s about driving meaningful change that aligns with business goals and product strategy. If you’re struggling to get your research recognized, the key lies in strategic influence.

Influencing business and product decisions means being proactive, speaking the language of stakeholders, and positioning research as a critical component of business success. But how do you do that effectively?

Many researchers feel frustrated when their insights are ignored or when they see a lack of follow-through from stakeholders. The truth is, product teams and executives don’t dismiss research because they don’t value it—they dismiss it when they can’t see its direct connection to business goals.

Your research should answer questions like:

• How will this impact revenue?

• Will this improve user retention?

• Does this support our strategic business objectives?

If your insights don’t align with these priorities, they risk being perceived as “nice-to-have” rather than essential.

For example:

A user researcher at an e-commerce company conducted a study on mobile usability. Initially, their insights were dismissed as “too minor.” However, when they reframed their findings in terms of potential cart abandonment reduction and increased average order value (AOV), leadership took notice, and the proposed improvements were prioritized.

The way you present your research findings can determine whether they are acted upon or ignored.

Key challenges in influencing business and product decisions

Before we discuss how to influence decisions, it’s important to understand the challenges that researchers often face:

Lack of alignment with business goals:

Research sometimes focuses too heavily on user experience without considering business objectives like growth, retention, or revenue.

Communication gaps:

Researchers often communicate in UX terms (e.g., usability scores, personas) that don’t resonate with business stakeholders.

Timing issues:

Research insights often come too late in the product development cycle, making it difficult to incorporate recommendations.

Perceived lack of ROI:

If research isn’t tied to tangible outcomes, stakeholders may deprioritize it in favor of other initiatives.

How to influence product and business decisions effectively

Step 1: Speak the language of business

To gain traction with stakeholders, you need to frame your research findings in terms of business impact, revenue, and growth.

Instead of saying: “Users struggle to find the checkout button.”

Say: “Improving checkout discoverability could increase conversion rates by 18%, potentially adding $500,000 in monthly revenue.”

Steps:

1. Get familiar with key business metrics such as:

   1. Customer Acquisition Cost (CAC)

   2. Customer Lifetime Value (CLV)

   3. Churn Rate

   4. Retention Metrics

2. Align your research insights with these metrics whenever possible.

3. Use frameworks like OKRs (Objectives and Key Results) to link research outcomes to strategic goals.

Step 2: Involve stakeholders early in the research process

Stakeholders are more likely to act on research when they feel invested in the process. Bringing them in early fosters buy-in and collaboration.

• Schedule kickoff meetings with product managers, marketers, and executives to align on research goals.

• Ask questions like:

  • “What business challenges are we facing right now?”

  • “What user behaviors do we need to understand to drive growth?”

  • “What success metrics matter most for this initiative?”

Steps:

1. Create stakeholder “co-design” sessions where they help shape research questions.

2. Share research goals early and align them with product roadmaps.

3. Conduct stakeholder interviews to understand their pain points and align insights accordingly.

Step 3: Tie research to key business decisions

Your research should not only support product design but also influence business strategy.

• Identify upcoming business decisions and ensure research addresses them directly. Anticipate business questions such as:

  • “Should we enter a new market?”

  • “Which feature should we prioritize?”

  • “Why are customers dropping off at a certain stage?”

Steps:

1. Align your research reports with business objectives.

2. Use storytelling techniques to make findings relatable.

3. Provide executive summaries highlighting business impact.

Example:

Instead of delivering a lengthy report, distill insights into a one-page dashboard with key findings like:

• Current user pain point: 65% of users drop off due to a confusing checkout process.

• Business impact: Reducing drop-offs by 20% could increase revenue by $2 million annually.

• Proposed action: Simplify checkout steps and add trust signals.

Step 4: Demonstrate the ROI of research

Leadership cares about numbers. When you can prove the financial or operational impact of your research, your influence grows.

• Track pre- and post-research impact using A/B tests, analytics, and customer satisfaction scores. Quantify improvements in terms of:

  • Increased conversion rates

  • Reduction in support tickets

  • Faster time-to-market

Steps:

1. Work with data analysts to measure the impact of your recommendations.

2. Develop case studies showcasing how past research influenced business success.

3. Present findings through quarterly impact reports.

Step 5: Become a strategic partner, not just a researcher

Product teams will start viewing you as a strategic partner when you actively contribute beyond research—helping prioritize initiatives and offering business-aligned recommendations.

• Regularly attend product strategy meetings.

• Offer insights proactively, even outside formal research projects.

• Educate cross-functional teams on the value of research.

Steps:

1. Stay informed on industry trends and market shifts.

2. Position yourself as an internal consultant, not just a service provider.

3. Work with leadership to build a long-term research roadmap aligned with business strategy.

Want to overcome these challenges? The Impact Membership offers expert-led workshops on how to align research with strategic business objectives, making your research invaluable to leadership.

Prioritization of research efforts for maximum impact

There’s never a shortage of questions to answer, stakeholders to satisfy, and initiatives to support. It’s easy to feel overwhelmed by competing demands and endless requests for insights.

The key to success lies in prioritization, focusing on the research efforts that will have the highest impact on business goals and user needs. Without it, research can become scattered, reactive, and ultimately, undervalued.

Effective prioritization allows you to:

Maximize your influence:

Working on the right projects ensures your research contributes to critical business decisions and product development milestones.

Ensure efficient use of resources:

Research teams often have limited bandwidth, and focusing on high-impact initiatives allows you to deliver more value with fewer resources.

Strengthen your position as a strategic partner:

When your work is aligned with business priorities, stakeholders see you as an integral part of the decision-making process rather than a reactive service provider.

Avoid wasted effort:

Prioritizing correctly helps you avoid spending time on low-impact research that may not drive action or align with company goals.

Challenges in research prioritization

Before diving into how to prioritize effectively, it’s important to recognize the most common challenges user researchers face:

Saying “Yes” to everything:

Stakeholders often bombard researchers with urgent requests, and without clear prioritization, it’s easy to fall into a reactive mode that drains resources and focus.

Lack of strategic alignment:

Conducting research without understanding broader business objectives can lead to misaligned efforts that don’t contribute to product or revenue goals.

Trying to do too much at once:

Attempting to juggle multiple research projects simultaneously can dilute the quality and depth of insights.

Focusing on short-term fixes:

Addressing only immediate usability concerns without considering strategic opportunities to shape the product’s future can limit your impact.

How to prioritize research efforts effectively

1. Align research with business and product goals

Step 1: Understand the company’s objectives

Start by gaining clarity on your organization’s strategic goals. Ask yourself:

• What are the company’s top priorities for this quarter/year?

• Are we focusing on growth, retention, cost reduction, or product expansion?

• What key metrics (KPIs) are driving business success?

Step 2: Partner with stakeholders

Meet regularly with product managers, executives, and other stakeholders to align research initiatives with business priorities.

Step 3: Map research needs to business impact

Consider how each potential research project contributes to the following areas:

• Revenue growth: Does this research have the potential to improve conversion rates, upsell opportunities, or retention?

• Operational efficiency: Will this research reduce support tickets, decrease churn, or optimize workflows?

• Customer satisfaction: Does this research align with improving CSAT metrics?

Create a simple research roadmap that visually maps upcoming research projects against business goals. This ensures transparency and alignment across teams.

2. Use a research prioritization framework

A structured prioritization framework helps in objectively evaluating research opportunities. Some of the most effective frameworks include:

The RICE scoring model

RICE stands for Reach, Impact, Confidence, and Effort. Assigning numerical values to each factor helps determine which research efforts should take precedence.

• Reach: How many users/customers will be affected by the research findings?

• Impact: What is the potential business impact (high, medium, low)?

• Confidence: How confident are you that the research will produce actionable insights?

• Effort: How much time and resources will it take to complete the research?

The RICE formula is:

(Reach x Impact x Confidence) / Effort = Priority Score

For example:

• Research Study A: (500 users x High Impact x 80% Confidence) / 20 Effort = Priority Score: 2000

• Research Study B: (100 users x Medium Impact x 90% Confidence) / 30 Effort = Priority Score: 300

The project with the higher priority score should take precedence.

The MoSCoW method

This method categorizes research efforts into four distinct categories:

• Must-Have: Critical to the success of the business or product.

• Should-Have: Important but not essential for immediate impact.

• Could-Have: Nice to have but non-essential.

• Won’t-Have (for now): Can be deprioritized for future consideration.

For example:

If a company is planning an international expansion, research related to market feasibility would fall under “Must-Have,” while a UI tweak might be classified as “Could-Have.”

Impact vs. Effort Matrix

This simple yet effective tool helps categorize research tasks based on their potential impact and the effort required.

• High Impact, Low Effort: Prioritize immediately.

• High Impact, High Effort: Plan for strategic investment.

• Low Impact, Low Effort: Consider if resources allow.

• Low Impact, High Effort: Deprioritize.

For example:

Researching onboarding improvements (High Impact, Low Effort) should be prioritized over an exploratory study with unclear business value.

3. Prioritize based on risk mitigation and uncertainty

Prioritize research efforts that help reduce uncertainty in critical business decisions. Consider the level of risk associated with moving forward without insights.

Questions to ask:

• What decisions are currently being made without enough data?

• Which research gaps could lead to costly mistakes if left unaddressed?

• What are the riskiest assumptions within the current product strategy?

For example:

If a company is about to launch a new feature, conducting usability testing to uncover major usability blockers should take precedence over general exploratory research.

4. Consider the research’s longevity and reusability

Prioritize research that can serve multiple purposes across teams and functions. Look for research opportunities that can generate insights applicable to:

• Future feature development

• Marketing messaging

• Customer support improvements

• Product roadmap planning

A well-conducted persona study can inform product design, marketing campaigns, and sales strategies, making it a valuable long-term investment.

5. Be transparent and communicate prioritization decisions

Once priorities are established, ensure they are clearly communicated across the organization. Transparency helps set expectations and gain stakeholder support.

Steps:

1. Host a quarterly research prioritization meeting with stakeholders.

2. Share a research backlog with visibility into priorities and timelines.

3. Regularly update stakeholders on progress and any changes.

Struggling to prioritize? Join the Impact Membership to start prioritizing with confidence and clarity.

Bridging the gap between UX and business goals

User research and business objectives often seem like separate worlds, one focused on usability, empathy, and human-centered design, and the other on revenue, market share, and profitability. However, the most successful organizations understand that great user experiences drive business success, and it’s the responsibility of user researchers to help bridge the gap between the two.

When research insights are directly tied to business metrics, the value of research becomes undeniable. This alignment ensures that both user needs and business goals are met, creating a win-win scenario for the company and its customers.

When user experience efforts aren’t aligned with business goals, organizations face several challenges:

• Research that doesn’t tie into strategic business initiatives may go unused, wasting valuable resources.

• If UX research doesn’t demonstrate business impact, decision-makers may deprioritize it.

• Teams may focus on usability improvements with minimal impact instead of addressing core business drivers like retention and growth.

• If research isn’t aligned with business strategy, products might solve user needs but fail to address market realities or revenue goals.

For example:

A SaaS company wanted to improve their onboarding experience. While their UX team proposed usability improvements, leadership was focused on reducing churn. By reframing research findings in terms of churn reduction, the UX team gained buy-in and saw their recommendations implemented.

Bridging UXR and business goals isn’t about sacrificing user needs, but about aligning research efforts with strategic objectives to ensure actionable impact.

Key challenges in bridging UXR and business goals

Before we explore solutions, it’s important to understand the common roadblocks that prevent user research from influencing business decisions:

1. Different priorities between UXR and business teams

   1. UX teams prioritize usability, accessibility, and engagement.

   2. Business teams prioritize revenue, growth, and scalability.

   3. The challenge is finding common ground where both perspectives align.

2. Lack of a shared language

   1. UX professionals often communicate findings using design terminology, while business leaders think in terms of KPIs, revenue, and growth metrics.

3. Measuring UX impact is difficult

   1. Unlike sales or marketing, UX research outcomes aren’t always directly quantifiable, making it harder to tie efforts to ROI.

4. Siloed organizational structures

   1. UX, product, and business teams often work in silos, leading to misaligned goals and miscommunication.

How to effectively bridge the gap

1. Align UX goals with business objectives early on

The earlier research efforts align with business goals, the more effective they will be. UX researchers should proactively collaborate with stakeholders at the planning stage to understand business objectives and identify ways UX can support them.

Steps:

• Attend business planning meetings to gain insights into company goals and priorities. Ask strategic questions, such as:

  • What are our revenue goals this quarter?

  • What challenges are preventing growth?

  • How can UX improvements help achieve business objectives?

• Develop UXR objectives that map directly to business KPIs, such as:

  • Reducing churn rates

  • Increasing conversion rates

  • Lowering customer acquisition costs (CAC)

For example:

If a company’s goal is to increase annual recurring revenue (ARR), UX research should focus on identifying friction points in the user journey that prevent renewals or upsells.

2. Speak the language of business

Stakeholders respond better to data that reflects their priorities. To influence business decisions, UX researchers must translate findings into metrics that executives care about, such as:

• Customer Lifetime Value (CLV): How UX improvements impact long-term profitability.

• Retention Rates: Demonstrating how better UX leads to increased customer loyalty.

• Cost Savings: Showing how improved UX reduces support costs and churn.

• Convert UX metrics into business metrics.

  • Instead of saying “Users struggle with navigation,” say “Reducing navigation confusion can increase conversions by 20%.”

• Use business-oriented storytelling, focusing on the financial impact and risk mitigation.

For example:

If research reveals that users struggle to find key features, instead of reporting it as a usability issue, position it as an opportunity to improve feature adoption and increase upsell potential.

3. Quantify the impact of UX improvements

Executives want numbers. One of the best ways to bridge the gap is to show tangible, quantifiable results from UX improvements.

Steps:

1. Leverage A/B testing and analytics to measure the business impact of UX changes.

2. Track metrics before and after improvements, such as:

   1. Task completion rates vs. conversion rates

   2. Reduced support inquiries post-design changes

   3. Impact on Customer Satisfaction (CSAT)

3. Use qualitative and quantitative data to create compelling reports.

For example:

If optimizing an onboarding flow leads to a 25% increase in activation rates, presenting this result in revenue terms makes the impact clearer to executives.

4. Establish cross-functional collaboration

Breaking down silos between UX, product, marketing, and business teams ensures research findings are considered in broader strategic conversations.

Steps:

1. Create cross-functional task forces that include UX, product managers, marketers, and executives.

2. Conduct collaborative research planning sessions to align on priorities and share insights.

3. Offer UX training sessions for business teams to help them understand the value of research.

5. Prioritize research that drives strategic decisions

Not all research projects hold the same value. Prioritizing research that aligns with high-impact business goals helps secure stakeholder buy-in.

Steps:

1. Use prioritization frameworks like the RICE (Reach, Impact, Confidence, Effort) model to select research efforts with the highest business impact.

2. Focus on projects that answer critical business questions, such as market expansion, customer retention, or pricing strategy.

3. Develop a long-term research roadmap that aligns with business growth strategies.

For example:

Instead of focusing on minor UI changes, prioritize research that helps understand why customers churn after onboarding and what changes can improve long-term engagement.

6. Communicate UX impact regularly

Regular communication of research insights ensures they remain top-of-mind for business stakeholders and demonstrates ongoing value.

Steps:

1. Provide executive-friendly reports with key findings, potential business impact, and actionable recommendations.

2. Use storytelling techniques to illustrate how UX improvements have driven positive business outcomes.

3. Create UX dashboards that show real-time impact on key business metrics.

Example:

A monthly UX impact report could showcase how reducing friction in checkout flows resulted in an X% increase in completed purchases.

Inside the Impact Membership, you’ll learn how to effectively connect UX insights with business goals, making research a strategic asset that drives long-term value.

Securing stakeholder buy-in and advocacy

As a user researcher, one of the most crucial aspects of your role isn’t just conducting research, but ensuring that your insights influence decisions and drive action. However, many researchers struggle with getting stakeholders to truly engage with research findings, resulting in insights being ignored or deprioritized.

Without stakeholder buy-in and advocacy, even the most valuable research can end up collecting dust in a slide deck rather than informing strategic product and business decisions.

Securing stakeholder buy-in means:

• Your research gets implemented, not overlooked.

• Research becomes a strategic asset, not an afterthought.

• You build long-term advocacy and trust with leadership.

• You gain access to greater resources and influence within the organization.

Getting stakeholders invested in your work is a game-changer for both the success of your research and your career as a researcher.

How to secure stakeholder buy-in

1. Understand stakeholder motivations

To gain buy-in, you must first understand what drives your stakeholders. Different teams have different priorities, and your ability to align research with their goals will determine your success.

• Identify key stakeholders across departments:

  • Product managers care about feature success and roadmap alignment.

  • Executives focus on business growth, profitability, and risk reduction.

  • Marketing teams look for insights to drive customer engagement and acquisition.

  • Customer support wants solutions to reduce complaints and friction points.

Example approach:

When presenting to executives, focus on how research can drive revenue growth or reduce customer churn, rather than usability improvements alone.

Questions to ask stakeholders:

1. What are your current priorities and pain points?

2. What success metrics are most important to you?

3. How do you currently make product and business decisions?

By understanding what stakeholders value, you can position your research as a solution to their most pressing needs.

2. Involve stakeholders early and often

Stakeholders are more likely to support research when they feel like they are part of the process rather than being handed insights they weren’t involved in.

1. Hold kickoff meetings with stakeholders to discuss research objectives and align on goals.

2. Invite stakeholders to observe research sessions to create emotional connections with user pain points.

3. Establish a continuous feedback loop, ensuring stakeholders feel heard and involved.

4. Send weekly progress updates to keep stakeholders engaged and informed about ongoing research efforts.

3. Deliver actionable, concise insights

Stakeholders are busy, and they don’t have time to sift through lengthy research reports. To capture their attention, provide clear, concise, and actionable takeaways.

• Summarize insights into one-page executive summaries with key findings and recommendations.

• Use data visualization tools to highlight important trends.

• Offer a “next steps” section to guide immediate actions based on research.

Example report structure:

1. Key Insight: Users abandon carts due to complicated checkout forms.

2. Business Impact: Potential revenue loss of $500K per month.

3. Recommendation: Simplify form fields and introduce guest checkout.

4. Next Steps: A/B test the new checkout flow within the next sprint.

4. Build credibility and trust

Trust isn’t built overnight; it’s cultivated through consistent, valuable contributions. The more you demonstrate the reliability and impact of your research, the more stakeholders will advocate for it.

1. Start with small, high-impact wins to prove the value of research.

2. Regularly showcase how research has driven positive business outcomes.

3. Be transparent about research limitations and collaborate on solutions.

For example:

In a quarterly review, show how past research led to a successful feature launch that increased engagement by 30%.

5. Foster advocacy by educating stakeholders

Many stakeholders have limited exposure to user research. Taking the time to educate them on its value can turn them into strong advocates.

• Conduct UX workshops and training sessions to demonstrate how research informs better decision-making.

• Share industry best practices and case studies showing research’s impact on business success.

• Encourage stakeholders to champion research by including their perspectives in case studies and reports.

• Create a “Research 101” guide for non-researchers to help them better understand your role and the value you bring.

Elevate your research impact

Bridging the gap between research and business goals, prioritizing the right research efforts, influencing product decisions, and securing stakeholder buy-in aren’t just skills, they’re essential for driving meaningful change and proving the value of user research within any organization.

But mastering these skills doesn’t happen overnight. It requires strategic guidance, proven frameworks, and a supportive community to help you navigate the complexities of user research with confidence. That’s where the Impact Membership comes in.

With the Impact Membership, you’ll gain access to the tools, insights, and expert mentorship you need to take your research career to the next level. Whether you’re looking to:

• Position yourself as a strategic leader by aligning research with business objectives

• Maximize your influence and ensure your insights drive actionable change

• Develop business acumen that helps you speak the language of stakeholders

• Collaborate effectively across teams to prioritize research for maximum impact

• Secure stakeholder advocacy and establish research as a critical function in your organization

…the impact membership program provides everything you need to level up your skills and increase your influence.

What you get:

• Learn from industry leaders on how to align research with business goals and influence high-level decisions

• Actionable tools that help you prioritize research, communicate insights effectively, and gain stakeholder buy-in

• Connect with other ambitious researchers, share experiences, and gain support from peers facing similar challenges

• Personalized guidance to help you navigate the toughest challenges in your research career

• See how top researchers successfully apply strategic thinking to create business impact

The next level of your career starts here.

If you’re ready to go beyond traditional research practices and step into a role where your insights drive real business outcomes, the Impact Membership is for you.

Join the Impact Membership today and start transforming the way you approach user research.

Make your research matter. Make your impact count.

If you’re finding this newsletter valuable, share it with a friend, and consider subscribing if you haven’t already. There are group discounts, gift options, and referral bonuses available.

Share

Stay curious,

Nikki

Paid subscribers get the power tools: the UXR Tools Bundle with a full year of four top platforms free, plus all my Substack content, and a bangin’ Slack community where you can ask questions 24/7. Subscribe if you want your work to create change people can feel.

Subscribe now

If you’re a user researcher trying to create meaningful OKRs (objectives and key results), you’re not alone if you feel overwhelmed or unsure about where to start. Maybe your company’s goals are unclear, or you’re working in a team that doesn’t directly connect to product development, like marketing or customer support. Or perhaps you’re focusing on improving internal research processes and you’re unsure how to measure your impact effectively.

User research can sometimes feel intangible, and writing OKRs that clearly demonstrate its value can be challenging. But with the right approach, you can create OKRs that are both meaningful and measurable, ensuring your research aligns with broader business objectives, even when those goals aren’t explicitly defined.

This guide will walk you through the exact steps to create OKRs that are actionable, tailored for your role as a user researcher, and adaptable to different organizational structures and team functions. Whether you’re supporting product teams, marketing, customer success, or focusing on improving internal research efficiency, you’ll find everything you need to write OKRs that demonstrate impact and align with key business goals.

What are OKRs and why do they matter?

OKRs (objectives and key results) are a goal-setting framework that helps teams set ambitious yet achievable goals and measure progress. They consist of:

• Objectives (O): What you want to achieve. These should be clear, ambitious, and inspiring.

• Key results (KR): How you will measure progress toward the objective. They should be specific, measurable, and time-bound.

The purpose of OKRs is to help align individual and team efforts with broader organizational goals, ensuring that everyone is working toward a common vision.

User research often operates in the background, influencing decisions indirectly. OKRs can help by:

• Prioritizing what matters most and avoid spreading efforts too thin

• Making it easier to communicate the value of research to stakeholders

• Aligning with and contributing to business goals, even if company goals are vague

• Providing a clear framework for tracking progress and iterating on research efforts

This guide walks through a practical way to build OKRs from the ground up, starting with a broad goal you can defend, turning it into a clear objective, then choosing key results that track real progress instead of busywork. Inside the full guide, paid subscribers get:

• A step-by-step process for turning your research focus into OKRs (broad goal → objective → key results → evaluation)

• Stakeholder questions to help you find a research goal that fits your org, even when priorities are muddy

• Four goal-braindumping techniques (pain point mapping, reverse engineering success, the “so that” method, stakeholder alignment sessions)

• Simple formulas for writing objectives and key results, plus examples you can copy

• A breakdown of UXR-friendly metrics (engagement, performance, quality, operational) and how to avoid “output-only” KRs

• A practical checklist for evaluating and refining OKRs (SMART test, stakeholder review, peer clarity test, tracking plan, confidence scoring)

• Common OKR scenarios with example OKRs: unclear company goals, B2B vs B2C, and non-product teams like marketing and customer support

If OKRs have been the thing you avoid until the last possible second, this will give you a clean path to follow.

Exclusively for paid subscribers

Read more

If you want to see everything I post, subscribe below!

Subscribe now

Read more

You’ve just presented a beautifully crafted research report to your team. The insights are spot-on, the data solid, and you’re confident that real change is c…

Read more

Subscribe now

Read more

If you want to see everything I post, subscribe below!

Subscribe now

One of my favorite things to talk about is user research goals because I truly believe they are the foundation of successful user research projects.

When I first started as a user researcher, I had no idea how important goals would be to my research projects. Over time, I realized and recognized that they are (to me, at least) one of the most important indicators of success in a research project.

However, I also quickly learned that writing effective user research goals can be difficult. It took me a lot of practice to feel comfortable writing research goals in a way that made sense to me, the team, and for the overall study.

Why are Goals Important?

So many times, I have sat down to determine what should be in a research report, survey, dashboard, share out or…

And this is also a constant question in my membership.

I often find that whenever I am stuck, I haven’t fully defined the goals of whatever I’m trying to do. I also see this happen so much with other researchers I have worked with.

I can be easy to get deep into a project, making it so difficult to see the forest for the trees. You get stuck trying to find an answer, and it can be almost impossible to see that you need to take a step back and look at what you are trying to accomplish. One of my members, Harmony, and I talk about this very conundrum in a podcast episode about tooling.

I faced this very situation when I was trying to find research tools for my organization. I spent hours upon hours Googling different tools, comparing features, and writing up summaries of each platform. At the end of this process, I felt overwhelmed and dissatisfied. I hadn’t come up with some magic answer through my research and, instead, created more questions for myself.

In the end, I realized I had dove straight into researching the tools and hadn’t sat down to really think about the goals of this initiative. What was I trying to accomplish? What was the expected outcome? Once I asked those questions, not only was I able to narrow the scope of the initiative, but I focused on what I needed to make more informed decisions.

Goals give our projects and initiatives forward momentum and help us whenever we feel stuck at a certain point. When I started using a goal-first approach, I recognized a huge shift in my work:

• My studies were more aligned with what stakeholders needed and everyone knew what the outcome of the study would be (fewer surprises or disappointments)

• Stakeholders came to my presentations excited to learn because they knew what to expect

• My research sessions were significantly more focused because I knew the information I needed to get from participants (while still leaving room for unknown unknowns, of course)

• My workshops were extremely successful, and colleagues took action after them

• Colleagues used my insights because they were directly related to a decision they were trying to make

• I no longer had paralyzing doubt when trying to decide on the direction I needed to go on certain projects or deliverables

• There was no longer this dread I could feel during my research projects when I was unsure if the outcome was what the stakeholders needed

When I truly consider and think about my goals, there is so much less head-banging and spinning my wheels. Goals make everything clearer and give you a solid direction for moving forward.

How to Include Research Goals in Your Process

I quickly learned (and was thrilled to understand) that defining goals goes beyond just user research studies. You can apply this goal-first mindset to almost every single part of your user research process, and it will help you ensure you are doing or including whatever you need to accomplish in an efficient and effective way.

As I mentioned above, I used this goal-first approach to help me with my user research tool initiative, and it didn’t stop there. I’ve become rather obsessed with always starting with the goals of something (even in my business!) and always reminding people that whatever they do, they can focus and get answers by defining goals.

Since I discovered the power of user research goals, I have used them in many different circumstances to help me feel confident about my decisions. In this article, I’ll walk you through a few different ways to incorporate goals into your process so you can benefit from this wonderful approach!

Research Studies

My research studies were the first and most obvious place I started thinking about goals. In the past, I conducted several projects in a row that led to relatively disappointing results — either the methodology didn’t get us the information we needed, or the research outcome wasn’t effective in helping teams make better decisions.

I thought this was just a painful part of the research process for a while, but something felt off. It didn’t seem like getting the right information should be a toss-up, and I was tired of disappointing my colleagues. I had done so much work trying to prove the value of research, and I didn’t want anything to undo that.

So, I investigated what might be going wrong to lead to such a mismatch. After some whiteboarding and stakeholder conversations, I discovered that my lack of goals (poorly written goals) hindered our research projects. Because this step in the process wasn’t as well-planned, we struggled to get the exact information we needed from the study.

As soon as I realized this, I started to think much more deeply about defining research goals in my studies. Not only did this lead to better alignment on the project, but I was also able to more confidently choose participants and proper methodologies.

P.S. Want to learn more about writing user research plans? Check out this super-detailed article.

Presentations or Reports

There were so many times when I asked myself the type of information I should include in a presentation or report; it is also a question I get asked often by my members and mentees.

Before I started to think about the goals of my reports and presentations, I would spend hours going around in circles, trying to guess which information to include and what to leave out.

I would get stuck in this cycle trying to figure out the information I needed to include in these presentations or reports and spend hours endlessly contemplating this. In the end, I guessed, and I often felt nervous walking into those meetings. Did I strike the right balance? Did I include what I needed to? Or did I include too much? Or maybe I missed something?

And my biggest question: how did I get people to care about the things I was talking about in these presentations?

Sometimes, I nailed it, but sometimes, my reports fell flat. It was the inconsistency that really frustrated me. So, similar to what I did with my research studies, I tried to figure out how to improve my reports and came to the same conclusion: defining the goals and outcomes.

Once I started thinking about the goals and outcomes of my reports and presentations, I felt more confident about what I presented and saw the difference in engagement. People actually cared more about what I spoke about, and I had more active discussions that led to action.

Deliverables

There are many deliverables, from personas to journey maps to dashboards to flows. It can become exhausting trying to understand which deliverable to choose and, on top of that, what information to include in said deliverable.

I used to employ the “go-with-the-flow” approach, where I simply picked a deliverable or created the deliverable stakeholders asked for. The problem with this was that there was very little (or no) intention behind the deliverable. That ultimately meant the end result fell flat and was rarely used in people’s work.

This happened to me several times before I realized I was facing the same problem as before. I would spend so much time and effort creating personas or journey maps only for colleagues to look at them once or twice and then leave them to the wayside. Something was missing from them, but I had no idea how to get people to use these deliverables.

Since I couldn’t avoid creating them forever (I tried, trust me), I had to fix this problem before I continued to lose confidence in my skills. Instead of moving forward with a certain deliverable without thinking about it, I started to define why I was creating it and what I wanted to accomplish with it. Then, I started asking my stakeholders the same thing.

With this approach, I gained insight into the goals behind the deliverables and the outcomes we all expected from them. Armed with this information, I could create deliverables that aligned with stakeholders’ needs that they actually wanted to use.

Workshops

Workshops are fundamental to activating your insights and helping your teams go from the problem to the solution space. I didn’t think about my workshop goals for a long time. I just ran them because I was supposed to run them.

But, as you might imagine, this was disappointing for everyone. When people came to my workshops, they weren’t clear on the goals or the outcomes of the workshop, and my sessions lacked focus. In the end, there wasn’t a clear resolution.

People stopped coming to my workshops because they felt unstructured, and I got feedback that they were a waste of time. I was devastated. Workshops are a key soft skill for researchers, and I was terrified this would hold me back from leveling up in my career.

I went back to the drawing board and took the time to plan why I was running my next workshop. At first, I blanked, unsure why I had ever run workshops — I wasn’t used to thinking about this. However, I started to ask myself what I was trying to accomplish, what I wanted participants to get out of it, and what I wished the outcome would be. These helped me define my why and create more effective and impactful workshop sessions.

How to Write Research Goals

Writing goals takes practice and patience, especially if you haven’t deeply thought of them in the past. I remember trying to develop goals for different parts of my process, and I felt overwhelmed. I started to question everything, including my skills. Why did I do anything? Why this method? Why that report structure? Why, why, why?

Eventually, I took a deep breath and started asking myself different questions, and on top of that, I asked other people these same questions. With this mindset shift, I could better define goals without completely giving up on my user research career and becoming a bookstore owner (something I still want to do, though!).

I don’t want you to feel the same overwhelm (and, quite frankly, despair) I went through, so I will walk you through how I write goals for the different parts of my research process.

Avoid the Guessing Game

It’s really funny because, as researchers, we value asking questions so incredibly much. However, I frequently forgot to ask the most important people questions. And those were my stakeholders. I see this happening to other researchers as well. We tend to forget that our stakeholders are our users as well.

Instead, we try to guess and read minds, asking ourselves what we believe our stakeholders might want or need. I had to laugh out loud when I realized I was doing this. I’d spent years telling my stakeholders not to assume or guess what users were thinking only to understand I was doing the same exact thing!

So, from there on out, I started to include my stakeholders in this process, asking them questions that would help me define and align (what a great rhyming mechanism!). Depending on what I was doing, I tailored my questions for each part of the process. These questions include:

Information-gathering

• What information do you need at the end of the project? Why?

• What information do you need in the presentation/deliverable/report? Why?

• What are the top three questions you need to be answered? Why are those your top three questions?

• What is your number one gap in knowledge?

Decision-making

• What decisions do you want to be able to make by the end of the project?

• What decisions do you want to be able to make based on the deliverable?

• Who will use this presentation/deliverable/report?

Expected outcomes:

• What is the ideal outcome of this project?

• What is the ideal outcome of this presentation/deliverable/report?

• What is the number one thing you will do with the information?

Tracking success:

• What is your definition of success for this project?

• How does this project relate to any organizational/business goals?

• What metrics are you using to define the success of this project?

• How would you describe the success of this deliverable/report/presentation?

After asking these questions, I then ask them to fill out this mad-lib exercise:

I need [information] to understand [proposed research goal] to make [decision] that will impact [team/organizational goal]. Then, by the end of the study/workshop, I need [ideal outcome].

By gathering all this information up-front, you are ready to create goals that get everyone what they need and give clear focus to your study.

For Research Studies:

When it comes to writing goals for research studies, it is especially important to include your stakeholders whenever possible by asking them the above questions. Including them ensures you get the outcome they need and also helps you immensely with choosing the correct participants and methodology.

For research studies, I break up the goal-writing process into two parts:

1. A research statement

2. Research goals

A research statement is what you are trying to learn about users at a high level. Here is a model you can use:

We want to better understand how users [think about/make decisions on/interact with] [subject of research/ product] to [create/improve] [product/website/app/service].

This statement gives one or two sentences that describe what the overarching project is about. It is important to solidify this statement because it helps you to create your research goals.

Research goals directly relate to your research statement because they are the more in-depth areas you want to explore in your research statement that will help you answer what you are trying to learn. Your research goals should address what you want to learn and how you will study the research statement.

These goals are the things you want to be able to gather information about by the end of the study. They aren’t posed as questions, but you want to be able to “answer” them in the sense of getting enough data to feel comfortable making decisions. Below are some models you can use for creating research goals.

Common generative research goals:

• Discover people’s current processes/decision-making about [research subject], and how they feel about the overall experience.

• Learn about people’s current pain points, frustrations, and barriers about [current process/current tools] and how they would improve it.

• Understand what [research subject] means to people (how they define it) and why it is important to them.

Common evaluative research goals:

• Evaluate how people are using a [product/website/app/ service].

• Evaluate how people are currently interacting with a [product/ website/app/service].

• Uncover the current tools people are using to [achieve goal], and their experience with those tools. Uncover how they would improve those tools.

These definitely aren’t all the goals you could have, but they can give you a structure and a jumping-off point for writing your research goals. If you’re having a hard time creating research study goals, you can ask yourself and your stakeholders these questions:

• What do we want to learn about [research topic]?

• What type of experiences do we want to learn about?

• What information do we want at the end of the study?

• What decisions are we trying to make by the end of the study, and what can help us make those decisions more confidently?

Research Study Goal Examples

Here are two examples of research study goals:

Example one:

Research statement: We want to understand better how users currently find content through the Merchant Portal in order to understand how to improve the experience for them (through a search functionality or otherwise)

Goals:

• Discover how users currently search through content within the Merchant Portal

• Uncover users’ pain points when it comes to finding content within the Merchant Portal

• Identify how users think about search and their unmet needs when it comes to finding content within the Merchant Portal

  ---

Example two:

Research statement: We want to understand better how users interact with sustainable choices within our platform to create an experience that aligns with their needs and mental models

Research goals:

• Evaluate how participants interact with the sustainability prototype

• Uncover any pain points or confusion participants encounter when interacting with the prototype

• Uncover other current tools participants use to understand their sustainability when choosing travel options

I recommend, for each study, having no more than three goals. I’ve found that going over three goals increases the scope and makes it hard to get in-depth information on each goal.

For Presentations or Reports

It used to take me hours just to figure out what to put in my user research reports or presentations. I used to want to scream, staring at a blank page for what felt like ever, constantly asking myself what I could do to get people to care about my report.

After some time, I decided to take a step back and assess my research reports, like a retrospective on how I put them together. I mainly did this because I felt my reports had become dull and dry, causing people to yawn or disengage. This was the last thing I wanted. I needed colleagues to be engaged and get excited about my research findings, not take a snooze during my presentation.

I returned to the basics and asked myself, “Why should they care about this presentation/report?”

My simple answer was that it should help them make decisions.

That was an ah-ha moment for me. I used to organize my reports and presentations by themes (which I still occasionally do), but I decided to try a slightly different approach. I went straight to answering the research goals aligned on at the beginning of the project. The incredible impact of this structure was that it directly answered what the stakeholders needed to know.  

Let’s say the research goals were to:

1. Understand people’s current mental models around deciding on where to travel next 

2. Discover pain points behind deciding on where to travel 

3. Identify the tools people currently use when getting inspired and deciding on where to travel to next

So, instead of grouping by themes, I would structure it like:

• Research goal one title

  • Finding one directly related to the research goal

    • Evidence of finding one

  • Finding two directly related to the research goal

    • Evidence of finding two

  • Finding three directly related to the research goal

    • Evidence of finding three

Whenever I use this structure to present my reports, people tend to be more engaged because the information in the report is directly related to what they care about and what can help them make better decisions.

If you aren’t necessarily presenting to a specific team or presenting a research report, you can ask yourself (and your audience) the following questions to help you define your presentation goals:

• Who is the audience?

• What do they care about?

• What decisions are they trying to make? What are the top three pieces of information to help them move forward in that decision?

• What is the number one thing you want them to take away from the presentation?

• What is the number one thing you want them to do after the presentation?

• What is your ideal outcome of the presentation? What is their ideal outcome?

• Why would they care about coming to this presentation?

If I were presenting to high-level executives, some of my goals might include:

• Communicate the top three findings that impact the most relevant business metrics they care about

• Get an idea of prioritization based on the research findings from a business perspective

• Get buy-in for additional research studies and budget by presenting research's impact on teams and the organization

Always think about these goals because they will give you a structure of what you need to include and what you are asking participants to act on during or at the end of the presentation, making it more inspiring and clear.

P.S.: If you are struggling to write insights, look at this step-by-step guide on how to write impactful UXR insights.

For Deliverables

How many times has a stakeholder come to you asking for a particular deliverable? I can’t even count the number of times I’ve been asked to create personas, journey maps, mental models, or Jobs to be Done. And one of the worst things I’ve done is agree and move forward without getting context. It always resulted in the deliverables dying with a dusty cover. Or colleagues looking at the deliverables with confused expressions.

Although I did my best to avoid creating most deliverables for a while (that was interesting and funny), I couldn’t avoid them forever, and eventually, I had to create another set of personas. I didn’t want it to end up the same as before, so I knew I had to approach it differently.

The next time a stakeholder came to me with an idea for a deliverable, I asked:

• What decisions are you trying to make with the deliverable?

• What type of information are you looking for?

• How does the team best digest information?

• What’s the ideal outcome of this deliverable?

• What kind of visuals/deliverables have been helpful in the past? Why have they been helpful?

Using this combination of information, I created goals that led me to a completely different deliverable than the one the stakeholder had requested. Originally, the stakeholder asked me to create a persona, but when I probed for information, I found they needed:

• An understanding of how people thought about a certain process

• The areas/gaps where the product wasn’t supporting users in their tasks/needs

• The features that we should de-prioritize because they weren’t helping users

With this, I knew a persona inherently wouldn’t help the team with what they needed. Personas are much more geared toward building a deeper understanding of people’s needs, goals, and pain points, and can help us prioritize roadmaps and future work.

Initially, I was stuck. So I took their needs and created them into goals:

• Communicate the process people go through when ordering meal kits, including how they feel about the process

• Visualize where our product isn’t helping users and the tasks users are doing without our support

• Highlight the necessary features of our users and those that aren’t being used in people’s process of ordering meal kits

With this, I quickly realized that a mental model diagram would be the perfect fit for the needs of this project. I then reversed-engineered the deliverable goals into study goals and aligned with the team to make sure this all made sense. It did, and guess what? They loved the mental model diagram.

So, when you are trying to choose a deliverable, always talk to your stakeholders to understand what they need and then use that to create your deliverable goals — it will help save you a huge headache!

For Workshops

Whatever the topic, I always create goals for my workshops and share them with my audience. Whenever I have been super transparent and up-front in my workshops about what people can expect, I’ve got much more out of the session. If people know what you need, they are better equipped to participate in a helpful way.

Whenever I am creating goals for my workshop, I start by asking myself:

• What do I want people to get out of this workshop?

• What do I want to achieve by the end of the workshop?

• What action do I want to have done within or at the end of the workshop?

• What is the ideal outcome of the workshop?

For me, workshops typically fall into one of the following themes:

1. Create or innovate on new ideas based on problem statements from research

2. Assess current ideas to identify problems before launch

3. React to research findings or post-launch learnings

Each of these themes has goals that also correspond with different activities.

Create or Innovate on New Ideas

A workshop within this theme would aim to:

• Generate a specific amount of ideas to test

• Come together to solve complex user problems

• Find the unknown unknowns

• Gain a deeper understanding of pain points and how to solve them

With this in mind, you would pick activities that would help us achieve these goals. Some activity examples would be:

• Empathy mapping

• How Might We statements

• Crazy 8's

Assess Existing Ideas

You can use theme after the team has created a prototype or concept. The goals for this theme are:

• Identify and solve problems in ideas before they launch

• Get critical and early feedback from users

• Come together to create a better solution

• Create a specific number of new ideas to tes

When trying to get feedback on the prototype or concept within a workshop, you can try the following activities:

• Method 6-3-5

• Usability speed testing

• Do, undo, redo

React to Research or Post-Launch Findings

Sometimes, you need a workshop to give your research that extra attention. At least, I know I do. Often, a report is insufficient, so holding a workshop to unite people is a great way to utilize your insights.

Some of the goals for these workshops include:

• Maintain launched products (ex: usability issues, customer support)

• Gain a deeper understanding of your user

• Create deliverables together

For these workshops, there are several different activities you could use based on the goal:

• Maintain launched products → Gathering issues across departments and prioritizing them via the RICE model (rather than dot voting) OR reviewing an opportunity gap survey

• Gain a deeper understanding of your user → Reviewing research plus How Might We statements

• Create deliverables together → Persona generation, journey mapping

P.S.: Check out this article for more in-depth ways to activate your research insights!

Join my membership!

If you’re looking for even more content, a space to call home (a private community), and live sessions with me to answer all your deepest questions, check out my membership (you get all this content for free within the membership), as it might be a good fit for you!

Subscribe now

Demonstrating impact is critical to our jobs as user researchers, especially recently. Everywhere you look, it’s all about impact. Showing impact, proving impact, sharing impact.

Often, the impact gets tied to the output of user research. Were the insights impactful? Did they spur action? What about the product changed? How did the stakeholders feel about the report?

I played the dangerous game of waiting until the insights came from the research to see how impactful the project was. This approach led me to hoping my research would impact teams and the organization rather than knowing I was conducting the most influential research possible.

At one point, I ran several studies in a row that had landed on my desk without really thinking about how they tied back to the larger goals of the team and the organization. When it came to performance review time, I had done a lot of stuff, but there wasn’t much to show. It was disappointing for me, but a fantastic lesson.

A few months before, I had started a user research roadmap and backlog to organize my upcoming projects better and share them with my stakeholders. I’d “grown up” with product roadmaps being important, so I simply took the same concept to apply to my research projects.

However, over time, I saw my research roadmaps fall into the same trap many product roadmaps do — they became like “feature factories” filled with projects focused on outputs rather than outcomes. I simply threw research projects on the roadmap, not thinking too much about how the project tied back to the outcome or the business.

While this worked for a while, it ended up not serving me. I was frustrated churning out projects as teams churned out features. The work felt disjointed from the “bigger picture,” but I didn’t want to let go of my roadmap. Although it wasn’t the most ideal, it gave me such a great place to plan from and was so helpful in transparency on what I was working on.

What’s an outcome-based research roadmap?

An outcome-based user research roadmap is a living, ever-evolving document that shows the work a user researcher (or user research team) is focused on and how it specifically relates to a larger business objective. It mainly includes projects the team will work on in the next quarter, half-year, or year.

The biggest difference between a general roadmap and an outcome-based roadmap is that, instead of feeling like a feature factory, all of the projects on the roadmap are tied to a specific outcome.

The roadmap demonstrates the different outcomes the team will work on and how they will achieve them.

What do you mean by outcome?

Outcomes can be difficult to measure in user research, but it is essential to consider how our work ties to larger team or company-based objectives/goals.

When simply putting projects on my roadmap without thinking about the larger goal, I spun my wheels doing the same work repeatedly and always failed to answer the question, “How does user research relate to business?”

When it comes to outcomes, you have to look to your colleagues, teams, and organizations to help you. User research is a support system for decision-making and risk mitigation, so the outcomes of your research should support teams in the decisions they have to make and the risks they might be taking.

This concept can be tough to understand, so let’s look at some examples:

Example one:

Imagine we are working with the retention team at Pokemon TCG Live (add me if you play - my username is nicolerothier), and the team’s outcome is to “improve our day-7 app retention rate by 10%.”

Essentially, when people sign up for the live Pokemon Trading Card Game, we want them to return to our app within seven days because, once they pass that seven-day threshold, they are more likely to play for longer and purchase more cards from the store.

There are a million ways that we could likely brainstorm how to do this. This means there are a million risks they could take to try and move this metric. That’s where user research comes in and where we can start to tie our research back to an outcome.

Our research project becomes about mitigating the risks the team are taking when they work to improve this metric. It gives them more of a path or guidance toward making better decisions that resonate with users. So, within this project, our outcome would be:

“Reduce the risk of wasted time/energy when creating solutions to improve our day-7 app retention rate by 10%.”

You could also just tie the project directly to the team outcome, but I always like mentioning risk mitigation, help with decision-making, or reducing choice because it really is the essence of user research.

Example two:

For this example, I will demonstrate the difference between a more feature-based research project versus an outcome-based research project.

Imagine we are working with a conversion team (focused on increasing conversions in our product) at a company called Spooky World, where we sell year-round Halloween decorations (anyone??? Let me know if you want to go in on this fantastic idea). The team’s questions are:

• “Should we add a quick buy button?”

• “Should we add product reviews and photos?”

• “Should we include tips on how to decorate? Or maybe create a blog?”

• Should we let users connect with each other and talk about tips? Should we create a Spooky Community?”

These questions focus on features rather than an outcome or users. They can lead to many usability tests that, ultimately, don’t add much value to an organization or a product. When you go into a performance review, these types of projects can sometimes feel like low impact while still being a good amount of work.

Instead, you can reframe these questions to a larger outcome. Let’s take the quick buy button and the product reviews and photos feature. Instead of just talking about features, we could look at this like: “Improve conversion rate by 5% by simplifying the purchase process.”

Or, if we take the blog and community idea, we could tie it to a much larger objective of “Increasing customer basket size by 10% by helping customers understand how to use decorations together.”

Either way, we aren’t focused on “adding a button” or “creating a community,” but rather, we are mitigating risk by helping users and moving business metrics.

Example three

The final example I want to share is when you run into research projects that feel like they aren’t particularly tied to an outcome, such as generative research. A lot of the time, generative research can be lofty and abstract or could have a lot of potential outcomes across multiple teams.

For this example, let’s imagine we are working at Lego, and we are trying to understand our customers better by doing generative research to uncover their pain points, goals, and needs. We’re focusing primarily on parents because…money 😁

Within this context, what is our outcome? There are a few things we could tie this to:

1. Break down exactly how this project could impact the current outcomes/goals your teams are working on. Generative research helps you gather a lot of useful information that could help all the major metrics (AARRR metrics, for instance). For instance, generative research could absolutely help with improving retention rates by understanding unmet needs.

2. Look further than team-based metrics toward higher-level organization metrics. Generative research helps identify avenues for growth and innovation, which tend to be larger company goals.

3. Take into consideration internal outcomes for your team/yourself. You could have a goal of conducting more generative research (e.g. balancing evaluative and generative research better), so that could be an outcome you could include in the study.

Try not to tie it to a deliverable because that’s an output rather than an outcome, so if you are looking to create an output, what is the outcome that output will achieve? For example, the output of a project is a persona. The outcome of the project is what that persona helps the team do. If we created a persona at Lego, we would want to tie it to an outcome such as creating user-centric product roadmaps or increasing retention rates by understanding and addressing unmet needs.

What’s in an outcome-based research roadmap?

Read more