Forty-Seven Slides and the Rule Did Not Change

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 the 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.

This is not a story about a bad team. It is the modal outcome of good technical work in most organizations, and it repeats because nothing in the sequence was obviously wrong.

The work was aimed at the wrong product

The product is not an explanation of last quarter, however accurate. It is a commitment to one alternative over others, made by someone with authority, under uncertainty, that will still be in force after the meeting ends.

Test the forty-seven slides against that definition and every clause fails. There is no commitment, because a dashboard commits to nothing. There is no owner, because the deck was addressed to a meeting. There is no alternative set, because nothing was being chosen among. And there is no operating process at the end of it, because the deck was the deliverable.

What the team produced was a description. Descriptions are not worthless, and they are not what anyone was asking for.

Why this is so hard to see from inside

Because effort and correctness are tightly coupled everywhere else in a technical career, and nothing announces when they stop being coupled.

For a decade or more, the derivation is what gets graded. A proof that asserts its conclusion without steps is worthless. A benchmark without methodology is not evidence. Showing the work is not merely permitted, it is the deliverable, and people who are good at it get promoted.

Then the audience changes and nothing flags the change. The same person produces the same artifact for a vice president, and the artifact is now the wrong shape. Six weeks of work reads as six weeks of work, and six weeks of work was never what was being purchased.

The failure is therefore systematic rather than individual, which is the only reason it is fixable. Individual failures require better people. Systematic ones require a different starting move.

The three places it breaks

Three parts have to be present or you have a study rather than a decision, and most work is missing exactly one.

The choice. The alternatives, including the status quo, who can commit, by when, and whether this fires once or repeats. When it is absent, the work produces a tour: interesting cuts, no owner, no freeze date, a dashboard that can be admired.

The evidence. Only what could change the ranking of those alternatives, not what would be interesting. When it is absent, the work produces a sales document: a pick with no killable reasons, or reasons that could not change the ranking if they turned out to be false.

The rule. What the operating process does now, who runs it, and when it is revisited. When it is absent, the work produces a good meeting: agreement in principle, and Tuesday unchanged.

The forty-seven slides were missing the first, which is why the third never had a chance. You cannot install a rule for a decision nobody specified.

What would have happened instead

The same brief, handled differently, starts with a sentence rather than an extract.

By the April freeze, Priya will choose among keeping the current replenishment rule, imposing a blanket inventory cut, or adopting a class-based stocking rule, in order to reduce working capital without stranding repair jobs, knowing that we will not have a reliable per-item demand model by then.

That sentence takes fifteen minutes to write and it is not easy, because getting it agreed requires finding out who Priya is, when the freeze actually falls, and what the third alternative even is. Those fifteen minutes are the ones that were skipped.

Notice what the sentence does to the workplan. It makes the demand model optional, because it is not needed to rank three rules by April. It makes a concentration analysis mandatory, because if the misses are spread evenly across item classes then class-based stocking is theater and one of the three alternatives is already dead. It gives the project a stopping condition, which an exploratory phase does not have.

Most of the forty-seven slides do not get made. That is the point, and it is why this is difficult to adopt: the method’s first visible effect is that your output looks smaller.

The count worth running

Take the studies your function produced last year. How many 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 also the single most useful number a technical leader can hold, because it cannot be argued with, it cannot be met by working harder, and it reframes every subsequent conversation about headcount and tooling.

The next email will still ask for a dashboard by Friday. Write the sentence anyway.