Sources of Power How People Make Decisions

A firefighter walking into a burning building does not calculate. She recognizes. Some feature of the fire, the way smoke curls under a doorframe, the sound of the structure above her, matches a case she has lived through before, and that match tells her what is likely to happen next. The past case is not stored as a rule. It is stored as a whole situation, with its texture intact, and it functions as a template she lays over the present.

This is why an analogue does more than remind. It structures. When an experienced decision-maker finds a parallel between an old case and a new one, the old case carries its consequences with it: what worked, what went wrong, what the situation became a few minutes later. That transfer lets someone predict where a problem is heading and generate options without working through every alternative from scratch. The story does the reasoning that deliberate analysis would otherwise have to do slowly.

The power depends entirely on the quality of the match, and this is where experience earns its keep. A novice sees surface features and reaches for a case that resembles the present in the wrong ways. An expert reads the deeper structure, the causal skeleton, and finds the analogue that actually applies. Experience builds the library of cases; it also builds the judgment about which case fits.

What the analogue finally produces is a sharper reading of the situation itself. By mapping the current problem onto a remembered one, a person sees which cues matter and what they mean. The story is not decoration laid over understanding. It is the scaffolding on which understanding gets built.

How to

1. When a situation feels familiar, name the specific prior case it reminds you of and state out loud why it fits.
2. Test the match by listing where the current case diverges from the analogue, not just where it aligns.
3. Deliberately collect a second, dissimilar analogue to break the grip of the first one that came to mind.
4. Build a library of instructive cases—including near-misses and failures—so your retrieval set isn't limited to personal experience.

Watch out for

• Surface similarity (same industry, same words) hijacks retrieval while the structurally relevant case goes unnoticed.
• The most vivid or recent story dominates recall regardless of whether it actually parallels the current problem.

A well-functioning team moves as if it can read its own mind. One member reaches for a tool before another asks; a piece of information arrives at the moment it is needed, unrequested; a plan changes and everyone adjusts without a meeting. This is not telepathy. It is the accumulated product of people who share a picture of the situation, a common sense of what they are trying to achieve, and enough knowledge of each other to anticipate what comes next.

Three things sit underneath the team mind. The first is shared situation awareness, meaning the members are looking at the same reality and weighting the same cues. The second is a common understanding of intent, so that when the plan meets friction, individuals can improvise in the same direction rather than scatter. The third is the ability to predict a teammate's actions and information needs, which lets coordination happen quietly, ahead of demand, instead of through constant negotiation.

When these hold, the team decides better than any individual in it. Coordination stops consuming attention and adaptation becomes cheap, because members are already braced for the same possibilities. When they fail, the failure is usually invisible until it isn't: two people acting on different pictures, each certain the other sees what they see. The team mind is fragile precisely because it is implicit, and it is worth protecting for the same reason it is easy to lose.

How to

1. Make commander's intent explicit so members can improvise toward the same goal when plans break.
2. Build a shared mental model through joint briefs, rehearsals, and after-action reviews rather than assuming it forms on its own.
3. Assign and communicate who holds which knowledge so members know where to route information and requests.
4. Practice implicit coordination—delivering information before it's requested—to test whether the team mind is actually working.

Watch out for

• Silence gets misread as shared understanding when it actually signals divergence nobody has surfaced.
• Adding communication tools can degrade shared cognition if they replace the tacit anticipation experienced teams rely on.

The measure of a decision is not how close it comes to the theoretical optimum. It is whether it works, and whether it arrives in time to matter. A commander who reaches a good-enough course of action in thirty seconds outperforms one who reaches the best possible action after the moment for acting has passed. In situations with real stakes and moving conditions, timeliness is not a compromise on quality. It is part of quality.

This reframes what a skilled decision-maker is doing. Rather than comparing options against each other to find the winner, the effective decision-maker recognizes a workable response and checks it against the situation, ready to move. The goal is a course of action that fits the case in front of them well enough to succeed, not one that would survive an academic defense afterward.

Effectiveness has several roots. Situation awareness feeds it, because a decision built on a clear reading of the situation is more likely to hold. Mental simulation feeds it, because playing an option forward reveals whether it will actually work. A team's shared understanding feeds it, because coordinated action executes the decision the choice implies. And the difficulty of the conditions bends all of this: time pressure, ambiguity, and high stakes shape how much deliberation is even possible, and what counts as good enough shifts with them. A decision that would be reckless in a calm office can be exactly right in a fire.

How to

1. Judge a course of action by whether it will work in this context, not by whether it beats every alternative.
2. Set an explicit time budget for deciding and treat a satisfactory answer within it as success.
3. Evaluate your leading option by mentally running it forward rather than generating a menu to rank.
4. Reserve full comparison for the rare cases where time is abundant and stakes justify it.

Watch out for

• Chasing the optimal decision burns the time that made any decision effective in the first place.
• Judging effectiveness by outcome alone ignores that a sound process can produce a bad result under uncertainty.

