Avoiding Research Theater starts with a simple test: does this make the work more decidable, or does it only make the work easier to describe? Avoiding Research Theater: in discovery and customer research, teams often mistake fluency for progress. Avoiding Research Theater: they can explain the issue, name the stakeholders, and produce a tidy artifact while the actual research decision remains untouched.

Avoiding Research Theater matters because operating systems decay when decisions stay implied. Avoiding Research Theater: the company keeps moving, but each team carries a different version of the truth. Avoiding Research Theater: one group thinks the bet is strategic. Avoiding Research Theater: another treats it as optional. Avoiding Research Theater: a third waits for a signal that nobody has agreed to produce. Avoiding Research Theater: the surface looks aligned until execution exposes the disagreement.

Avoiding Research Theater is the part of the series that shows where the idea crosses functional boundaries and where ownership can blur. Avoiding Research Theater: the post should therefore leave the reader with something more useful than a principle. Avoiding Research Theater: it should leave a sharper question, a better artifact, and a way to inspect whether the work changed.

Where the work breaks

Avoiding Research Theater breaks when the team keeps the conversation abstract. Avoiding Research Theater: abstract language lets everyone nod because nobody has to give anything up. Avoiding Research Theater: a real decision has a cost. Avoiding Research Theater: it changes priority, sequence, ownership, scope, customer contact, or follow-through. Avoiding Research Theater: if none of those things changes, the team may have had a good conversation, but it has not changed the operating system.

Avoiding Research Theater also breaks when teams use process as a substitute for judgment. Avoiding Research Theater: a meeting can collect updates without creating insight. Avoiding Research Theater: a memo can summarize context without recommending a choice. Avoiding Research Theater: a dashboard can show movement without showing whether the movement matters. Avoiding Research Theater: the repair is not more ceremony. Avoiding Research Theater: the repair is a clearer relationship between evidence and action.

Avoiding Research Theater has another failure mode: people protect optionality until the decision window closes. Avoiding Research Theater: optionality feels responsible because it avoids premature commitment. Avoiding Research Theater: past a certain point, though, optionality becomes a tax. Avoiding Research Theater: teams keep weak work alive, delay learning, spread attention thin, and make every downstream handoff harder.

What good looks like

Avoiding Research Theater is healthy when a team can say what changed after the conversation. Avoiding Research Theater: the change might be small: a narrower customer segment, a stopped feature, a clearer launch owner, a better research question, a different account plan, or a new review date. Avoiding Research Theater: small changes count when they remove ambiguity and create forward motion.

Avoiding Research Theater should make disagreement more useful. Avoiding Research Theater: good disagreement is not noise. Avoiding Research Theater: it is information about assumptions, risk, incentives, and evidence quality. Avoiding Research Theater: the operating move is to capture the disagreement in a form the team can test. Avoiding Research Theater: if the disagreement cannot be tested, it should at least be named as a judgment call instead of hidden as consensus.

Avoiding Research Theater should also protect the team from false completeness. Avoiding Research Theater: complete-looking artifacts can still avoid the most important question. Avoiding Research Theater: the test is whether a new person could read the artifact and understand the decision, the evidence, the tradeoff, the owner, and the next inspection point without reconstructing the whole history.

The useful artifact

Avoiding Research Theater needs an artifact that is small enough to survive normal work. Avoiding Research Theater: a useful artifact has five parts: the decision, the evidence, the tradeoff, the owner, and the review trigger. Avoiding Research Theater: anything beyond that should earn its place.

Avoiding Research Theater should name the decision in plain language. Avoiding Research Theater: if the decision is actually three decisions, split it. Avoiding Research Theater: if the decision has already been made, say that and use the artifact to clarify execution. Avoiding Research Theater: if the decision is still open, make the options visible enough that people can argue about the real choice.

Avoiding Research Theater should treat evidence with respect without worshiping it. Evidence has shape. Avoiding Research Theater: a customer quote, usage trend, sales objection, churn pattern, or support signal can matter a lot, but each proves a different thing. Avoiding Research Theater: the artifact should say what the evidence supports, what it does not support, and what would be strong enough to change the next move.

Avoiding Research Theater should make the tradeoff impossible to miss. Avoiding Research Theater: tradeoff language is the difference between a strategy document and an aspiration document. Avoiding Research Theater: the team should know what receives less capacity, what waits, what gets cut, what risk is accepted, and which stakeholder will feel the cost.

How to inspect it

Avoiding Research Theater can be inspected with four questions. What are we choosing? What are we refusing? Avoiding Research Theater: what evidence would change our mind? Avoiding Research Theater: what happens before the next review? Avoiding Research Theater: if a team cannot answer those questions, the work is not yet ready for more process. Avoiding Research Theater: it needs clearer judgment.

Avoiding Research Theater should show up in the calendar. Avoiding Research Theater: if the decision matters, it deserves a checkpoint. Avoiding Research Theater: that checkpoint does not need to be heavy. Avoiding Research Theater: it needs a defined signal, a real owner, and permission to change course. Avoiding Research Theater: without that, the team will keep carrying the decision as background anxiety.

Avoiding Research Theater should reduce the need for executive translation. Avoiding Research Theater: a senior leader should be able to inspect the work without redoing the thinking. Avoiding Research Theater: if the leader has to infer the customer, rebuild the evidence, guess the tradeoff, or identify the owner, the artifact is not doing enough operating work.

Field test

Avoiding Research Theater can be tested on one live piece of work this week. Avoiding Research Theater: pick something already consuming attention. Avoiding Research Theater: rewrite it as a decision, not a status update. Avoiding Research Theater: name the owner, the evidence, the tradeoff, and the review trigger. Avoiding Research Theater: then ask what changed because the artifact exists.

Avoiding Research Theater passes the test when the next action becomes more specific. Avoiding Research Theater: the next action may be a customer call, a killed initiative, a narrower scope, a pricing review, a product bet, a launch decision, or a management conversation. Avoiding Research Theater: the important part is that the work leaves the realm of explanation and re-enters contact with reality.

Evidence note: This is an operator-judgment essay grounded in Antoine's local source pack for Discovery and Customer Research Without Theater and adjacent series context, including https://www.antoinebuteau.com/building-ai-products-is-not-prompt-decoration/.

This is part 7 of 10 in Discovery and Customer Research Without Theater.