How Do I Get My Managers to Make Decisions Faster Without Becoming Reckless?

Start by stopping the one-size-fits-all decision process

Not every decision deserves the same amount of attention. Choosing whether to trial a new meeting format is not the same as signing a five-year lease. Changing a minor internal process is not the same as terminating a senior employee. Managers need to learn to recognise the difference. Ask how consequential the decision really is A useful first question is:

“What happens if we get this wrong?”

Minor inconvenience? Recoverable cost? Customer irritation? Major financial loss? Legal exposure? Safety risk? The consequence should influence the process.

Reversible decisions should usually move faster

If you can: try it; see what happens; change it back, why spend three weeks debating it? Make a reasonable decision. Test. Learn. Adjust.

Irreversible decisions deserve more care

Some decisions are difficult or expensive to reverse. Major capital. Senior appointments. Legal commitments. Significant structural change. Slow down where consequence justifies it.

Teach managers to distinguish the two

A lot of decision delay happens because managers treat reversible decisions as though they are permanent. They want certainty before moving. There may be no need. Ask:

“If this doesn’t work, can we undo it?”

If yes, perhaps the threshold for action should be lower.

Use small experiments

Rather than debating whether an idea will work for six months: trial it for four weeks. Define what you expect. Measure. Review. That often produces better evidence than another meeting.

Do not experiment casually with serious risk

Again, proportion. Safety, ethical and legal issues require appropriate controls. Common sense still applies.

Clarify decision authority

A manager cannot make decisions faster if they do not know whether the decision is actually theirs. Who decides? What can they approve? What needs consultation? What must be escalated? Clarity removes delay.

Unclear authority produces cautious managers

They think:

“I could decide, but what if the CEO disagrees?”

So they ask. Again. And again. If you want speed, give people real boundaries.

Do not retain invisible veto rights

This is common. The manager officially has authority. But everybody knows the owner might later say:

“Why did you do that without asking me?”

That is not real authority.

If you give authority, honour it

Within agreed boundaries. You can still coach the decision afterwards. But do not make independent judgement feel unsafe.

Ask managers to bring a recommendation

Decision speed improves enormously when people arrive having thought. Not:

“What should we do?”

But:

“I recommend option B because…”

Now the conversation starts further forward.

Recommendation first

Before you offer your view, ask:

“What do you recommend?”

Then:

“Why?”

You learn far more about the manager’s judgement that way.

Ask for enough evidence

Not every possible piece of evidence. Enough. This is an important distinction. Managers can always find another: report; survey; opinion; meeting; spreadsheet. The question is:

“What information do we actually need to make a sensible decision?”

Ask what information would change the decision

This is one of the best tests.

“What are we still trying to find out?”

Then:

“If we knew it, could it genuinely change what we decide?”

If not, stop collecting it.

More data can become procrastination

Managers sometimes call it diligence. It is really discomfort. They hope one more piece of information will remove uncertainty. It often will not.

Business decisions rarely come with perfect certainty

At some point the manager has to choose. That is part of leadership.

Teach managers to decide with incomplete information

Not carelessly. Intelligently. What do we know? What do we not know? How important is the uncertainty? Can we mitigate it? Then decide.

Separate uncertainty from risk

They are not identical. You can be uncertain about something with low consequence. Or quite certain about something carrying huge consequence. Managers need to understand both.

Ask about probability and consequence

A useful mental model: How likely is this to go wrong? And if it does, how bad is it? That improves calibration.

Do not make every unlikely risk a reason to stop

A business can become paralysed by hypothetical possibilities. Ask:

“How material is this really?”

But do not wave away low-probability catastrophic risks Again, judgement. Some consequences justify more care even when probability is lower.

Set decision deadlines

If the issue matters, say when it will be decided. Otherwise consideration can stretch indefinitely.

“Decision by Thursday.”

Useful.

Give consultation a time limit too

“Get Finance’s input tomorrow. We decide Wednesday.”

Now consultation supports the decision rather than consuming it.

Clarify who actually needs to be consulted

Everyone? Probably not. Who has: relevant expertise; critical information; a genuine dependency? Ask them.

Do not confuse stakeholder impact with decision rights

Many people may be affected. That does not mean all of them need to approve. Some need consultation. Some simply need communication afterwards.

Separate four roles

For significant decisions, clarify: Who decides? Who advises? Who approves, if anyone? Who needs to know? That removes enormous confusion.

Stop consensus-seeking

Managers can consult. Listen. Challenge their view. Then somebody needs to decide. Universal agreement is rarely necessary.

