The First 100 Days

The first hundred days of building Readiness capability can shape both momentum and resistance. Sequence matters, though it is not everything. Kotter's work on organizational change stresses establishing urgency, building a coalition, and showing short-term wins. That is a useful frame for early decisions. In Enterprise Readiness, the first change can be in the conversation rather than the structure.

Instead of opening with "What is the status of our initiatives?" leaders can ask, "What Strategic Situations are we currently managing, and how prepared are we for each?" At first, the conversation will probably drift back to familiar project status. Follow up by asking which portfolio items respond to a cross-functional situation, which situations lack a current project, and what is developing that could demand a response. In meetings I led, those questions sometimes moved the discussion from reporting to the situation. Kotter's later work describes the value of a network that operates alongside the hierarchy. New conversations and behaviors can start inside existing structures before anyone decides whether to reorganize.

The first thirty days can focus on vocabulary. Simon's work on bounded rationality suggests that people judge within the frames and information available to them. A shared vocabulary may help leaders discuss Strategic Situations, Readiness Gaps, the Preparation Layer, and the Mobilization Tax more precisely. Introduce the terms in real conversations rather than assuming a formal initiative is needed. When someone describes a situation, a leader might ask: "Is this a Strategic Situation that our current governance does not have a Readiness Protocol for?" The language becomes concrete once it touches real work.

The next thirty days can focus on diagnosis before recommendations. Map the significant Strategic Situations the organization is managing. Assess preparation across the nine domains, and look for where a Readiness Gap is widest. In the organizations I led through this exercise, leaders often found gaps larger than they expected; the result may differ elsewhere. A situation stress test can help make preparation visible. For two or three situations leaders consider significant, ask what the first days would look like: who would convene, what authority is delegated, what communications are needed, and how governance would work. The gaps give a forward-looking view of possible assembly costs, not a precise Mobilization Tax calculation.

In the third thirty days, begin developing Readiness Protocols for selected situations. They need not be comprehensive. Start with who convenes, who has authority, what the first forty-eight hours require, and the order of communication.

In one organization, we chose a ransomware event because leaders saw an unstaged response as a liability. I convened five roles: the Chief Information Security Officer, the head of Legal, the Chief Operating Officer, the head of Communications, and the controller. Then I asked: if ransomware hit the primary operational system at six tomorrow morning, who makes the first call, and who do they call?

The CISO believed the first call was his and that he would call the COO. The COO believed the incident-response policy named Legal as the first notification because of regulatory implications. Legal believed the CEO had to be notified first. Communications believed it belonged on the first call, because the external-statement clock started when an executive was notified. Four people gave four different answers, each reflecting a legitimate concern: immediate operations, regulatory notification, CEO awareness, or external communications. Nobody had agreed how those decisions fit together.

We spent three meetings on the order of the first four phone calls, not on the technical response or the communications plan. The protocol clarified ownership. The CISO kept operational authority for the technical response, and Legal owned the regulatory notification sequence. Business-continuity decisions belonged to the COO. Communications had standing authorization to start drafting external statements once the COO was notified, without waiting for approval of the draft. The controller was included in the financial and resource discussions.

Six months after the protocol was finalized, a tabletop exercise showed that the CISO and the head of Legal still described the same event and notification sequence differently. Both believed they were following the protocol. The document existed; the shared understanding had not fully formed. That taught me that a document alone is not preparation; the people involved have to work through scenarios together. This is one organization's experience, not evidence that the same protocol or sequence will fit another.

An initial protocol can give the organization something tangible, surface gaps in authority or resources, and create a basis for institutional learning. Still, it does not guarantee value or make each later situation cheaper. In the example I observed, participants judged that a proposed protocol could have helped in three of the five significant situations the organization had recently handled. That was a retrospective practitioner assessment, not a measured impact study. Likewise, a Prepared Response for competitive displacement may cut assembly time from weeks to days, when the situation is comparable and the response is current. That is a hypothesis to test, not a promised return.

The first hundred days need not involve a reorganization, a new committee, a platform, or a method. Kotter's work offers reasons to establish urgency, coalitions, and visible early progress. Heath and Heath discuss shaping behavior and environments. In my experience, organizations that redesigned governance without changing the conversations inside it sometimes saw little change in behavior. Whether structural change is needed, and when, depends on what the diagnosis reveals. Look for evidence that the new questions, vocabulary, and early protocols are useful before building structures to sustain them. The period need not produce a complete transformation. A baseline, a pilot, and a basis for deciding what comes next can be enough.

The test is whether the first hundred days create the conditions for further work: urgency, shared vocabulary, evidence of early value, and leaders willing to continue. Start with a conversation in a meeting you lead, then decide what the evidence suggests should follow.

The operating prerequisites are deliberately concrete. Name an executive sponsor and a day-to-day steward. Select a few Strategic Situations already consuming leadership attention. Map the current authority chain and set safe integration targets. Record the baseline time and leadership effort to reach coordinated action. Review the evidence at thirty, sixty, and ninety days. The first hundred days should not be judged by how much software was configured. Judge them by whether the organization can show clearer authority, faster mobilization, stronger coordination, and a response that improves when tested again.

Days 91 through 100 can close the initial pilot with a bounded tabletop exercise for one of the first Readiness Protocols. Use a plausible, unrehearsed variation of the situation. Record the time from recognizing the situation to convening the people with authority to respond. Note where the communication sequence or handoffs remain unclear. The sponsor and steward can then compare those observations with the baseline. Together they decide what to continue, revise, or stop, and record why for the next cycle. A tabletop can reveal gaps and preserve what was learned, but it cannot establish how an actual situation would unfold.