Decision Making

At work, decision making means weighing the options and the risks fairly, even under pressure, and committing in time to a clear direction, so the team can move.

Most decisions at work are small and frequent, like which tool to buy or whether to ship on Friday. The cost of a slow one is the work that waits behind it.

A good decision starts with a clear trade-off for each option, what it costs and what it gives, and a word with the people closest to the work. When a plan rests on one big assumption, a quick test comes before the full commitment.

Under pressure, the Skill is about distance. A good decision-maker asks how the choice will look in ten months, and weighs criteria like cost and speed by what matters most this time. A deadline next week and a deadline next year call for different weights.

At the highest levels, the trade-off is explicit. A leader weighs the cost of waiting against the cost of being wrong, and makes the unpopular call when the long term needs it, taking full responsibility for it.

Where it shows up

A software company sells two products: the billing tool it started with eight years ago, and a scheduling app for small clinics it launched last year. At the yearly planning meeting, the product lead has to decide where the team’s effort goes. Four options are on the whiteboard: split it evenly, lean toward one, put everything into one, or shut the other down.

A list of pros and cons would fill the board and settle nothing, so she takes the team through four questions instead. How much of the business does each product carry today, and which way is it moving? The billing tool still brings in most of the revenue, a little less every quarter, while the scheduling app is small and growing fast. If we hadn’t built the billing tool ourselves, would we start it today? That one gets a laugh, then a long silence. Where will each market be in three years? And what are competitors doing? Two large companies have just launched billing tools of their own, and nobody serves small clinics with scheduling yet.

By the end of the meeting, the billing tool gets what it needs to keep current customers well served, and most of the team moves to the scheduling app. They’ll look at the numbers again in six months.

An even split would have felt fair, and it would have kept both products at half speed. Weighing what each one is worth now and later, with some distance from the product everyone was attached to, is what turned a hard choice into a clear one.

What it changes at work

Waiting feels safe, but it’s a decision too.

In 2025, the Journal of Management Scientific Reports (a peer-reviewed journal of the Southern Management Association) published a meta-analysis by Kalin Kolev and colleagues covering 127 studies on how fast companies decide and act. Faster decisions were linked to better performance, and the link was stronger in fast-moving industries. It showed up mostly when managers rated their own company’s performance, though. With objective numbers, the link disappeared.

So the case for deciding fast is real, and it has a limit: speed pays when the decision is also sound. For a team of 12, that means making a call like the one between two products on time, after an honest look at what each one is worth, instead of letting it ride for another quarter.

What it looks like, from 0 to 20

Each level of Decision Making on Skill Deck’s scale, from 0 to 20, is a named Practice with a worked example. Here are three, from routine choices to high-stakes ones:

8, Option Expansion

Brings more than one real option to the table, so the choice isn't just yes or no.

15, Second-Order Logic

Looks at the ripple effects, like a price cut that will flood the support team, and plans for them before deciding.

17, Robust Contingency Architecture

Presents a risky plan together with the trigger that would stop it, so the exit is agreed before the start.

Skill Deck finds where each person stands from how they reach decisions in their real meetings.

One thing to try if you want to develop this Skill

We recommend starting with Practice 11, Autonomy Mapping. It solves a familiar problem: decisions that drift because nobody knows who makes the call.

1. Find a decision your team has discussed in more than one meeting without closing, like a new tool or a change to the schedule.
2. In the next meeting, before the discussion starts, name who will make the final call and the date it will be made.
3. Pick the person who will live closest to the consequences.

The discussion is the same. Now it has an owner and an end, and people know when to speak up.

Notice whether the decision lands on the date. If it does, and the team moves on to the work, the map did its job.