A framework for leading teams through prolonged uncertainty
Four pillars, a fixed meeting rhythm and a written test for when to stop, for leaders whose disruption will not end on schedule.
Most crisis guidance assumes the disruption has an end date. Prolonged uncertainty does not. A flood recedes, a supplier recovers, a regulator issues new guidance, and the next question arrives before the last one is settled. Teams that hold up tend to stop treating each development as an emergency and start running a fixed rhythm of decisions instead. What follows is a four-pillar framework for setting that rhythm. It draws on Ready.gov's business preparedness guidance and on recent National Bureau of Economic Research work about when founders should stop. Where the evidence is thin, we mark the judgement as ours.
Chapter one: Set the rhythm before the pressure arrives
Start with the calendar, not the content. Choose three cadences and write them down: a short daily check on facts that have changed, a weekly decision meeting with a fixed agenda, and a monthly review of the assumptions behind the plan. The point is that people know when decisions get taken. Without that, every urgent message becomes a meeting, and the senior team spends its days answering whoever shouted loudest. A sensible test is whether each member of the team can name the date of the next decision on the agenda. If not, the rhythm does not exist yet.
According to its Ready Business page, Ready.gov offers firms a way to build a preparedness plan before a disruption arrives. The same logic applies to cadence. A rhythm improvised in the middle of a disruption tends to reflect whoever is most anxious that morning. Agree it while the company is calm, put it in diaries for the next quarter, and write down who may call an extra meeting and under what conditions.
Pair the rhythm with a short list of who decides what. In our experience, the frustration in long disruptions rarely comes from a lack of information. It comes from decisions that sit in a queue because nobody is sure whether they belong to the chief executive, the finance lead or the site manager. Write one line per recurring decision type, name the owner, and state the cost limit above which that owner must escalate. Review the list at each monthly meeting, and record every change.
Chapter two: Plan the communications before the news breaks
Ready.gov lists communications planning among the core parts of a business plan, alongside IT support and recovery and continuity plans. Give it its own owner and its own calendar. Leaders most often underestimate this part. The operations side has a plan, but nobody has settled who tells staff, customers and lenders what, or how often. Silence gets filled, usually with the least accurate version of events.
Write three standing messages in advance: what you know, what you do not know yet, and when the next update arrives. Use the same three headings every time. A team that hears from leadership every Thursday at four reads a delay as information. A team that hears news irregularly reads every gap as bad news. Keep the update even when the honest content is no change, and say so in those words.
Separate the audiences, not just the channels. Staff need to know what to do on Monday. Customers need to know whether their orders will arrive. Lenders and insurers need to know what has changed in the numbers they rely on. Each group should receive the same facts, cut to its own questions, from the same named person. Where a message to one group would surprise another, hold it until both are ready.
Chapter three: Keep operations, systems and suppliers running
Ready.gov's guidance covers communications planning, IT support and recovery, and continuity plans. It also says a business should plan for as much of an emergency's demands as it can. For a leadership team, the useful version is short. List the systems, suppliers, people and decisions the business cannot do without for a fortnight, and name who holds each one. Keep it to a single page. A longer list will not be read in a bad week.
Then test the list against the cadence. Each item should have an owner who attends the weekly decision meeting and a written fallback. Where the fallback depends on one person's laptop or one supplier's goodwill, record it as a risk, not a footnote. A common failure is a list that is complete on paper while its fallbacks have never been used. Ask for one fallback to be run in practice each quarter.
Single points of failure rarely reach the list, because they look ordinary. A payroll file sits on one administrator's account. A logistics contract was signed by one manager. A shared mailbox can be opened by one person. Ask each owner to name the person who could do their job for two weeks without calling them. If the answer is nobody, the risk belongs on the agenda.
Ready.gov publishes a Ready Business Toolkit series in hazard-specific versions. The list runs from earthquakes and hurricanes through inland flooding and power outages to severe wind or tornadoes. Each version gives a sequence of tasks for building preparedness into a firm's own operations. Use the one closest to your main exposure. In our view, the sequence of tasks transfers to other disruptions better than the hazard-specific detail does, so the same single-page list serves a supply shock as well as a storm.
Chapter four: Rehearse the plan and read the signals with care
A plan nobody has rehearsed is a document. Run a tabletop exercise each quarter, with the real decision-makers and a scenario that lasts longer than a week, so the rhythm is tested when people are tired and the answers are not obvious. In our experience, exercises show who knows what to do when operations are disrupted. The practical test is simple: a junior manager should be able to say, without checking, who decides.
Reading signals is the harder discipline, because the evidence in a long disruption often points two ways. NBER working paper 35551, Chinese Sputnik Moments?, sets out the case on both sides. One side argues that headline statistics overstate underlying progress. The NBER's own material also records a live dispute. Some observers say DeepSeek's 2025 low-cost, high-performing AI model shows China's rapid technological advance. Others say China's patent filings outnumber the US's three to one, overstating real innovative progress, and sceptics argue that incentive schemes produce many incremental patent filings. The two sides disagree. A leadership team should not pick the reading it prefers and call it the signal.
The same discipline applies to decisions about continuing. NBER's bulletin article on entrepreneurship training suggests such training can help founders learn when to stop. In our view, a decision to stop deserves its own owner and its own date, not a verdict reached in a bad week. Working paper 34755, Learning to Quit?, by Bailey, Fehder, Floyd, Hochberg and Lee, is built on a randomised, multi-year, multi-site experiment with innovation-driven entrepreneurs.
For a leadership team, the lesson is to write the stop conditions down before pressure arrives. Name the measures that would end a product line, close a site or pause a hiring round, and the level at which each applies. Review them at the monthly meeting. In our experience, judgement under strain tends to keep things going. A written threshold turns the stop into a decision rather than a defeat.
Seven questions for the next monthly review
Answer yes or no. Any no becomes a task for the next meeting, not a reason to wait.
- Can every member of the senior team name the date of the next decision meeting?
- Is there one named owner for staff, customer and lender communications?
- Do standing updates go out at a fixed time, even when nothing has changed?
- Does each critical system and supplier have a written fallback and an owner?
- Has the plan been rehearsed in the last quarter with the people who would make the decisio
- Are the conditions for stopping a project, site or product line written down?
- Do we check headline data against the detail before we act on it?
Outgrace checklist
Where it breaks
The framework fails in three predictable ways. The first is that the weekly meeting becomes a reporting session: status fills the agenda and no decision is taken. Move status into a written note circulated in advance, and give the meeting a short list of decisions. The second is that the communications plan reads like a press release. Staff notice the tone within a week and stop reading. The third is that exercises are run by the people who wrote the plan, and the findings are filed rather than acted on. The test is whether anything in the plan changed after the last exercise. In our view, readers outside the US should check the guidance of their local emergency authorities, since the Ready.gov material may not fit their rules.
Training, testing and exercises are essential components of preparedness.
Start on Monday with three things. Put the cadence into diaries for the next six weeks. Name one owner for each audience that must hear from you, and write the standing update in the three-heading form. Ask whoever runs operations for the single-page list of systems and fallbacks, due before the next decision meeting. Then hold the first exercise before the quarter ends, and treat what it reveals as the real output.