Decision speed improves when managers can tolerate disagreement

Someone may dislike the call. That is not automatically a reason to delay.

Teach “challenge before, alignment after”

Before the decision: debate. After the decision: execute. That keeps the organisation moving.

Ask whether another meeting will genuinely help

This question can save hours.

“What will we know after the next meeting that we do not know now?”

If the answer is unclear, perhaps decide.

Meetings should land somewhere

Decision. Action. Specific further evidence required. Or conscious decision not to proceed. Not:

“Let’s keep thinking about it.”

forever.

Use written preparation

For larger decisions, ask managers to arrive with: the issue; evidence; options; recommendation; risk. Then meeting time is used to challenge thinking. Not discover the issue.

Writing forces clarity

A manager who cannot explain the decision in one page may not yet have clarified the problem. That does not mean every decision needs a document. Use proportion.

Stop requiring paperwork that adds no value

Bureaucracy can be just as reckless as speed if it prevents timely action. Every process should earn its place.

Ask what the decision process is protecting

Legal requirement? Financial control? Safety? Or historical habit? Keep the useful controls. Remove redundant ones.

Decision-making slows when approvals accumulate

Manager. Senior manager. Finance. CEO. Maybe board. Why? Some approvals are necessary. Some are fossils. Review them.

Set approval thresholds

Perhaps managers can make ordinary decisions under a clear financial or risk limit. Only exceptions rise. That speeds the business.

Use exception-based escalation

If inside agreed boundaries: decide. Outside them: escalate. Simple.

Make the boundaries visible

Managers should not need to rediscover them on every issue.

Teach when escalation is genuinely appropriate

Safety. Legal. Ethical. Material financial exposure. Serious reputation risk. Outside delegated authority. Potentially irreversible high-consequence decision. Those are sensible reasons.

Discomfort is not necessarily a reason to escalate

This distinction matters. The manager may be perfectly authorised. They simply do not like making the call. That is a development issue. Ask:

“Is this outside your authority, or outside your comfort zone?”

Very useful question.

Do not let escalation become insurance

Managers sometimes escalate so that if the decision fails they can say:

“Well, the CEO agreed.”

That weakens ownership.

Encourage ownership language

“This is my recommendation.”

“This is my decision.”

That is healthy when appropriate.

Accountability should follow authority

If you allow managers to decide, they also need to review the consequence. What happened? What did we learn? That closes the loop.

Post-decision review is how speed becomes safer

This is critical. You can allow faster decisions when the organisation is good at learning afterwards. Decision. Result. Review. Adjust. That builds judgement.

Review decisions without hindsight arrogance

Do not say:

“Obviously that was wrong.”

Was it obvious at the time? Judge the reasoning fairly.

Ask what was known then

Not what everybody knows now. That creates a much better learning culture.

A bad result can follow good reasoning

Business contains uncertainty. Do not punish sensible judgement simply because the outcome was disappointing.

A good result can follow terrible reasoning

Do not ignore that either. Luck is not a management system.

Review decision quality and outcome separately

Ask: Was the process sound? Was the result good? Those are two different questions.

This helps managers become faster over time

Because they learn: which evidence matters; which risks matter; which consultations matter. Experience reduces unnecessary processing.

Capture recurring decision knowledge

If a similar question will appear again, record: what mattered; what was decided; why. Then the next manager does not start from zero.

Do not require every future case to be identical

Context changes. Captured knowledge should inform judgement. Not replace it.

Decision frameworks are useful for recurring issues

For example: pricing exceptions; customer credits; stock levels; recruitment approvals. Set sensible criteria. That speeds routine decisions.

Keep judgement for exceptions

Not every unusual case needs a new policy. Sometimes you just need a capable manager.

Build confidence through low-risk decisions

If a manager is too cautious, do not start by handing them the biggest decision in the company. Give them more real, recoverable decisions. Let them build evidence that they can decide.

Autonomy should expand with capability

Good judgement. Reliable follow-through. Early warning. Then wider authority. That is a sensible progression.

Watch whether managers wait for reassurance

They may already know the answer. But still ask:

“Do you agree?”

Sometimes useful. Sometimes dependency. Ask:

“Are you asking for my input, or my permission?”

Make them name which That alone can improve self-awareness.

Teach them to consult specialists without transferring ownership

Manager asks Finance:

“What financial risk do you see?”

Good. Not:

“Finance, tell me what decision I should make.”

The manager still carries the decision if it is theirs.

Use specialists for expertise

Not avoidance.

Teach managers to recognise decision traps

