Decision-Making Is a Discipline

I’ve been thinking about why smart, experienced people — people who clearly care about doing good work — still end up in situations that feel stuck.

Not stuck in an obvious way. Stuck in the way where things look fine on the surface, the meetings are happening, the reports are going out, and yet somewhere underneath it all there’s a quiet unease. A sense that something important isn’t quite right, but it’s hard to name.

I think a significant part of it comes down to this: most of us were never taught to treat decision-making as something you build deliberately. We were taught to make decisions. Not to understand them.

That’s worth sitting with.

Not All Decisions Are the Same Weight

One thing that’s helped me think more clearly is recognising that we’re making three fundamentally different types of decisions — and they deserve very different amounts of our attention.

Micro decisions are the daily automatic ones. Which meeting to take. How to respond to an email. These should cost us almost nothing. If they’re draining significant energy, that’s usually a signal that something in our systems or delegation isn’t working — not that we’re deciding badly.

Macro decisions are the ones that shape direction. Which system to commit to. How to restructure a team. Who gets a critical role. These carry compounding consequences in both directions — and they’re expensive to reverse. A macro decision made in 2022 can still be shaping outcomes in 2026, through symptoms that nobody traces back to the original choice.

Strategic decisions are the rarest. These are what Jeff Bezos called one-way doors — decisions where reversing course is genuinely costly or impossible. They deserve disproportionate care, not because the stakes are always visible in the moment, but because by the time they become visible, the decision has already been made.

The pattern I notice most often — in organisations I work with, and honestly in my own thinking — is applying micro-decision energy to macro and strategic choices. Moving quickly because movement feels productive. Treating a two-hour workshop as a decision-making process when the decision actually needed weeks of careful consideration.

What Gets in the Way

We don’t usually struggle to decide. We struggle to understand what we’re actually deciding.

The cost of a bad decision is often invisible until it isn’t.

There’s a well-documented case from UK retail — a major ERP implementation where steering committees received green status reports for over a year. The system went live. Within months, significant inventory discrepancies surfaced, costing tens of millions to unwind. The critical decision wasn’t the go-live. It was made quietly, months earlier, when nobody adequately questioned data readiness. It took less time than a routine ops meeting.

The problem wasn’t the decision itself. It was that nobody in the room had a clear picture of what getting it wrong would cost.

I’ve sat in similar rooms. The pressure to keep moving is real. The discomfort of slowing down to ask hard questions is real. It’s not a character failure — it’s a system that rewards motion over meaning.

External noise can quietly replace internal judgment.

When “digital transformation” became the dominant industry narrative, many organisations committed to major programs not because they had a clear picture of their own need, but because not committing felt like falling behind. Some of those programs are still running — years past original timelines, well over budget, with benefits still unmeasured.

We’re all subject to this. The last conference we attended, the vendor with the compelling demo, what peers in similar organisations are doing — these shape our thinking without always announcing themselves. Noticing that influence, and separating it from what your organisation actually needs, takes deliberate effort.

The decision often isn’t named clearly enough to be made well.

This one is subtle. Kodak’s leadership didn’t decide to ignore digital photography. They decided to protect film margins — which is a different decision, made with a different frame, producing a different outcome. The decision they thought they were making and the decision they were actually making weren’t the same thing.

When we don’t name the decision accurately, we can optimise for the wrong outcome with perfect precision and complete sincerity.

What the Discipline Might Look Like

A few things seem to matter most.

Naming the decision type before making it. Is this micro, macro, or strategic? One-way or two-way door? If that’s hard to answer quickly, it might be worth pausing before moving forward.

Matching effort to consequence. Most of our attention goes to what’s urgent. Strategic decisions are rarely urgent — until they are. Creating protected time for the decisions that matter most, before they become crises, is something worth considering as a deliberate practice rather than an aspiration.

Creating conditions where truth can surface early. The organisations that tend to make better decisions aren’t necessarily smarter. They’ve usually built environments where problems can be named before the status report is written, before the vendor relationship becomes political, before the sponsor has publicly committed. That kind of culture doesn’t happen by accident.

Expanding decision inputs deliberately. Our instincts are shaped by our own experience — which means they have the sample size of one career. Independent perspectives, whether through advisors, mentors, or structured challenge, aren’t a sign of uncertainty. They’re a recognition that the higher we sit, the less unfiltered information tends to reach us.

What I Keep Coming Back To

Organisations don’t drift into difficulty because people stop caring or stop deciding. They drift because the decisions keep happening — at pace, habitually — without anyone examining whether the quality of the decision-making itself is holding up.

The reports stay green. The milestones get checked. And somewhere underneath all of it, a decision made a year ago is quietly compounding into a problem that will take far longer and cost far more to correct than the original choice would have.

That’s not a technology problem. It’s not usually a people problem either. It’s what happens when decision-making runs on autopilot — when we’re so focused on moving that we don’t stop to ask whether we actually understand what we’re deciding, and what it might cost if we’re wrong.

The question worth sitting with isn’t whether we’re making decisions. We all are, constantly.

It’s whether we’re building the discipline to make them well — or whether we’re leaving that to chance, and hoping the reports stay green long enough.

SP Singh is the founder of Bhani Consulting. He provides independent ERP oversight and advisory to executives in WA local government, Aboriginal corporations, and mid-sized organisations. bhaniconsulting.com