Discovery Theater
User research and discovery activities produce artifacts but do not meaningfully change decisions.
- Also known as
fake user researchpost-hoc validationthe research ritualinsight without impact
- First noticed by
product leadUX researchersenior PM
- Mistaken for
- user-centered design
- Often mistaken as
- mature product practice
Why it looks healthy
Concrete external tells that make the pattern read as responsible behavior.
- The team runs regular user interviews
- Research documents are plentiful and well-formatted
- Product reviews include "what users told us"
- The org cites user-centered design as a value
Definition
What it is
Blast radius product team business
Discovery activities - interviews, personas, journey maps, usability tests - are conducted as process compliance rather than genuine inquiry.
How it unfolds
The arc of the pattern
-
Starts
A team adopts discovery practices to be more user-led.
-
Feels reasonable because
Running research looks like the right thing to do.
-
Escalates
Research is conducted after the decision is made, framed to validate rather than challenge, or ignored when inconvenient.
-
Ends
The team ships something users do not want and cannot understand why, given that research was done.
Recognition
Warning signs by stage
Observable signals as the pattern progresses.
EARLY
Early
- Research is scheduled after the roadmap is already committed.
- Personas and journey maps are created but not referenced in design reviews.
- Research findings that contradict current direction are not discussed.
MID
Mid
- Discovery outputs are not connected to specific decisions.
- The same insights appear in successive research cycles without driving change.
- Researchers feel their work is not used.
LATE
Late
- A feature ships that contradicts known user needs.
- The team is surprised by user reception despite having done research.
- Researchers stop raising inconvenient findings.
Root causes
Why it happens
- Decisions are made by conviction or seniority before research begins
- Research is treated as documentation rather than input
- Inconvenient findings threaten committed roadmaps
- Discovery is a ritual not a decision input
Response
What to do
Immediate triage first, then structural fixes.
First move
Pick one current decision that could actually be reversed by research - if there isn't one, don't run the research.
Hard trade-off
Accept research that might force you to change a direction leadership has already signaled, or accept that research is not decision-support.
Recovery trap
Tightening the research process - faster cycles, better synthesis templates - without moving research ahead of the decision.
Immediate actions
- Identify one current decision that research could change
- Present inconvenient findings to the decision-maker directly
- Connect each research activity to a specific open question
Structural fixes
- Run research before committing roadmap items
- Make research findings a required input for design reviews
- Track which decisions were changed by research
What not to do
- Do not run research that cannot change the outcome
- Do not use user quotes to validate decisions already made
AI impact
How AI distorts this pattern
Where AI-assisted workflows accelerate, hide, or help with this failure mode.
AI can help with
- AI can help analyze real user feedback, session recordings, and support tickets to surface genuine patterns quickly.
AI can make worse by
- AI can generate synthetic personas, journey maps, and user stories that reinforce existing assumptions without real user contact.
Relationships
Connected patterns
Causal flows inside Failure Modes, and related entries across the site.
Easy to confuse with
Nearby patterns and how this one differs.
-
Scope theater performs trade-offs that don't reduce scope. Discovery theater performs learning that doesn't change decisions.
-
Feature factory ships without learning. Discovery theater learns without shipping differently.
- Adjacent concept Legitimate user research
Legitimate research can change the decision. Theater can't, because the decision is already made.
Heard in the wild
What it sounds like
The phrase that signals the pattern is about to start, and who tends to say it.
We did the research. Users will get used to it.
Said byproduct manager or senior leader
Notes from practice
What experienced people notice
Annotations from engineers who have worked this pattern before.
- Best momentWhen intervention actually changes the trajectory.
- When research activities are scheduled after decisions have already been made
- Counter moveThe specific action that breaks the pattern.
- If the research cannot change the decision, do not do the research.
- False positiveWhen this pattern is actually the correct call.
- Some research genuinely validates good decisions. The failure mode is research that cannot challenge any decision.