The Seven Laws of Enterprise Readiness
Inside a fixed play clock, the huddle is one way a team sets shared context and assignments before the next snap. That bounded example makes preparation visible, but it is not a model for the full range of enterprise uncertainty. The laws in this chapter describe principles an organization can prepare before pressure arrives.
These laws did not come from theory. I watched the same patterns hold across very different operating environments, and I saw what happened when leaders assumed those patterns did not apply to them. Over time the evidence became too consistent to treat as isolated observations. Call them principles if you prefer; the label matters less than what happens when an organization ignores them.
Deming had his fourteen points, Drucker his principles of management, and the Agile Manifesto its four values and twelve principles. The seven laws serve a similar organizing purpose. They are practitioner-derived propositions about patterns I observed in organizations preparing for Strategic Situations, not universal rules that predict the behavior of every organization. I call them laws because, across more than two decades of enterprise leadership, the patterns seemed consistent enough to design around and test.
They are not established causal findings, and you should judge their effects in context. Charles Duhigg's work on organizational routines offers one explanation for why repeated patterns persist: good intentions alone do not always change established behavior.
Law One: Organizations respond to their understanding of reality, not reality itself. Two organizations can face similar conditions and respond differently because their leaders read the situation differently. The failure mode is fragmented sensemaking. Functions receive information but do not compare interpretations, so leaders act on an incomplete or inconsistent picture. Shared understanding is one place to prepare.
Law Two: Strategic Situations are an important object of leadership. Projects, portfolios, and finance remain essential, and leaders can also ask which situations create the demand for that work. One failure mode is letting delivery measures take up so much of the agenda that the executive team reviews activity more often than the conditions that may require its priorities or its response to change. Delivery deserves governance; the question is whether that governance also gives leaders a view of the Strategic Situations behind the work.
Law Three: Readiness is an enterprise capability, not solely an individual competency. Individual judgment and expertise remain essential, but organizations can prepare roles, relationships, and responses so the work does not depend only on heroic effort. The failure mode is authority, relationships, and institutional knowledge concentrated in particular people. Then a departure or absence reveals that the organization had not made them transferable. Prepared Responses and succession arrangements are meant to make more of the work visible and available to others, not to remove the need for expertise.
Law Four: Decision Quality affects organizational velocity. Speed is no advantage if the decision points the wrong way. In cases I observed, organizations moved quickly toward outcomes they later had to correct. One failure mode is treating rapid action as proof of readiness while shared understanding, decision rights, or relevant evidence are still unsettled. Preparation can help leaders examine information and clarify authority before committing, but it cannot guarantee a sound decision. The test is both how quickly leaders make a decision and how it holds up against events.
Law Five: Alignment can constrain Capability. The three dimensions are not independent, and limited alignment can keep an organization from using otherwise strong capabilities. The failure mode is investing in skills, tools, or response capacity while functions still cannot coordinate around a shared decision. Sometimes more investment in alignment is worth more than additional capability, but leaders have to assess that in context. Alignment does not substitute for expertise or authority. It is one condition that lets capabilities work together.
Law Six: Learning should become organizational memory. In organizations I observed, some retrospectives did not change future practice. The failure mode is a review that records events but leaves Prepared Responses, governance, sensing, and decision rights unchanged. A later team then has to reconstruct the same lessons. Institutional Memory is meant to embed relevant learning in those practices instead of relying only on what individuals remember. After-action review, and lessons carried into future practice, offer related examples in other fields. The Mobilization Tax on a comparable situation can fall if the learning is captured, maintained, and applied. A record or retrospective alone does not ensure that result.
Law Seven: Enterprise Readiness is not finished once implemented. Competitors, technology, customer expectations, and regulation change, and preparation has to change with them. The failure mode is treating readiness as a completed project and letting protocols, contact paths, or delegated authority go stale while the environment moves on. An organization can maintain capability through review and practice, but it should not assume that one investment will keep it suitable indefinitely.
Together, the seven laws give you a working framework and a common language for examining readiness. Treat their failure modes as questions to investigate, not conclusions to impose. The useful question is which laws matter most in your organization, and how you would test that.