Every Requirement Has a Name

Every requirement has a name. Somewhere, a person wrote it down. A CFO who wanted predictable revenue. A VP of Sales protecting a favored process. A founder who built the company around a single customer who is no longer even in the top ten accounts.

The constraints your team debates today were authored by people who are not in the room — and often no longer in the company. The first move of first-principles thinking is not to build something new. It is to audit the constraints you have inherited.

The audit

We start every engagement with the same exercise. Take the three most stubborn constraints in the business — the things everyone agrees cannot be changed — and ask, for each: who wrote this requirement, and what were they optimizing for?

The question sounds procedural. It is closer to archaeology. Pricing floors trace back to a board meeting nobody remembers; territory rules to a conflict between two managers who both left; the sacred product bundle to a customer whose logo came off the slide years ago. Nine times out of ten, the constraint was rational at the time. One time out of ten it was never rational at all.

Either way, the discovery is the same: the ceiling in the room is not the ceiling of the universe. It is the ceiling of the last generation of leadership.

Strategy done correctly is the practice of distinguishing physics from folklore.

Physics and folklore

There are real constraints. Cash is real. Regulation is real. The speed at which trust can be built with a market is real. The audit is not a license for wishfulness — it is a sorting exercise, and the sorting matters because the two categories demand opposite responses. Physics you design around. Folklore you delete.

The game-theoretic frame is useful here. A Nash equilibrium tells you what rational actors do given a payoff structure — not what the payoff structure has to be. Change the payoffs and the equilibrium moves. Most operators inherit the payoff structure of their industry as if it were weather. The interesting ones ask who set it up, and whether it can be re-authored the way it was authored.

But you cannot change what you do not believe is changeable. This is why the audit is cognitive before it is operational: before you can architect the new system, you have to grant yourself permission to question the old one. That permission is the scarcest resource in most organizations we walk into.

Naming the author

The technique that unlocks the audit is embarrassingly literal: put a name next to every requirement. Not a department — a person. “Finance requires twelve-month contracts” dissolves into “Daniel required twelve-month contracts in 2019 because the board was pricing the company on revenue predictability.” Now it can be examined. Daniel was optimizing for a financing event that closed years ago. The requirement outlived its reason.

Requirements without names are unfalsifiable, and unfalsifiable requirements accumulate like sediment. The discipline of attribution — who, when, optimizing for what — converts a company’s folklore back into decisions. Decisions can be re-made.

What this costs

The audit has a price, and it is worth naming: it produces conflict. Every inherited constraint has a constituency — someone whose work is organized around it, someone who mistakes the question for an accusation. A leadership team that wants the comfort of consensus should not run the exercise, because the exercise is designed to surface exactly the disagreements consensus has been papering over.

Our position is that the conflict is the point. A polite consensus around an unexamined constraint is the most expensive line item on the P&L, precisely because it never appears on it.

The ceiling in the room is not the ceiling of the universe.

The practice

This essay is the first thing we do on nearly every engagement, written down. We run the constraint audit; we trace authorship; we sort physics from folklore; and then — only then — we architect. Strategy that skips the audit optimizes brilliantly inside a box someone else drew.

The falsifiable claim, stated plainly: take your three most immovable constraints, find their authors, and reconstruct what each author was optimizing for. If all three survive the examination, your strategy problem is real and we would tell you so. In our experience, they rarely all survive. The move that transforms the business is usually hiding behind the one that doesn’t.