The Ridiculously Simple Decision-Making Framework for CEOs and COOs: How to Decide Faster Without Deciding Worse

Why the Leader Becomes the Decision Bottleneck

There are three main situations where a bottleneck forms:

1. With a founder-CEO, the shift hasn't happened: the move from entrepreneur, where everything rests on them, to leader, the keeper of the vision, the overall goal and the values. This is first and foremost a change of mindset. To grasp the difference between the two roles, think of the entrepreneur as an instigator and the leader as a visionary. The leader's job is to instill a vision, set the overall goal, and shape and embody the internal culture through values that cascade into behaviors. Neither the entrepreneur nor the leader is meant to be the conductor of the orchestra, which is exactly why a COO is appointed.
2. Growth phases aren't matched by a management structure sized to keep up. It's even truer, and more brutal, in hypergrowth, when you hire fifty or sixty people in a few months.

   A real client case: an accounting firm was opening offices in several cities, each one running faster and faster; it had to hire aggressively to keep up with the workload. The hiring focused on frontline staff first, because the urgency was to clear the case files. The result: with no middle management in place, a huge hierarchical gap had opened between the leader and the frontline. That gap is what created the bottleneck.

3. As a CEO or COO, you inherit an organization that's one in name only. An org chart whose job, remember, is to define the scopes of responsibility and the hierarchical levels that go with them, but that no one actually applies. Here the bottleneck comes mostly from the confusion around "who" decides "what." Decisions then drift, and that drift, sooner or later and at best, climbs back up the levels of the pyramid or, at worst, vanishes entirely.

A Decision-Making Framework You Can Actually Run

Let's kill another fashionable myth: "deciding under uncertainty," "deciding when you only have X% of the information." It means nothing. To know what percentage of the information you actually hold, you'd first need to be able to spell out precisely what the necessary 100% even is. The sheer human arrogance. We are limited beings: context, time, resources and information are all limited, and the information you hold may be false, incomplete or biased. So stop believing you decide with a "known percentage" of information: you have no idea. And that's fine. Every decision we make is made under uncertainty. Every single one.

Your Two Real Factors: Objective and Resources

The real framework comes down to two factors:

1. First, what do you want to achieve?
2. Second, what resources do you have, in terms of time, money, know-how, and people who are both available and willing?

From there, two outcomes: act right away, or wait, which is itself a form of decision if you want to give yourself time to refine a piece of information or wait for more.

The trap is the endless loop that has you waiting for complete information that will never come, since, remember, you don't even know what complete information would be.

Reversible or Not: An Insufficient Criterion

Of course, whether a decision is reversible or not is also a useful criterion, but it isn't enough. You also have to factor in the temperament, the personality, the level of intuition and of trust in that intuition of whoever decides, all of which is specific to each person. This is how you see leaders think and think again about a process that isn't remotely strategic. Take, for example, a customer-request process that already works, or would only need marginal improvement: some will pour considerable time and energy into it for very little real impact. So why do teams go round in circles on this kind of decision (reversible ones, by the way)? Often because of the egos in the room, or because no one was ever clearly put in charge of it. Everyone is looking for their place, and the whole thing bogs down.

Getting Buy-In: The Real “Disagree and Commit”

Now let's turn to "disagree and commit." Once the decision is made, some of those who took part in the thinking may not agree with your choice, and will still have to carry it out. Two things:

1. Let's stop putting the full responsibility for an employee's commitment on the manager: an employee is a human being, free to commit or not.
2. But be careful not to hide behind that handy phrase to push decisions through. A real client case: a sales management team that waits until May, nearly six months into the year, to set the year's sales targets. Those targets, of course, factor in the revenue already booked over the period: the number is inflated with full knowledge of what's been achieved, which is anything but ethical. For the teams, it amounts to working blind for six months, then watching their own performance be used to set a target that will largely drive their year-end bonuses. The employee quite understandably concludes that everything they've done so far counted for nothing. In this particular case, demanding a "Disagree and Commit" from the employee is unacceptable: the principle assumes an honest decision from the start. Here we're no longer in "disagree and commit," we're in "shut up and execute."