Some problems do not come with a menu. They are ill-defined, novel, or shaped so oddly that no stored response fits, and the person facing them cannot simply reach for the typical move. What matters then is the ability to build a solution rather than select one, to improvise a course of action that answers the specific demands of a situation no one anticipated.

The skilled improviser is not throwing ideas at the wall. They are looking for leverage points, the places where a small, well-aimed action changes the shape of the whole problem. Finding those points depends on seeing the situation clearly enough to know where its joints are, which is why a sharp reading of the situation drives adaptive problem solving. You cannot spot leverage in a picture you have misread.

Mental simulation is the other engine. Building a new course of action means imagining it forward, watching it collide with obstacles in the mind's eye, and revising before committing. The improvised solution is tested internally, adjusted, tested again. What looks like inspiration in the moment is usually rapid, disciplined rehearsal.

Adaptive problem solving is therefore less a talent than a byproduct of understanding a situation deeply and running it forward honestly. The person who can do both does not need the problem to match anything they have seen before. They can construct the answer the situation actually requires.

How to

1. Diagnose whether the problem is truly novel or merely unfamiliar before deciding to improvise versus retrieve.
2. Identify leverage points—places where small action produces disproportionate effect—rather than attacking the problem head-on.
3. Construct a solution from components you understand deeply, and mentally simulate it before committing.
4. Stay ready to abandon and rebuild the approach as the situation reveals more of its structure.

Watch out for

• Forcing a familiar procedure onto a novel problem because improvising feels riskier than following a rule.
• Improvising from shallow situation awareness produces creative solutions to a misunderstood problem.

Experience is not the accumulation of years. A person can spend two decades in a field and remain a novice at the moments that matter, because what builds expertise is not time on the clock but the quality of what happens inside that time: the variety of situations met, the feedback that arrives close enough to the action to correct it, and the practice that pushes into cases the person has not seen before.

The distinction shows up in what a person notices. An experienced decision-maker walks into a situation and sees structure where a beginner sees a wash of undifferentiated detail. That perception is earned. It comes from having stood in enough versions of a situation that the recurring shape has become familiar, and from having been wrong often enough, with the correction close enough to the mistake, that the lesson stuck.

Relevance matters as much as depth. Skill accumulated in one narrow set of conditions does not transfer freely to a different set, which is why a person can be genuinely expert in one corner of a domain and clumsy in a neighboring corner. The practiced knowledge is specific.

This store of knowledge is what everything else draws on. The rapid reading of a situation, the ability to run a scenario forward in the mind, the instinct to reach for a case that resembles the present one — none of these work without a reservoir of relevant experience feeding them. Where the reservoir is thin, the faster ways of deciding have nothing to work with, and the person is left to reason it out slowly from first principles.

How to

1. Inventory the actual variety of cases someone has faced, not their years — count distinct situation types, not calendar time.
2. Trace whether they got timely, unambiguous feedback on past decisions; where feedback was delayed or absent, treat that experience as weak.
3. Deliberately expose developing decision-makers to rare, high-consequence cases via simulation so their pattern library covers the tail, not just the routine.

Watch out for

• Domains with slow or noisy outcome feedback (long-horizon strategy, low-frequency emergencies) let people accumulate confidence without accumulating skill.
• Expertise is domain-bound — a seasoned expert in one setting reasons like a novice the moment the situation type shifts.

The conditions that define real decision-making are the same ones that make the textbook methods useless. Time is short. The stakes are high enough that being wrong carries real cost. The information is incomplete, sometimes contradictory, and rarely arrives in the order a person would want it. The goals themselves are often ill-defined, shifting as the situation moves. And frequently the work has to be coordinated with other people whose actions the decision-maker only partly controls.

Each of these features alone would strain a formal, analytical approach. Together they close it off. A method that requires listing every option, scoring each against fixed criteria, and selecting the optimum assumes stable goals, ample time, and adequate information. Strip those away and the method has nothing to stand on. There is no time to generate the options, no stable target to score them against, no complete picture to score them from.

The conditions do not merely make good decisions harder. They change what a good decision looks like and which mental processes can produce one. A setting that is dynamic and time-pressured rewards the ability to read a situation quickly and act on the first workable course, and it punishes the deliberate weighing of alternatives that would serve well in a calm, information-rich setting. The environment sets the terms; the decision method has to match them or fail.

How to

1. Diagnose the condition set before choosing a method: if goals are ill-defined, stakes high, and time short, abandon formal option-comparison protocols.
2. Under these conditions, generate one plausible course of action and stress-test it by imagining how it plays out, rather than assembling a list to rank.
3. Design training and drills to reproduce the actual pressure — clock, noise, missing data — so the skill built matches the condition it must survive.

Watch out for

• Retrofitting a tidy analytical rationale after the fact convinces you the method worked, obscuring that recognition, not analysis, drove the call.
• Not every setting is naturalistic — imposing intuitive shortcuts on genuinely deliberative, information-rich decisions throws away real analytical advantage.

