The Analysis Is Not the Product

A vice president reports that dealer inventory is too high and fill rate is still deteriorating, and asks for a dashboard in time for Friday’s meeting. A competent team does what it was taught to do. It extracts data, explores it, fits a model, charts the exceptions, and assembles a presentation. Forty-seven slides later, someone senior asks the only question that mattered at the beginning: what, exactly, are we supposed to do?

The meeting ends in agreement that the work was thorough. The replenishment rule does not change.

The work was not empty. It was aimed at the wrong product.

What the product actually is

A decision, in the sense this method uses the word, is a commitment to one alternative over others, made by someone with authority, under uncertainty, that will enter an operating process.

Every clause in that sentence is doing work. Commitment to one alternative over others rules out a dashboard, which commits to nothing. Someone with authority rules out a recommendation addressed to a meeting rather than a person. Under uncertainty rules out waiting for the analysis that removes all doubt, which is not coming. Enters an operating process rules out agreement in principle, which is the most common way good work dies.

Analysis that cannot change which alternative is chosen is decoration. Accurate decoration is still decoration, and this is the sentence most technical people find hardest, because accuracy is the thing they were trained to defend.

Why labor gets mistaken for rigor

The substitution is not laziness. It is the natural consequence of how technical competence is built and rewarded.

For a decade or more, the thing being graded is the derivation. A proof that asserts its conclusion without steps is worthless. A benchmark without methodology is not evidence. Effort and correctness are tightly coupled, and the coupling is real in that setting.

Then the audience changes and nothing announces it. The same person produces the same artifact, and the artifact is now the wrong shape. Six weeks of work reads as six weeks of work, and six weeks of work is not what anyone is buying.

The diagnostic

Take the last substantial study your team produced. Ask two questions.

First, which alternative was chosen because of it, by whom? Not which insights it generated. Which commitment it caused.

Second, what does an ordinary Tuesday do differently now? If the answer to both is nothing, the study was decoration. That is not a verdict on the analyst’s competence. It is a verdict on the brief they accepted, which is the subject of the rest of the method.

The uncomfortable count

Run it across a year rather than a single study. How many of the analyses your function produced last year changed an operating rule?

Most organizations have never counted, and the count is usually low enough that nobody wants it in a slide. It is the single most useful number a technical leader can have, precisely because it cannot be argued with and cannot be met by working harder.