Not every yes is a decision

A company of three hundred people says yes to things hundreds of times a week. Approve this expense. Hire this candidate. Accept this vendor's quote. Extend this person's leave. Each one feels like a decision. Each one gets called a decision. And in most cases, it is not.

It is a choice. And the difference matters more than it looks.

A choice follows a rule. A decision makes one.

When a manager approves a promotion, she is making a choice. She is applying criteria that already exist. The competency framework says that at this level, the company looks for strategic influence, not only delivery. She looks at the person, she looks at the framework, and she says yes or no. The framework did the deciding. She did the choosing.

When a procurement lead picks a vendor from three quotes, he is making a choice. The procurement policy says anything above ten lakhs needs three quotes, the lowest qualified bidder gets the work unless there is a documented reason to go otherwise. He follows the policy. The policy did the deciding. He did the choosing.

When finance releases a payment against an approved purchase order, that is a choice. When HR processes an increment within the band, that is a choice. When a regional head extends credit within the approved limit, that is a choice. All of them are governed by something upstream, a rule or a policy or a framework that somebody, at some earlier point, put in place.

That earlier point is where the decision lives.

The competency framework itself. Who wrote it, why those eleven competencies and not six, why strategic influence sits where it sits, why delivery alone is not enough past a certain level. That was a decision. It was made once, probably in a room, probably in 2019, and it now governs every promotion the company makes.

The procurement policy. Why ten lakhs, why three quotes, what counts as a documented reason to override. That was a decision. It shapes hundreds of vendor selections a year.

The approval limits. The credit terms. The travel policy. The increment bands. Every one of these was decided once and then followed thousands of times. The one-time act was the decision. The thousand-time acts are choices.

Companies are very good at keeping choices

This is the part that hides the problem.

Every choice those three hundred people make gets captured somewhere. The purchase order goes into the procurement system. The hire letter goes into the HRMS. The expense claim goes into the finance tool. The leave approval goes into the portal. Companies have built entire software categories to record these, and they work well. Every PO is numbered, dated, approved, stored, and auditable.

So it feels like the company has a grip on its decisions. Look at all these records. Look at all these approvals. Everything is tracked.

But what is tracked is the choosing, not the deciding. The system captured the vendor selection. It did not capture the procurement policy that governed it. The system captured the promotion. It did not capture the competency framework that determined it. The system captured the payment within the approved limit. It did not capture who set the limit, or why, or whether the number was principled or just a round figure someone picked in a different year.

Every choice, recorded. Every decision behind it, gone.

Why this is expensive?

A choice made within a good rule is a good choice. A choice made within a rule nobody can explain is a gamble wearing a suit.

Here is what happens. A manager is sitting across from someone whose promotion she just denied. She reads the criteria from the framework. Strategic influence, not only delivery. The person asks why. Why is strategic influence the bar. Why does it outweigh two years of delivery nobody disputes. And the manager has no answer, because the framework was decided before she arrived, and the reasoning was never written next to the words.

She is not being arbitrary. She is being exactly as consistent as the company asked her to be. And she cannot justify the consistency, because the decision underneath her choice is missing.

That person goes away and draws one of two conclusions. Either the criteria are genuinely right and the manager just cannot explain them, which is frustrating but survivable. Or the criteria are arbitrary, which means the system cannot be trusted, which means the rational move is to stop trying to work within it and start trying to work around it.

Multiply that by every rule in the company whose basis has been lost. The ten lakh threshold that may or may not make sense any more. The credit terms that differ by region for a reason nobody can reconstruct. The approval limits that were set in a different year at a different scale. The travel policy exception clause that exists because of one bad trip five years ago.

Every one of those is a decision that people are choosing within, every day, without knowing whether the decision still holds. And they cannot check, because the decision was never kept. Only the choices were.

The inversion

This is the thing that took me longest to see.

Companies have invested enormously in recording choices. Procurement systems, HR platforms, finance tools, ticketing systems, approval workflows. Billions of dollars of enterprise software, all designed to capture the downstream selections that people make within existing rules.

Almost nothing, anywhere, captures the rules themselves. The upstream decisions that all those choices rest on. The policy that was written in a workshop. The framework that was adapted from a consultant's model. The limit that was set on a phone call. The terms that were negotiated in a corridor.

The choices are the visible part, the part that feels like work, the part that gets a system built for it. The decisions are invisible, because they happen once, in a room, and then everything after them looks like the company simply doing what it does. Nobody notices that the thing the company does rests on something somebody decided and nobody kept.

A choice without its decision is a building without its foundation. It stands, it functions, it looks solid. You only find out the foundation is missing when somebody leans on it too hard, or when the ground shifts, or when somebody new arrives and asks what the building is standing on.

How to tell the difference

Stand in front of any approval in your company and ask one question: am I applying a rule, or am I making one?

If you are applying a rule, this is a choice. The rule should be on record somewhere, with its reasoning, and you should be able to point at it.

If you are making a rule, or changing one, or bending one, this is a decision. It should be recorded properly, with who made it, on what basis, and under what conditions, because everything that follows will rest on it.

If you are applying a rule and you cannot find the decision behind it, you are in the position of most managers in most companies. Following something you cannot explain, enforcing something you cannot justify, choosing within a framework whose own basis is gone.

That gap between the choice you are making and the decision you cannot find is where the cost lives. It shows up as arguments that cannot be resolved, because there is no record to resolve them against. It shows up as rules that run forever past the conditions that created them. It shows up as the manager sitting across from the person she just denied, reading words from a framework, unable to explain why those words and not others.

The choices are fine. The decisions underneath them are what the company needs to start keeping.

Part of The Other Books, an ongoing series on the decisions companies forget.