The one idea
You will never have enough information. Waiting for certainty is itself a decision, usually the worst available, and it is made silently.
The question is not "how do I become sure?" but:
How hard is this to undo — and how much effort does that deserve?
Decide fast on things you can change your mind about. Slow down only on things you cannot.
Classify the decision by reversibility and consequence, set what would change your mind, decide, and write down why.
Match analysis cost to the cost of being wrong. For low-cost reversible decisions, the expected value of further information is usually below the cost of acquiring it — so deciding quickly is the correct answer, not a compromise.
Reversible or not
Everything here follows from one question, asked first.
| Reversible | Irreversible | |
|---|---|---|
| Examples | Trial a tool, change a meeting format, draft an approach, pick a first supplier | Sign a two-year contract, announce publicly, delete data, resign, tell a client a date |
| How much effort | Minutes to hours. Decide and watch. | Days. Get a second opinion. Write it down. |
| Failure mode | Over-analysing something you could have tested in a week | Deciding fast because it felt like the other kind |
The trap is not that people cannot tell the difference. It is that irreversible decisions are disguised as small ones. An email is reversible; an email to a client containing a date is not. A hire is reversible in theory and rarely in practice. Deleting anything is permanent.
The test: if this is wrong, what does undoing it cost — money, time, someone's trust? Trust is the one people forget, and the slowest to rebuild.
What would change my mind
Before deciding, write one sentence: I would choose differently if I learned that ___.
This does three jobs. It tells you what to research, so you stop reading everything and look for one specific thing. It tells you when to stop — once checked, further reading is procrastination. And it gives you a monitoring condition: if that thing later turns out true, you know to revisit.
If you cannot complete the sentence, one of two things is true. Either the decision does not depend on information — it is a values choice no research resolves. Or you have already decided and are gathering support, the confirmation pattern from your-own-biases.
Comparing options without pretending to be precise
A decision matrix is options down the side, criteria across the top. Its value is not arithmetic — it forces you to name criteria before looking at options, which stops you inventing one afterwards to justify the option you liked.
| Cost | Time to set up | Team can use it | Risk if it fails | |
|---|---|---|---|---|
| Option A | High | Fast | Yes | Low |
| Option B | Low | Slow | Needs training | Medium |
| Option C | Low | Fast | Yes | High |
Use words, not scores. Weighted numbers create false precision, and someone will argue whether cost is a 7 or an 8 when the real disagreement is about what you are trying to achieve.
Two rules keep it honest. Write the criteria before filling any cells. And add a row for doing nothing — a genuine option, and leaving it off is how organisations do something expensive for no reason.
Expected value, in plain language
You do not need the formula, only the habit behind it: think about the size of the outcome, not only its likelihood.
A 10% chance of something excellent can beat a 90% chance of something mildly good, if the upside is large and the failed attempt is cheap. That is why applying for a job you probably will not get is usually correct: the cost is an afternoon, the upside is a year of your life going differently.
It runs the other way too. A 2% chance of something catastrophic outweighs a 98% chance of a small gain when the catastrophe is unrecoverable. That is why "it will probably be fine" is a bad reason to skip a backup.
The practical version, in two questions:
- How bad is the worst realistic outcome, and can we recover?
- How good is the best one, and how likely must it be to be worth it?
If the answer to the first is "we cannot recover", probabilities stop mattering. Avoid it.
Decision: commit to a client that a feature ships in March.
Reversible? No. You cannot un-promise a date, only apologise later, which spends trust.
What would change my mind? "I would say March if the two people building it confirm the estimate and neither is on the other project in February."
Worst outcome: you miss by six weeks, the client escalates, and your manager hears it from them. Not cheaply recoverable.
The right move: do not answer today. "Let me confirm with the team and come back tomorrow" costs one day and is a complete answer. Fast responses feel competent; a wrong date is remembered far longer than a day's delay.
Decision: which of two health insurance policies to buy.
Reversible? Partly — you can switch later, but waiting periods for pre-existing conditions often restart, so switching has a real cost. Treat it as semi-irreversible.
Criteria written first: room-rent cap, exclusions, waiting period, claim settlement record, premium as you age. If you are in India, exclusions and the room-rent cap most often turn a cheap policy into a useless one at the moment you need it.
What would change my mind: "I would pick the more expensive one if it has no room-rent cap and the cheaper one does." That sentence turns an overwhelming comparison into one thing to look up.
Deciding in twenty minutes
1 of 5State the decision as a choice between named options. Not "what should we do about onboarding" but "do we do A, B, or nothing". If you cannot list options you are not ready to decide — go back to generating-options-worth-choosing.
Fast, wait, or escalate
Decide fast when it is reversible, when delay costs more than being wrong, or when you have checked the one thing that would change your mind. Most decisions are here.
Wait when specific information is arriving on a known date, when the decision gets cheaper later, or when you are angry or tired. The condition is that you can name what you are waiting for and when it arrives. "Waiting until I feel confident" is avoidance.
Escalate when the decision is irreversible and outside your authority; when it commits money, people, or the organisation's word; when it involves legal, safety, privacy or regulatory risk; or when you would be uncomfortable if your manager first heard it from someone else. That last test is the reliable one.
Escalate with a recommendation, not a question. "I think we should do B because of X; the alternative is A; I need your call because it commits us for two years" takes thirty seconds of their time. "What should we do about the vendor thing?" takes twenty minutes and hands the work back.
Try this
Classify each as reversible, semi-reversible or irreversible, and say how much effort each deserves:
- Which font the team uses in slide decks.
- Deleting a shared folder nobody has opened in a year.
- Trialling a new task tracker with your team for one month.
- Telling a candidate they have the job, before paperwork is signed.
Your challenge
Level 3 · IndependentTake a decision you are avoiding. Produce a one-page note:
- The decision, as a choice between named options including "do nothing".
- Reversible, semi-reversible or irreversible — and why.
- The worst realistic outcome, and whether you could recover.
- What would change your mind, in one sentence.
- Your decision, and the review date.
Success criterion: under 30 minutes, ending with a decision. If you finish still undecided, you have found a values question rather than an information one — name it as such and take it to whoever owns it.
What people usually get wrong
- Spending equal effort on every decision. The core error. Most deserve minutes.
- Treating "gather more information" as neutral. It is a choice with a cost, and the delay is often more expensive than being wrong.
- Deciding without recording why. In three months nobody, including you, remembers the reasoning, and it gets relitigated from zero.
- Escalating without a recommendation. It reads as unwillingness to think.
- Not escalating because you want to look capable. The uncomfortable conversation is cheaper than the surprise.
- Confusing a values disagreement with an information gap. More data never settles "is this worth it to us".
How someone experienced does it
Experienced people convert irreversible decisions into reversible ones before deciding. A one-month trial instead of an annual contract. A pilot with one team. An exit clause at six months. A staged rollout. This is the highest-leverage skill here: you rarely have to make the hard version of a decision if you can find a cheaper version of the same question.
They also make small decisions visibly fast. Deliberating publicly over trivia costs credibility and teaches everyone around you that all things require deliberation. Deciding in ten seconds and saying "reversible, let's try it" sets a norm that saves a team hundreds of hours.
And they separate the quality of a decision from its outcome. A good decision can turn out badly — you were right about the odds and the unlikely thing happened. Judge only by outcomes and you will learn the wrong lesson about as often as the right one. The written paragraph from step 4 is what lets you tell the difference later.
When not to use this
Do not use this when a procedure already exists. If your organisation has a process for procurement, data deletion or discount approval, follow it — this is for decisions nobody has defined, not for improvising around ones that are.
Do not use it on decisions that are not yours. Working out the answer to someone else's choice and presenting it as settled is a good way to be right and unwelcome at once.
Prove it
Write one decision note this week using the five-point structure and give it to whoever the decision affects.
Then set a calendar reminder for the review date. Keeping that date is what separates this from a document that made you feel organised for an afternoon.
Keep learning this
Paste this into any AI assistant. It turns the assistant into a tutor that tests you instead of just answering you.
Act as an experienced practitioner who is good at teaching. I have just learned pressure-testing a decision I have to make with incomplete information. Assume I am intelligent but relatively new to this — treat me as intermediate level. Work through this in order, and wait for my reply at each step: 1. Ask me 5 questions that test whether I actually understood pressure-testing a decision I have to make with incomplete information. Do not reveal the answers yet. 2. After I answer, tell me which parts I got right, which I got wrong, and which I only half-understand. Explain only what I misunderstood — do not re-teach what I already know. 3. Give me one practical challenge based on something I could genuinely encounter at work or in daily life. Do not solve it for me. 4. Evaluate my solution the way an experienced person would judge it, including what a professional would have done differently. 5. Tell me what to learn next, and why that comes next. 6. Give me trustworthy sources for deeper study — prefer official documentation, primary research or standards bodies over blogs and videos. Rules for you: no buzzwords. No motivational filler. Say "I'm not certain" when you are not certain, and tell me which parts of your answer I should verify myself. Clearly separate facts from your recommendations and your opinions.
Become independent at this
Use this when you want a path from where you are to actually good, with checkpoints you can test yourself against.
I want to become independently capable at deciding under uncertainty — not permanently dependent on AI, tutorials or step-by-step guides. Design a progression for me with five stages: Beginner, Guided practice, Independent practice, Real-world application, Professional level. For each stage tell me: - what I must know - what I must be able to do without help - the mistakes people make at this stage - one practical challenge - one real project that would prove I reached this stage - one way I can test myself honestly Then tell me the signals that I am ready to move to the next stage, and the signals that I have skipped ahead too early. Keep the theory to the minimum I actually need. Focus on ability I can transfer to situations you and I have not discussed.