“It is not enough to be industrious; so are the ants. What are you industrious about?”

— H. D. Thoreau

Many decisions fail not because the idea was wrong, but because the wrong room tried to do the wrong kind of deciding. You demand operational certainty before you will approve a strategic direction. Or you let an operational tweak quietly rewrite the strategy, and never notice the swap. Either way, the work gets done, the room aligns, and the system still moves in the wrong direction. It is drift that feels like progress. So what is the question no one asks? At what altitude does this decision belong?

Altitude is the name for what is going wrong. Strategy, tactics, and operations are not levels of detail. They are different decision regimes, and each runs on its own proof standard, its own tempo, its own way of being governed. Strategy sets direction and the non-negotiables; it needs coherence, a clear beneficiary, and priced trade-offs, not perfect data; tactics turns direction into a sequence of reversible bets: believable steps, clear thresholds, a first move that earns learning without burning what matters. Operations executes this week, and needs crisp ownership, a definition of done, and clock time.

The proof standards are where it bites. Strategic proof is directional; it accepts irreducible uncertainty, because the future cannot be measured in advance. Operational proof wants the opposite: hard numbers, a definition of done. This is not to say the tiers never speak to each other. A strategic bet is sharper for some operational data, and an operation runs better with strategic clarity above it. What cannot cross is the proof bar. Demand the operational bar to approve a strategic move, and you wait forever for a certainty you will never get. Apply the strategic bar to an operational task, and you drown the operation in an ambiguity it cannot execute against. So where does it break? Not in the information. In the filing. The trouble is never that a tier lacks what it needs to know; it is that the question got answered at the wrong table, against the wrong standard of proof.

Do not confuse this with levels of detail, which is the misunderstanding that does the damage. Detail says the tiers differ in zoom, the same picture seen closer. Regime says they differ in kind: what counts as a good answer is not the same at each. Ask a strategic question in an operations room and you get paralysis, because strategy can never meet the operational standard of proof. Ask an operational question in a strategy room and you get churn, because operations cannot tolerate strategic ambiguity.

The error is durable because it is draped in discipline. Demanding hard numbers before approving a direction feels rigorous. Debating the ten-year mission before settling a font size feels thorough. Both are category errors. And the cost compounds into something worse than a single bad call: the institution loses the ability to tell motion from direction. Strategic churn sets in when daily noise keeps rewriting the destination, and operational paralysis sets in when execution stalls, waiting for a certainty that strategy was never going to provide. Worst of all is fake alignment, when the room agrees at one altitude while reality is demanding a decision at another, and everyone leaves satisfied that something was settled when nothing was.

Altitude language can become a bureaucratic escape hatch, and the risk is real. A leader can say that’s a strategy question, not an ops question to duck the decision, kick it to another table, and call the evasion process. Naming the tier could become a way to never answer at any tier. But the discipline is not to wall the regimes apart so questions bounce between them. It is to route each question to the table that can resolve it, answer it there at the right standard of proof, and bring the answer back. The aim is faster resolution, not ping-pong between tables. Altitude discipline that delays a decision has been inverted into the drift it exists to prevent.

The intervention, when your room fogs, is not to argue harder. It is to reset the altitude. Blockbuster shows the cost of failing to. In 2000, Netflix offered a partnership for fifty million dollars, and Blockbuster declined. The refusal usually gets filed under failure of vision. It was closer to a failure of altitude. At the operational level, late fees were a brilliant mechanic, throwing off sixteen percent of revenue at almost no cost. So when the strategic question arrived, whether to pivot to streaming, it got answered in the operations room: no, because subscription models kill late fees, and the company could not absorb the operational hit. An operational line item was allowed to veto a strategic survival move. They demanded operational certainty, protection of a current profit stream, before they would make a strategic bet, which is to ask the future to prove itself using the metrics of the past.

The reset would have sounded like this. Stop the profit-and-loss debate and name the tiers out loud: we are letting a billing mechanic decide our survival. The strategic question is whether physical distribution is dying. If it is, late fees are already dead, and we pivot regardless of the near-term cost. Settle the strategy first, and solve the lost revenue second, at the operational table where that question lives.

That is the move in general. When a decision fogs, name the tier your question belongs to, rewrite it in one sentence at that tier, and only then debate. A strategic question should sound like direction and non-negotiables. A tactical one should sound like the next reversible bet. An operational one should sound like ownership and a deadline. Then send everything else up or down to the table that owns it.

A room will settle a font in an afternoon and leave the survival question for a quarter that never comes. So before your room argues, fix the altitude the question is being asked at. Name the tier first, then decide. Because if you cannot name the tier, you are not deciding. You are performing seriousness.

Decision Rule — The Altitude Rule

When a decision fogs, stop arguing and fix the altitude before you continue.

• Name the tier. Is this a question of strategy (direction and non-negotiables), tactics (the next reversible bet), or operations (ownership and clock time)?
• Rewrite the question. State it in one sentence at that tier, in that tier’s language.
• Route it. Send the question to the table that can resolve it at the right standard of proof, and return the answer, rather than answering it at the wrong altitude.

If you cannot name the tier, you are not deciding. You are performing seriousness.

Name the altitude before you argue the answer.