Of course, there's always the contractual approach: the subordinate is under contract; they have to carry out the order they're given. But it remains purely legal. So I'd suggest a sincere managerial approach instead. It rests on equally sincere listening, paired with adult-to-adult communication. The message to get across is simple: you'll hear the different views, but the decision will be yours, not because you're dismissing your people's positions, but because you have the full picture, while they only see one part of the chain. The rest is a matter of teaching and explaining.

Watch out for manipulation: listening only to let someone vent, without taking any of their input into account, is far more destructive than not listening at all.

Who Owns the Decision, and at What Level

Let's move on. Yes, in any organization worth the name, the decision belongs to someone. But to whom?

Responsibility and Authority, Inseparable

It's very simple: to the person whose responsibility it is. And here the word has two sides:

1. The responsibility to decide. Normally, employment contracts, the org chart and the targets to be met point to the people involved.
2. The responsibility for the outcome, the one that will be called upon when the consequences land, whether good or bad.

One more thing: there can be no responsibility in an organization without authority. The two are inseparable: you can't be held responsible for a scope without holding the authority to decide within it, nor claim an authority whose consequences you won't answer for.

Does that mean the team should decide? I don't buy it. In the thinking that leads to the decision, their input is valuable: it feeds the analysis and surfaces on-the-ground realities that decision-makers can't see. But the act of deciding must rest with a single person.

Now, of course, collective decision-making exists: on a board of directors, for instance, or when a decision is put to a vote. But in those cases, other forces come into play, even more strongly: competing interests, politics, the weight of the shares held, where the first person's voice doesn't always carry as much as the second's.

So the real question lies upstream: who should decide, and how was the decision process designed?

By Design, Not by Courage

It's airtight. If you're wondering who should decide at the very moment the decision lands, you're finally bringing to light a problem that, unfortunately for you, only gets solved upstream. In other words: no clear organizational structure, poorly defined scopes of responsibility, and authority that was never clearly distributed.

This falls to the leadership, and more precisely to operations. It's the COO who has to set clear operational and managerial boundaries. Each scope comes, by the way, with its responsibility, the authority to match and, automatically, its own decisions to make.

And we need to stop praising managers for having "the courage" to decide. A manager doesn't decide because they're brave, they decide because it's their role, because they're paid to, within their scope, using the authority their contract grants them. What is true, though, is that some managers fail to decide out of a lack of courage.

Beating Decision Paralysis

Nothing but the decision itself gets you out of paralysis. No extra information will help you; only the act of cutting through does.

Rest assured, there are a few levers and tricks if you really do struggle with decision-making:

1. If the stakes of the decision allow it, delegate it to someone else.
2. Set yourself a deadline, provided you back it with real performance pressure. A deadline that matches nothing in operations stands a good chance of being missed, because it creates no tension in the real world (and none in your head either, for that matter). Take a simple example: equipping the company with a CRM so the sales managers can announce their targets before the selling season kicks off. You can see that starting that season without the tool is impossible. Even if not all the vendors have gotten back to you, you'll have to decide as things stand to be operational by the deadline.
3. That leaves the most important lever: accept the incompleteness, right from the start. The information will always be incomplete, as I said earlier. When you hire, you'll never know the candidates whose résumés never reached you and who would have been a perfect fit. This incompleteness is a constant in every decision: accept it, and decide while taking it as a given.

The Takeaway

One last word. Don't blame yourself too much for your decisions, and don't congratulate yourself too much either. A decision is only the product of a host of parameters you don't control in the moment, and a decision once made could not have been otherwise. Believing the opposite means judging the past with the knowledge and the mood of the present: hindsight arrogance. Owning a decision means answering for it, without blaming yourself for it. A real decision-making framework rests as much on this clear-headedness as on method.