Decision-making under pressure

The problem it solves

In a small company most important decisions are made in a hurry, on incomplete data, and without a record. Not because anyone thinks that is good business, but because the day offers nothing else. Decisions get made standing up, between one phone call and the next, and whatever information is missing gets filled in with the decider's experience.

The signs are familiar. Minor matters get debated for weeks while large commitments — a long lease, a key hire — are settled in an afternoon. Meetings reopen questions everyone thought were closed, because nobody remembers what was agreed or why. Group decisions that go wrong somehow belong to no one. And one line keeps coming back: "we tried that already", with nobody able to say under what conditions.

The problem shows up later, in disguise. Because nobody wrote down what was decided or on what assumptions, there is no way to tell whether the decision was bad or whether it was good and turned out badly. Without that distinction there is no learning: the organization repeats the same mistake believing it had bad luck, or drops a sound practice because it once went wrong. Waiting has a cost as well, but delay never sends an invoice, so nobody sees it. Over time the company's judgment ends up stored in one person's memory, and walks out the door with them.

What it covers

The workshop does not teach better decision-making in the abstract. It works on an earlier question that almost never gets asked: what kind of decision is this, and which method does that kind call for? So it starts by sorting decisions by type. A cheap, reversible decision does not deserve the same process as an expensive, irreversible one, and treating them alike produces two symmetrical pathologies: paralysis on the small things and haste on the large ones.

Next comes the cost of waiting, the variable that almost never reaches the table. Postponing is deciding, and it has a price; the central exercise is putting a number on that price before postponing. Alongside it sits a distinction that changes how people decide in a hurry: sufficient information is not complete information, and under pressure, waiting for the missing figure is often the most respectable way of not deciding. The session also looks at the biases that surface specifically under urgency — anchoring on the first number anyone mentions, overweighting whatever happened last, closing a discussion just to end the discomfort — and at how to catch them as they happen.

Participants practice on their own material. Each brings real decisions, recent or pending, sorts them with the workshop's criterion, estimates what waiting costs in each case and runs them through the record format. The group then reviews a decision already taken, separating the quality of the decision from the quality of the outcome. It is an uncomfortable exercise, because it means owning up to good calls that turned out badly and poor ones that got lucky.

The last part installs the record: a short format capturing what was decided, on what information, what was expected to happen, and when it will be reviewed. That is what turns a decision into something the organization can learn from. It closes with an explicit rule on what gets decided alone and what gets decided together, and on how a group can decide without accountability dissolving around the table. Participants leave with a classification rule they have already tested, a one-page record filled in on their own decisions, and that rule in writing. In ALUD's Strategy work the same record serves another purpose: read back over the months, it shows which assumptions about customers, the market or the company's own capacity keep failing, and an assumption that fails repeatedly usually points to a question of direction rather than method.

What participants learn

• Classify a decision by reversibility and cost before choosing how to take it.
• Price the cost of waiting and treat postponement as the decision it is.
• Tell a bad decision from a bad outcome.
• Record decisions in a form that allows review and learning.
• Fix in advance when and on what evidence a decision will be revisited.

Agenda

1. 01Decision types: cheap and reversible versus expensive and irreversible
2. 02The cost of waiting: postponing has a price
3. 03Sufficient information versus complete information
4. 04Biases that appear specifically under pressure
5. 05Decision versus outcome: why confusing them blocks learning
6. 06The one-page decision record and its review
7. 07Deciding as a group without diluting accountability
8. 08What an organization that learns from decisions looks like

What the organization leaves with

• A classification rule for decisions, usable immediately.
• A one-page decision record format.
• A review carried out on three real decisions from the business.
• An explicit rule on what is decided alone and what is decided together.