When an experienced person sizes up a situation in a few seconds, what looks like a flash of insight is recognition. The features of the present moment match a pattern the person has met before, and with that match comes a package of understanding: what is going on, what kind of situation this is, and what usually works. The judgment feels instant because the recognition is instant. The work that made it possible happened earlier, over many prior encounters.

The process is non-analytical. The decision-maker is not comparing options against a checklist. The pattern arrives whole, carrying with it a sense of what is typical here and, just as important, a sense of what does not fit. Anomaly detection is the other side of recognition — the trained eye catches the one cue that violates the expected pattern, the detail that says this situation is not what it appears to be. That catch is often the difference between a routine call and a save.

Recognition also delivers a plausible course of action, not a menu of them. The pattern that identifies the situation typically comes with the response that usually suits it, ready to be checked rather than invented from scratch.

This depends entirely on the store of experience behind it. A rich, relevant store yields fast and accurate recognition; a thin one yields either no match or a false one. And the recognition feeds directly into the person's grasp of the whole situation — it is the mechanism that turns raw cues into an understanding of what is happening.

How to

1. Treat your first read of a situation as data: name the specific cues that triggered it before overriding it with analysis.
2. Deliberately expand your pattern library by studying diverse cases and outcomes, including your near-misses and failures.
3. Run a quick mental simulation of the course of action your intuition proposes to check whether it would actually play out.
4. Distinguish domains where your intuition is trained from ones where it is not, and demand analysis in the untrained ones.

Watch out for

• Trusting intuition in a domain where you lack real repetition and feedback — confidence there is often pattern-matching on the wrong features.
• Forcing intuitive judgments into a lengthy justification, which can make you discard a correct read because you cannot yet articulate it.

Situation awareness is the working picture in the decision-maker's head: not just what is happening now, but what it means, what to watch, and what is likely to come next. It is the product of pattern recognition assembled into a coherent understanding of the whole.

The picture has parts that are easy to miss when it works smoothly. It includes a sense of which goals are plausible in this situation — not abstract objectives but the ones that actually fit the moment. It includes the critical cues worth monitoring, the small number of things that will tell the person whether the situation is developing as expected or drifting toward trouble. It includes expectancies, a set of predictions about what should happen next, so that a violated expectation registers as a signal rather than passing unnoticed. And it includes the typical responses that go with the situation, the actions that usually fit.

Expectancies do quiet, essential work. When the situation matches them, the person proceeds with confidence and attention to spare. When it violates them, the mismatch draws attention exactly where it is needed and prompts a fresh read. This is how a person stays oriented in a moving situation instead of being surprised by it.

A good situation picture is what makes good decisions and flexible responses possible. When the picture is accurate and complete, the right action tends to follow and the person can adapt as conditions shift. When the picture is wrong or partial, even sound reasoning downstream produces the wrong result, because it is reasoning about a situation that does not exist.

How to

1. Identify the three or four cues that actually distinguish this situation type from adjacent ones, and monitor those instead of scanning everything.
2. State your expectancies explicitly—what you predict will happen next—so you can detect the moment reality diverges from your model.
3. When a cue violates your expectation, treat it as a signal to re-diagnose the whole situation rather than patching your existing read.

Watch out for

• Fixation: holding onto an initial interpretation and reinterpreting contradictory cues to fit it, rather than updating the frame.
• Confusing surface familiarity with true recognition—a situation that resembles a past one can carry a different underlying structure.

Mental simulation is the act of running a scenario forward in the mind to see how it will unfold. A person takes a course of action, imagines the steps it would set in motion, and watches — in imagination — for where it might break. The same process runs backward to diagnose a problem: given this outcome, what sequence of events could have produced it. In both directions the decision-maker is building and playing a small internal model.

This is how an experienced person checks an option before committing to it. Recognition may hand up a plausible course of action; simulation is what tests it. The person plays the action through, and if the imagined sequence hits a wall — a step that will not work, a consequence that cannot be accepted — the option is rejected or repaired before anything real is at stake. The evaluation happens without trying the option in the world, which is precisely its value when the stakes are high and there is no room for a failed trial.

The quality of the simulation rests on experience. Playing out a scenario accurately requires knowing how events in this domain actually connect, which steps follow which, where the hidden dependencies lie. Without that knowledge the imagined sequence is a fiction that feels plausible and leads nowhere useful.

The payoff shows up in two places. Simulation makes decisions more effective by catching flaws that a first impression misses, and it makes a person more adaptive by generating expectancies and revealing the moves a situation allows before it has fully arrived.

How to

1. Run the scenario as a concrete sequence of events, forcing each step to lead to the next, and stop at any transition you can't explain.
2. Limit yourself to a small number of moving parts—simulations collapse in accuracy past roughly three interacting variables or six transitions.
3. Deliberately conduct a pre-mortem: assume the action failed, then work backward to construct the story of how it did.

Watch out for

• Overloading the simulation with too many variables, which produces false confidence rather than insight.
• Explaining away the point where the story breaks instead of treating that break as the discovery you were looking for.