Common ones include: waiting for certainty; seeking unanimous agreement; overweighting the latest anecdote; avoiding uncomfortable consequences; making decisions too quickly to escape discomfort. Awareness helps.

Fast does not mean impulsive

A manager can decide quickly because: the decision is routine; criteria are clear; risk is low; evidence is sufficient. That is good speed.

Reckless decisions often skip important questions

What is the risk? Who is affected? Do I have authority? What evidence do I have? Managers need a short mental check.

Use a simple fast-decision test

Ask: Is this mine to decide? Is it reversible? What is the consequence if wrong? Do I have enough evidence? Who genuinely needs input? What do I recommend? Then act.

That should not take a week for ordinary decisions

The discipline is simple.

Slow down deliberately when the answer changes

High consequence? Difficult to reverse? Limited evidence? Important stakeholder dependency? Then invest more time.

Decision speed is about calibration

Not always faster. Correct speed. That is much more sophisticated.

Create three decision categories if useful

Fast decisions

Low consequence. Reversible. Within authority. Make them.

Considered decisions

Moderate consequence. Some dependencies. Gather relevant evidence and input. Then decide by a set date.

High-consequence decisions

Major risk. Hard to reverse. Use deeper review and appropriate escalation. This gives managers a practical mental model.

Avoid twenty-seven categories

Keep it usable.

Ask why the business is slow today

Is it because managers lack: authority? confidence? information? decision rules? Or because senior leaders keep taking decisions back? Diagnose the actual cause.

Decision delay can be a leadership-system problem

Do not simply tell everybody:

“Be more decisive.”

That is not enough.

Review the journey of a slow decision

Pick one. When did the issue first appear? Who touched it? How many approvals? How many meetings? Where did it wait? That reveals friction.

Remove unnecessary handoffs

Every extra handoff adds time. Does it add value?

Decision queues matter

Perhaps one senior person has become the approval bottleneck. That is an organisational design issue.

Push routine decisions down

If the capability exists. Then build capability where it does not.

Do not solve bottlenecks by lowering standards

Faster does not mean sloppy. It means designing a better decision system.

Give managers access to information

Waiting often occurs because only senior people can see the data. Share appropriate information.

Real-time enough matters

If managers wait two weeks for basic business information, decision speed will suffer.

Dashboards can help

The right numbers make decisions easier. But the dashboard still requires thought.

Evidence should guide, not paralyse

A number tells you where to think. Not necessarily exactly what to do.

Teach managers to prioritise decisions

Some decisions deserve immediate attention. Others can wait. A manager who treats everything equally wastes capacity. Ask:

“What decision, if made today, unlocks the most progress?”

Very useful.

Focus on blockers

Sometimes a whole project is waiting on one decision. Make that visible.

Weekly leadership meetings should surface decisions

Not merely report what everybody did. Ask: What decision is needed? Who owns it? By when? That creates momentum.

Do not let the same decision return every week

If no new evidence is required, decide. Repeated agenda items are often evidence of avoidance.

Challenge vague “we need more information”

What information? Who is getting it? By when? What decision will it inform? Make it specific.

Then return to it

If the evidence arrives, make the decision. Do not start another loop.

Teach managers to distinguish an action from a decision

“We’ll investigate further.”

That may be an action. The decision is still outstanding. Make that visible.

Give one person ownership

No group ownership fog. One owner for driving the decision to conclusion.

Create decision logs for important calls

What was decided? By whom? When? Why? That reduces reopening.

Stop revisiting settled decisions without new evidence

Constant reopening slows execution and weakens confidence.

Make the threshold for reopening clear

New material evidence. Changed risk. Changed circumstances. Not: someone remains unhappy.

Protect managers from endless second-guessing

If senior leaders continually reopen sensible decisions, managers will become slow. That is predictable.

Senior leaders need decision discipline too

CEO changes mind every two days? Priority shifts? Overrides? Then manager speed will fall because everybody learns to wait.

Consistency at the top creates speed below

People know the rules. They know authority is real. They can act.

Leaders should model decision ownership

“I made this call based on the information we had. Here’s what we learned.”

That is healthy.

Do not perform certainty

A leader can say:

“I’m not completely certain, but we have enough to decide.”

That is realistic.

Confidence is not certainty

A manager can be confident in the process while recognising uncertainty in the outcome.

Teach provisional commitments

“We’ll proceed with X for four weeks and review against Y.”

That can speed appropriate decisions.

Use stop-loss points

For some choices:

“We proceed unless X occurs. If it does, we stop.”

That controls risk without preventing action.