Avoiding UX Research Theater: When Activities Look Like Research But Aren't

A researcher's greatest fear is not delivering bad news, it is being ignored. The nightmare scenario is not that your findings are challenged, but that they are not taken seriously in the first place.

Sometimes, UX professionals, with the best of intentions, make it unnecessarily hard for themselves by engaging in what can only be described as UX Research Theater.

What Is UX Research Theater?

UX research theater is the performance of research-like activities that lack substance and rigor. It is a series of workshops and exercises designed to make teams feel involved and productive, but which produce outputs with no real connection to actual user data.

This can be devastating to a researcher's credibility, especially with serious stakeholders who can easily see when there is no actual research behind the recommendations.

Common Signs

Unstructured Workshops

Internal workshops, often under the banner of "Design Thinking," that devolve into random brainstorming sessions for survey or interview questions without clear goals.

The team leaves feeling energized and collaborative. But what was actually produced? A list of ideas generated from opinions, not evidence.

The Alternative: Collaborative Synthesis Workshop

A rigorous workshop is not for brainstorming questions, it is for making sense of data you have already collected. Present your tagged and analyzed findings to the team. Their role is not to generate ideas from scratch but to use their expertise to help connect patterns, move from findings to insights, and prioritize recommendations.

Substanceless Mapping

Drawing simplified user journeys, creating affinity maps, or clustering themes from ad-hoc brainstorming rather than from structured, empirical data.

These activities, combined with exercises like dot voting, create an illusion of consensus while blurring the line between opinion and evidence.

The Alternative: Evidence-Based Mapping

An affinity map or customer journey map is only as valuable as the data it is built on. A rigorous map is created after your analysis is complete. Each step in the journey, each pain point listed, must be directly tied to a specific, validated finding from your research.

Every sticky note on the board should be traceable back to a user quote, an observation, or a quantitative data point.

The Persona Problem

One method highly prone to being misused as UX theater is the Persona.

While this book uses the term pragmatically as roughly equivalent to a well-defined user segment, the method as it is often practiced has serious conceptual issues.

Foundational Critique

Research has highlighted significant methodological flaws in the persona method ^[1]:

• While personas are often presented as a scientific tool, there is a lack of empirical evidence proving their effectiveness
• The process for creating them is often poorly defined, relying heavily on the creator's subjective interpretations
• This is exacerbated when teams literally "make up" personas from scratch or base them on incredibly thin data

The Risks

When personas are not grounded in rigorous data:

The Alternative: Empirically Grounded Segments

Instead of creating fictional narratives, focus on defining user segments based on rigorous segmentation principles.

A valid segment is defined by:

• Shared, observable behaviors
• Validated needs that have emerged from your data
• Patterns observed across multiple users

You are not creating a character, you are describing a pattern.

The Core Problem

All forms of UX research theater share a common flaw: they substitute the appearance of rigor for actual rigor.

Workshops, brainstorming, and collaborative processes are highly important for:

• Reaching consensus about research goals
• Making sense of data
• Communicating and presenting insights
• Driving impact

But these activities should never replace actual research.

Why It Happens

Teams engage in research theater for understandable reasons:

• Time pressure: Proper research takes time; workshops feel faster
• Budget constraints: Brainstorming is cheaper than recruiting participants
• Desire for collaboration: Workshops feel more inclusive than solo analysis
• Familiarity: "Design Thinking" exercises are well-known and comfortable

The Stakeholder Reality: Don't assume stakeholders only want the "final answer." In my experience, they are often only as interested in your methods as they are in evaluating if a finding is "valid." Simply suggesting changes without showing the "how" (the process, the raw evidence, the logic) often fails. They need transparency on the journey from data to recommendation to trust the destination.

The solution is not to eliminate collaborative activities but to ensure they are built on an empirical foundation.

For how strategic positioning prevents research from becoming performative, see From Data Collector to Strategic Partner.

A Simple Test

Before any workshop, mapping exercise, or persona creation, ask:

1. What data is this based on?
2. Can every output be traced to specific evidence?
3. Would a skeptical stakeholder find the methodology credible?

If the answers are unclear, you may be engaging in research theater.

For the methodological rigor that separates real research from theater, see Research Quality and Managing Bias.

Theater vs. Reality: The Checklist

Use this comparison to diagnose whether an activity is genuine research or performance:

For how systematic research operations prevent theater from taking root, see Building a UX Insights Repository: A ResearchOps Guide.

What This Means for Practice

The goal is not to eliminate collaboration and creativity from the research process. It is to ensure that collaboration is applied to real data, not to opinions dressed up as insights.

Evidence-based outputs build credibility. Research theater destroys it, often permanently, as stakeholders who have been burned once will be skeptical of research going forward.

Protect the credibility of your function by insisting on empirical foundations. If you cannot cite the evidence, do not include it in the output.

For how to produce reports that demonstrate real research value, see Anatomy of an Effective Report.