Every decision you avoid gets made anyway

An unmade decision does not sit quietly and wait for you. It gets made nine times a week by people who do not know they are making it.

A salesperson calls you on a Thursday. The prospect wants twelve percent off. Good logo, decent size, would close this quarter.

There is no discount policy. There has never been a discount policy, because every deal is different and writing one down felt like it would tie your hands. So you look at this specific deal, decide it is worth it, and tell her to go ahead. Use your judgment, you say. This one makes sense.

That is a reasonable answer. It is probably the right answer for that deal.

It is also the ninth time in six weeks someone has asked a version of that question, and you have given nine slightly different answers, and none of them are written down anywhere.

Not deciding is a decision. It just has a worse implementation.

Here is the thing leadership teams get wrong about deferred decisions. They think the choice is between deciding now and deciding later. It is not. The choice is between deciding once, deliberately, in a room where you can think about it, or having the decision made repeatedly by whoever runs into it next, under time pressure, with less context than you have.

The question does not wait. Somebody has a prospect on the phone right now. They need an answer today. If there is no policy, they will invent one, and it will be a reasonable invention based on what they know.

The next person will invent a different one.

Within a year you have three salespeople operating at three different discount floors, two of whom believe theirs is the company standard. You have a services team where “done” means one thing to the person who has been there six years and something looser to the person hired in March. You have a marketing team passing leads to sales under a definition of “qualified” that nobody ever ratified, which is why the two departments have been arguing about lead quality for eighteen months without either side being wrong.

None of that came from bad people. It came from a question that needed an answer and did not have one.

Why you never see it happening

If distributed decision-making were visible, it would get fixed. The reason it runs for years is that every individual instance looks fine.

Each call is defensible on its own terms. The rep gave twelve percent because the deal was good. The other rep gave twenty because that deal was competitive. The project manager signed off on a deliverable that was eighty percent there because the client was happy and the team was buried. Look at any one of those in isolation and you would probably have made the same call.

The damage does not live in any single instance. It lives in the variance, and variance only shows up in aggregate, and almost nobody in a growing business is looking at the aggregate. You would have to pull every deal from the last four quarters and chart the discounts to see the spread. Nobody does that, because the number that gets reported is average discount, and the average of twelve and twenty is a perfectly comfortable sixteen.

So the business feels fine, right up until the quarter where margin compresses and nobody can explain why. Or the client escalation where it turns out two teams had genuinely different understandings of what was promised. Or the good salesperson who quits because she found out she has been competing against a colleague who was allowed to give away more.

The failure never gets attributed to the unmade decision. It gets attributed to the incident.

The ones worth making

Not every open question needs closing. Most of a business is judgment, and it should be. But a small number of decisions get asked over and over by people who are not in the room with you, and those are the ones worth spending a Tuesday on.

What a good customer is. Not a persona document. A specific answer to: when we win one of these, we make money and the team likes the work, and when we win one of those, we lose on both. Until that is written down, every salesperson has their own version, and marketing is optimizing toward a target nobody has agreed on.

What happens to a lead after day five. Somebody decides this every day. Whether it goes back in the pool, whether it gets nurtured, whether it just sits in a stage called “working” forever. Right now the answer depends entirely on which rep owns it and how their week is going.

Where the discount floor is, and who can go below it. Both halves. A floor with no exception path gets ignored, which is worse than no floor.

What work you will not take. The hardest one, and the one that pays back most. Every business has a category of project that looks like revenue and behaves like a tax. If leadership has not named it, sales will keep selling it, because from where they sit it is a signed deal.

What “done” means for the thing you deliver. Not a quality aspiration. The actual checklist that separates shipped from shipped-ish.

None of these are strategy. They are the unglamorous rules that let a business run without every question climbing back up to the founder.

Why it feels safer not to decide

Because a decision can be wrong, and not deciding feels neutral.

If you set the discount floor at fifteen and it turns out to be too high, that is your call and you can see the deals you lost. If you never set one, you never lose a deal to a policy. What you lose instead is margin, spread thinly across every deal, invisibly, forever. There is no moment where anyone can point at the mistake, which is precisely what makes it comfortable.

The other reason is that deciding closes a door, and founders of growing businesses are correctly trained to keep doors open. Flexibility got you here. But flexibility at the leadership level and ambiguity at the operating level are not the same thing, and the second one is what you actually produce when you decline to answer.

A decision you make can be revisited in ninety days. A decision you avoid gets re-made nine times a week by people who will never tell you they made it.

How to actually close one

This takes less time than it seems, and the ceremony around it is usually what stops it from happening.

Write the answer in plain language, short enough to say out loud. If it takes a page, it is not a decision yet, it is still a discussion.

Name who owns it. Not a committee. One person who can change it and who people can go to when the situation does not fit.

Name the exception path, because there will be exceptions, and a rule with no legitimate way around it teaches people to route around it illegitimately.

Put a revisit date on it. Ninety days. This is the part that makes it possible to decide at all, because you are not committing forever, you are committing until you have evidence.

Then tell everyone the decision exists and where it lives. A policy nobody can find is the same as no policy, except now you also think the problem is solved.

The point

You are already making these decisions. Every one of them. The only open question is whether you are making them in a room, once, with the full picture in front of you, or whether you are making them nine times a week through other people who are guessing at what you would want.

The businesses that feel calm to work inside are not the ones with fewer hard calls. They are the ones where the hard calls were made on purpose, written down somewhere findable, and revisited when they stopped fitting.

Pick the question you have answered most often in the last month. That is the one. Go close it.


If your team keeps bringing you the same three questions and you can feel that the answers have been drifting, that drift usually has a structural cause and a findable one. A Systems Audit maps where decisions actually get made inside your business, which ones have no owner, and which two or three are quietly costing you the most.