Should I Make Fast, Unilateral Decisions to Keep Momentum, or Slow Down to Get Buy-In From My Management Team?
Two patients arrive at the same hospital within minutes of each other. One has a twisted ankle. The other has chest pain with an unclear cause. The doctor treating the ankle writes up a routine plan alone and moves on. The doctor treating the chest pain pages a cardiologist, and within minutes five people are standing over a scan together.
Nobody would say the second doctor is slower or less decisive than the first. The number of people in the room isn't a measure of speed or confidence. It's a response to what the case actually requires.
Two things decide whether a decision needs more input
Framing this as fast-and-alone versus slow-and-collective treats every decision as if it belongs to one category or the other by default. It doesn't. What determines whether a decision needs wider input is two specific things about it.
The first is whether someone else holds knowledge that would change the outcome. A manager who understands why a client relationship works a certain way, or who knows a technical constraint the owner doesn't, can change what the right call actually is. A manager whose input wouldn't touch the substance of the decision costs time without improving it.
The second is complexity and reversibility. A decision that's easy to undo if it's wrong doesn't carry much cost either way - the ankle gets checked, treated, and the patient goes home. A decision that's hard to reverse, or that has enough moving parts for a blind spot to hide in, benefits from more than one perspective looking at it before it's made. The more moving parts a decision has, the more places something can be missed, and another set of eyes catches what one alone would not.
β‘ Involve people when their knowledge can change the decision - not by default, and not never.
That's the actual test. It replaces "am I moving fast enough" and "am I including my team enough" with a narrower question: does this specific decision have a knowledge gap or a complexity profile that makes another perspective worth the time it costs?
Most decisions clear the bar in one direction fast
Run the test honestly and the answer usually comes quickly. A routine pricing exception, a scheduling call, a minor vendor swap - these clear the "no consultation needed" bar almost instantly, the same way a twisted ankle doesn't need a specialist paged in. Slowing these down to loop in the management team doesn't produce a better decision. It just produces a slower one.
A decision to restructure a service line, walk away from a major client, or change how the business is positioned is on the other side. These carry enough complexity and enough cost if they're wrong that pulling in the people who see angles the owner doesn't is worth the extra time it takes.
The mistake is applying a single default to every decision, regardless of what each one actually needs.
Implementation knowledge is a third reason to involve people
There's a third reason to bring someone in that has nothing to do with whether their input changes the decision itself: they're the ones who'll carry it out. A manager who'll be responsible for executing a decision often has knowledge about what will and won't work in practice - their knowledge shapes how the plan gets carried out, whether or not it shaped the decision itself.
That's a different question from whether the decision needs their knowledge to be made correctly. Both can be true for the same decision, and either can be true without the other.
The distinction that gets missed
Trust holds up when the amount of consultation matches what a decision actually required - a quick, solo call on a low-stakes decision, and a fuller consultation on one that genuinely needed several perspectives. Trust erodes when an owner applies the same amount of consultation to everything: always alone regardless of what a decision demands, or always deferring to the full room regardless of whether it needed one.
π What to do next
If this feels familiar, start here:
π Run the Second Look Decision Diagnostic to see whatβs missing before you decide
πSee related business decision
π π Read more on Second Look blog
You can continue with making the decision afterwwards.