“The only real mistake is the one from which we learn nothing.” — John Powell

Introduction: Learning by Doing (and Failing)

In a previous article, I shared how I transitioned into UX research as a self-taught researcher. Like many who enter the field without formal training, I learned the hard way — by making mistakes. My first year was full of them. But every error sharpened my skills, deepened my understanding, and taught me lessons I couldn’t have learned any other way.

Here are 10 real mistakes I made early in my UX research career — and what they taught me.

Mistake #1: Writing Leading Questions

In my early studies, I thought I was helping by asking clear, direct questions. However, I soon realized I was unintentionally steering users toward certain answers. For example, asking, “Did you find this feature helpful?” assumes a positive experience and can bias the response.

“If users echo your words, you’re not hearing their thoughts.”

After reviewing recordings and noticing users echoing my phrasing, I knew I had to change. I ask open-ended, neutral questions like, “How did you feel using this feature?” or “What stood out to you?” These let users guide the narrative and surface more authentic insights.

Mistake #2: Not Having a Research Plan

I often jumped straight into writing tasks and questions without clarifying the purpose of the study. I didn’t align with stakeholders or define research goals ahead of time, which led to fragmented, unfocused feedback.

Now, I begin every project with a clear research plan outlining the purpose, objectives, and questions the study aims to answer. This clarity helps me write better tasks and collect more targeted, valuable insights.

Mistake #3: Writing Confusing Tasks

In early sessions, participants would freeze or ask, “What do you mean by that?” My tasks were often too vague, overly technical, or crammed with multiple steps.

I’ve since learned to write tasks in plain language, test them with a peer, and focus on one clear goal per task. If users are confused by the instructions, I’m not testing the product — I’m testing the task itself.

“Clarity in tasks is just as important as clarity in design.”

Mistake #4: Testing Too Many Things at Once

Trying to test multiple features, flows, and variations in a single session overwhelmed participants and diluted my data. I had high drop-off rates and conflicting feedback.

Now, I use a focused, step-by-step approach — testing one feature or question at a time. This improves the quality of the insights and helps teams act faster on the results.

Mistake #5: Presenting Raw Data Instead of Insights

Initially, my reports were more like data dumps — filled with quotes, transcripts, and video links, but no clear takeaways. Stakeholders would skim, nod politely, and rarely take action.

“Good research doesn’t just tell you what users said — it explains what it means and why it matters.”

I realized research is about storytelling. I now synthesize patterns, highlight key insights, and connect findings to business outcomes. Including a quick “TL;DR” at the top has also improved visibility and engagement.

Mistake #6: Trying to Sound Smart Instead of Being Clear

As a self-taught researcher with imposter syndrome, I needed to prove myself. I loaded my reports with jargon and complex terms like “heuristic violations” and “cognitive load,” thinking it added credibility.

But instead of building trust, I confused my audience. Today, I focus on clear, direct communication. Simplicity doesn’t mean dumbing things down; it means ensuring everyone understands.

Mistake #7: Not Involving Stakeholders Throughout the Process

Early on, I treated research like a solo mission — I’d complete the work, write the report, and drop it in Confluence or Teams. Unsurprisingly, it often got ignored.

Now, I engage designers and project owners from the start. I ask what they want to learn, invite them to observe sessions, and preview insights before final reports. When people see and hear user pain points firsthand, they’re more likely to take action.

Mistake #8: Assuming Users Would Behave Logically

I used to watch users miss buttons or struggle with what I thought were obvious flows and wonder, “How did they miss that?”

It turns out users don’t think like designers or developers. They scan, guess, and get distracted. Testing reveals actual behavior — not the ideal experience we imagined. I now go into sessions expecting surprises and letting them shape our solutions.

Mistake #9: Not Testing with the Right Audience

In the beginning, I often recruited whoever was available without screening. This sometimes led to feedback from people who didn’t reflect our actual users, which skewed the results.

Today, I use straightforward screener questions to ensure participants align with the product’s intended audience. Testing with the right users leads to more relevant insights and better product decisions.

Mistake #10: Not Creating Strong Documentation

My early research findings were scattered across emails, Slack threads, and random folders. When someone asked, “Didn’t we test this before?” I often couldn’t remember where anything lived.

Now, I maintain a central research repository with standardized documentation: goals, methods, participants, key findings, and links to materials. This makes it easy to reference past studies and scale research knowledge across the team.

Conclusion: Embrace the Mistakes

Every mistake I made was part of the learning process. They taught me to ask better questions, conduct better studies, and communicate more clearly. If you’re new to UX research or navigating it on your own, don’t fear failure.

Make mistakes. Learn from them. Document them. And keep going.

What about you? What mistakes have shaped your UX research journey? Drop a comment — I’d love to learn from your experiences too.