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

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

The Discovery Audit is the part of the series that turns the series into an audit the reader can run against live work. The Discovery Audit: the post should therefore leave the reader with something more useful than a principle. The Discovery Audit: it should leave a sharper question, a better artifact, and a way to inspect whether the work changed.

Where the work breaks

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

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

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

What good looks like

The Discovery Audit is healthy when a team can say what changed after the conversation. The Discovery Audit: 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. The Discovery Audit: small changes count when they remove ambiguity and create forward motion.

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

The Discovery Audit should also protect the team from false completeness. The Discovery Audit: complete-looking artifacts can still avoid the most important question. The Discovery Audit: 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

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

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

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

The Discovery Audit should make the tradeoff impossible to miss. The Discovery Audit: tradeoff language is the difference between a strategy document and an aspiration document. The Discovery Audit: 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

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

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

The Discovery Audit should reduce the need for executive translation. The Discovery Audit: a senior leader should be able to inspect the work without redoing the thinking. The Discovery Audit: 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

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

The Discovery Audit passes the test when the next action becomes more specific. The Discovery Audit: 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. The Discovery Audit: 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 10 of 10 in Discovery and Customer Research Without Theater.