The Research Foundation
If you want the argument, it is in Parts I through IV. This chapter is the evidence it rests on: the theorists and studies each part drew from, documented for readers who want to examine the foundation directly.
Across the preceding chapters I have made an argument. In practice, organizations must coordinate responses to Strategic Situations, and the Preparation Layer is where I observed stronger performers do important, often less visible work. I have put a modeled cost on the absence of that work, the Mobilization Tax, and described an architecture intended to reduce it. I have offered these claims as an argument, grounded in the management tradition and in what I observed across organizations ranging from startups to Fortune 100 companies. A reader who has come this far is entitled to ask a harder question than whether the logic is coherent. The harder question is whether it is true, and it matters that the answer does not depend on me. Enterprise Readiness emerged from practice, not a laboratory.
The intellectual sequence should be explicit: observation gives rise to a model; the model generates hypotheses; those hypotheses can be measured; and future work must test whether the results hold across organizations, practitioners, and situations. My observations and case illustrations end where transferable proof begins. They can identify a pattern and motivate questions, but they cannot by themselves establish that Enterprise Readiness caused an outcome, that the framework works in every setting, or that another practitioner can reproduce it. That boundary is not a weakness to conceal. It is the ordinary work by which a practitioner-derived management discipline becomes capable of empirical testing. The next stage is independent measurement, including evidence about mobilization time, response quality, implementation effort, and what was proven or disproven after an activation.
The cost is the full mobilization gap: authority that has to be clarified, stakeholders who have to align, communications that have to be prepared, action lists that have to be built, and legal questions that have to be answered before coordinated work begins. In the cases described here, many of these elements were assembled under pressure; a prepared response seeks to stage relevant elements in advance. The effort and delay together contribute to the Mobilization Tax. If the response takes long enough, some of the opportunity window may have passed before coordinated execution begins.
But the reason this framework may be useful is not that I discovered something no one else had seen. Research in decision-making, organizational learning, high-reliability operations, military planning, and neuroscience offers several relevant mechanisms: people recognize patterns, teams coordinate through shared intent, prior practice can shape responses, and pressure can affect judgment. These fields ask different questions and do not converge on a single conclusion about Enterprise Readiness. Their concepts help explain why preparation may matter and suggest hypotheses this discipline can test. The evidence discussed in this chapter is offered as context for the Preparation Layer, not as validation of the model or proof of its effects across organizations.
How experts actually decide, and why it looks nothing like the textbook
Begin with the individual mind, because organizational decisions are made by people working together. Gary Klein's field research on consequential decisions, including fireground command, found that experienced decision-makers often recognize patterns, generate a plausible course of action, and mentally test it rather than compare every possible alternative. Klein called this recognition-primed decision-making. Recognition can support fast action when the situation resembles patterns for which the decision-maker has experience; it does not guarantee that the first interpretation is correct. His work therefore offers a useful lens for preparation, not a complete foundation for Enterprise Readiness. A taxonomy of Strategic Situations may help an organization recognize a developing situation as related to a known class, and a Prepared Response may offer a starting point. Neither should prevent leaders from examining what is new or different in the specific case. Recognition can save time; deliberate shared understanding can help test whether the analogy fits.
Klein's reported studies of fireground commanders are useful because they examined consequential work in its operating context. Commanders faced incomplete information and limited time. Rather than generate and score a long list of options, experienced responders often recognized a pattern, considered a plausible action, and mentally simulated how it might unfold. If the course seemed workable, they could act; if the mental simulation exposed a problem, they revised it. This account differs from a simple claim that experts act by instinct. Experience supplies patterns, while situation-specific assessment remains important. Klein's findings describe expert decision-making in studied settings; they do not establish that an enterprise taxonomy will generate equivalent expertise or that a Prepared Response will fit a novel situation. They suggest a question for practice: can leaders use a familiar pattern as a starting hypothesis, then compare it with the present facts before acting?
Recognition can be fast, but it can also mislead when a situation resembles a familiar pattern without sharing its important features. Its value depends in part on experience and feedback; shared understanding can help test a recognized pattern before leaders commit to it. Cognitive-load research offers another relevant mechanism. John Sweller's work describes limits on working memory, the capacity used to hold and manipulate information in the moment. A situation may require leaders to interpret events, identify authority, assess resources, sequence stakeholders, and begin acting under time pressure. Preparation may move some recurring decisions and coordination steps out of that pressured moment, but it cannot eliminate the need to reason about the facts that are new. That is one way to understand the Mobilization Tax as an attentional as well as an economic cost. Organizations also operate as complex adaptive systems: many interacting agents produce outcomes that cannot always be predicted from the parts in isolation. Complexity research does not mean that leaders cannot plan or learn; it cautions against assuming that a plan can specify every development. This is why the proposed taxonomy organizes preparation around plausible classes of situations while preserving the ability to adapt to events as they unfold.
The connection to preparation is not that a plan removes complexity. A Prepared Response can record recurring roles, information requirements, decision paths, and communications so that leaders need not reconstruct each element while also interpreting an unfamiliar event. That may leave more attention for the features that could not be known in advance. The amount of working memory available varies with the person, task, expertise, and setting; it would be too strong to infer that every unprepared response overwhelms every leader. Sweller's research instead offers a mechanism worth testing: when avoidable coordination work adds demands during a difficult task, reducing that load may help people attend to the novel elements that remain. The distinction also identifies a limit. If a response is too detailed, outdated, or poorly matched to the event, consulting it can add rather than remove work.
Forecasts can be useful, but they cannot specify every event in a complex environment, and reliance on a single forecast can leave an organization less able to adapt when conditions change. Complexity research points to a more modest distinction: a particular event may not be predictable, while classes of situations may be recognizable and recurring. An organization cannot know with certainty when a competitor will stumble, a regulation will shift, or a supply disruption will occur. It can identify those as plausible situation types in its environment and prepare options accordingly.
Complexity theory helps explain why the discipline proposed here emphasizes readiness to adapt rather than a detailed script for a single future. In systems with many interacting participants, local actions can affect other parts of the system, and outcomes may emerge in ways that are hard to infer from the components alone. This does not make forecasts useless or preparation impossible. It suggests that leaders should state assumptions, notice when conditions depart from them, and preserve authority to adjust. A taxonomy of situation classes can help organize attention, but it is a map for discussion rather than a prediction engine. Whether the chosen classes are useful, comprehensive enough for a particular organization, or kept current must be examined in practice.
The Strategic Situation Taxonomy is not intended to predict particular events. It organizes preparation around classes of situations that leaders consider plausible, while leaving room to adapt when the facts differ from expectations. It complements the six-capability architecture described in Chapter 7: sensing, shared understanding, authority, communication, response, and institutional memory. Readiness is an emergent capability of relationships among people and processes, not a component that can be installed on its own. High-reliability research offers a relevant, though not identical, source of insight. Karl Weick and Kathleen Sutcliffe studied organizations such as aircraft carriers, nuclear power plants, air traffic control centers, and wildland firefighting crews, where failures can have serious consequences. In Managing the Unexpected, they describe a posture often called mindfulness, expressed through habits such as attention to small failures, reluctance to simplify, sensitivity to operations, commitment to resilience, and deference to expertise. These habits overlap with conditions Enterprise Readiness seeks to support. The research does not validate this book's six-capability model, but it offers useful examples of how preparation and coordination are treated in some high-reliability settings.
These practices offer a conceptual crosswalk, not a one-to-one correspondence. Attention to small failures is relevant to sensing because weak signals may matter before a formal threshold is crossed. Reluctance to simplify can encourage leaders to compare interpretations rather than settle too quickly on one label. Sensitivity to operations draws attention to what is happening in the work itself; commitment to resilience recognizes that systems need capacity to respond when conditions depart from plan; deference to expertise concerns whose knowledge should inform a decision. These observations may help practitioners ask better questions about their own preparation. Aircraft carriers, power plants, and emergency services differ from ordinary enterprises in mission, regulation, training, and consequence, so transfer requires its own evidence.
The high-reliability practices described by Weick and Sutcliffe overlap with aspects of shared understanding and authority architecture, but they are not identical to this book's constructs. Military planning offers another useful comparison. The often-cited distinction between plans and planning is not that a document has no value; it is that assumptions may change and people need the understanding and authority to adapt when they do. Mission command, for example, emphasizes shared intent and action within delegated authority. These practices inform the preparation argument without making Enterprise Readiness a military doctrine. Emergency management offers a distinct example: the Incident Command System establishes common roles and communication for response, including situations in which participating agencies may not have worked together before. That is relevant to coordination, but not a complete model for routine enterprise situations.
Behavioral economics also cautions that judgment can be affected by uncertainty, incomplete information, and cognitive bias. Daniel Kahneman and Amos Tversky documented biases such as loss aversion, anchoring, availability, framing, and confirmation. Their findings do not mean that every leader under pressure makes the same mistakes or that every bias intensifies in every situation. They do point to a practical design question: can an organization create conditions for competing interpretations to surface before a consequential judgment hardens? Preparation may help by providing roles, information, and time for discussion, while leaving the decision with accountable leaders. The claim is a mechanism to test, not a guarantee that advance preparation will produce sound judgment.
These concepts describe tendencies and experimental findings, not a prediction of how a particular executive team will behave. Loss aversion may affect how people weigh a possible loss against a possible gain. An initial estimate can serve as an anchor, a vivid recent event can weigh heavily in recall, and framing can make equivalent information feel different. Confirmation bias may direct attention toward evidence that fits an existing interpretation. In an enterprise response, these tendencies could interact with the division of information across functions: one function may frame an event as a technology issue, another as a regulatory exposure, and a third as a client-retention problem. Deliberate discussion can put those frames in contact, but it does not guarantee that the group will recognize a bias or choose well. The practical question is whether leaders can make assumptions visible, seek disconfirming information, and record why they chose a course of action so a later review can examine the reasoning.
Preparation may support debiasing when it creates time to surface divergent interpretations through the meaning check described earlier. Bringing multiple framings into contact could help leaders notice anchoring or confirmation bias before one interpretation hardens into an organizational position, though it cannot eliminate those biases. A Prepared Response records decisions and assumptions considered before pressure; leaders still need to review whether they fit the facts when a situation arrives.
Interpretation can be easier to do before pressure arrives, when there is time to examine evidence and competing frames. Behavioral economics describes errors in judgment; neuroscience offers part of the mechanism. Research on the neurobiology of stress, including Amy Arnsten's work at Yale, has found that acute, uncontrollable stress can impair prefrontal functions associated with working memory, reasoning, planning, and impulse regulation. Under stress, catecholamines and cortisol can affect the balance between deliberative and more reflexive processing. This is not evidence that every leader under pressure will make a poor decision, nor that a Prepared Response removes the effects of stress. It is a reason to avoid adding preventable assembly work to a situation that already places demands on attention. A Prepared Response may move some recurring decisions into advance preparation, leaving leaders more capacity to interpret the specific facts they could not have known in advance.
The mechanism is conditional, not a simple rule that pressure makes judgment fail. The research concerns specific forms and intensities of stress, and findings do not establish that every business challenge produces an equivalent physiological response. It does, however, support a narrower design question: when people face high demands, can organizations avoid adding coordination tasks that might have been settled earlier? Preparation cannot remove the stressor, protect leaders from every effect, or predetermine a sound choice. A useful response should preserve a deliberate pause for checking current evidence, challenging a familiar analogy, and adjusting the protocol when circumstances require it.
Some research suggests that perceived control and familiarity can moderate stress effects, though neither eliminates uncertainty. Training can help responders recognize aspects of a situation without assuming that a novel event is identical to a rehearsed one. The football example has a limited parallel: within a defined play clock, players had prepared for recurring classes of situations. A Prepared Response can offer an organization a comparable aid to recognition and coordination, but it cannot convert an unfamiliar crisis into a fully rehearsed event. Decision science supplies another relevant lens. Herbert Simon described bounded rationality: people make judgments with limited time, information, and cognitive capacity rather than assessing every alternative. They often choose an option they consider sufficient given the frames available to them. This helps explain why different functions can interpret the same information differently and why shared understanding may matter; it does not by itself establish the effectiveness of the Enterprise Readiness framework.
The mechanisms do not collapse into a single explanation. Klein's work concerns how experienced people recognize and mentally test courses of action. Sweller's research concerns demands on working memory. Kahneman and Tversky describe patterns in judgment under uncertainty; stress research examines physiological conditions that can affect deliberative functions. Complexity research cautions against assuming that the organization can forecast each development or control the system's full response. These accounts address different levels and questions. Their relevance to enterprise preparation is that they suggest several possible pressures on collective response, not that they prove one management intervention will solve them.
One way to connect these ideas is through the concept of Enterprise Cognition. I use that term for a proposed organizational capacity to combine signals, expertise, shared interpretation, decision authority, and institutional learning so people can consider a situation together. It does not mean that an organization literally has a single mind, that group judgment is always better than individual judgment, or that technology can remove bias and uncertainty. It describes an arrangement of people and practices that may help an enterprise reason across functional boundaries while preserving accountable human decisions. The six capabilities in Chapter 7 provide one proposed architecture for examining such an arrangement. Whether they are sufficient, whether they interact as described, and whether they improve decisions are empirical questions.
The concept also clarifies why preparation is not equivalent to writing a script. Sensing can place relevant observations before people with appropriate expertise. Shared understanding can expose differences in interpretation. An Authority Map can make the decision owner and escalation path visible. Communication and response arrangements can support coordinated action, while Institutional Memory can carry approved learning forward. At each step, leaders must test the information and retain room to adapt. A protocol may help structure inquiry, but the situation may require rejecting or revising its assumptions. The architecture is useful only to the extent it helps people notice the difference between a known pattern and a consequential novelty.
This synthesis produces testable questions rather than a conclusion supplied by the cited disciplines. Does pre-staging recurring decisions reduce time spent on avoidable coordination without reducing attention to new information? Do shared-meaning checks reveal material differences in interpretation before those differences affect execution? Does an explicit succession path preserve decision continuity when a primary authority is unavailable? Do after-action reviews result in maintained changes that improve a comparable later response? Measurement should also consider possible costs, including false alarms, stale protocols, suppressed dissent, extra administrative burden, or premature commitment to a familiar pattern. A serious validation effort should report both benefits and failures, specify which situations were studied, and distinguish observed associations from causal claims.
The expected contribution of Enterprise Cognition is therefore not a borrowed guarantee from neuroscience or decision research. It is a proposition that structured cooperation may complement bounded individual judgment. The participating experts still hold different information and responsibilities; the architecture creates a way to bring some of those contributions into the same decision process. Better integration is not automatic and may not improve every decision. A later activation record could help researchers and practitioners examine where signals came from, how interpretations differed, which authority was used, what actions followed, and what changed after review. Such records could support empirical inquiry, provided they are complete enough, interpreted carefully, and compared across suitable cases.
These literatures offer complementary lenses rather than a single root cause for every issue discussed here. Recognition-primed decision-making, cognitive load, biases, stress research, and complex-systems theory each address different aspects of judgment and coordination. No one body of research establishes that enterprise readiness must take a particular form, and the interaction among these mechanisms remains an empirical question. The framework proposed here asks whether combining preparation, shared understanding, authority, response, and learning can help an organization act more coherently under pressure. That proposition should be assessed through measurement, not inferred from the fact that separate fields have each studied related challenges.
The bodies of research discussed in this chapter were developed in different fields to answer different questions. Their concepts are not a single consensus statement, and they do not establish that preparation determines outcomes in every complex situation. Taken together, however, they offer relevant support for hypotheses about preparation, shared understanding, authority established before pressure, learning, and coordinated action. My own observations, first in a defined football setting and later in enterprise work, motivated the framework; they do not prove that it transfers or causes improved results. Nor do the cited studies validate Enterprise Readiness as a finished discipline, the six-capability model, or the Mobilization Tax estimates. They help explain why the model is plausible and worth testing. The sequence remains observation, model, hypotheses, measurement, and future validation. Organizations that adopt the architecture should collect evidence about mobilization time, response quality, implementation effort, and what changes after an activation, so the framework's claims can be evaluated rather than assumed.