War Room

Urgent problems arrive and the company still moves at its usual cadence. Requests join each team's queue and decisions wait for next week's meeting. Most of the time that process makes work fair and predictable; in front of something that needs an answer within days, the process itself becomes the delay.

In practice it looks like this. On the day a large customer gives notice, sales doesn't know exactly why, and the data that would confirm it has to be requested from another team. The request lands behind that team's list for the week, and if the cause turns out to be in the product, changing the engineering schedule is a decision for the weekly meeting. The actual work takes two days; getting to the start of those two days takes ten.

A war room is the temporary structure built to remove that waiting. The people needed are pulled off their other work and put in one place, and the authority to decide moves there with them. The phrase comes from the military practice of gathering the state of an operation into one room. The important property is that it isn't a standing arrangement but one that closes when the job is done, which is why the conditions for closing get set before it opens.

It runs in six steps from opening to closing.

1. Write the goal and the exit condition as one sentence. Something like "cut monthly churn from 5 percent to 3 percent within three weeks" — a number and a date together. Without both, nothing tells anyone when to stop.
2. Fix the people and the authority. One lead gets decision-making authority over this problem, with one person from each function involved. Anyone joining is explicitly released from their normal work. Leave them double-booked and they attend while nothing progresses.
3. Meet briefly at the same time every day. Fifteen to thirty minutes, covering only what was done yesterday, what happens today, and what's blocked. Anything needing discussion gets handled afterward by the people it concerns.
4. Keep one board. The target metric, what's in progress, and what's stuck all have to fit on that single page. Let it spread to several and maintaining the boards becomes the work.
5. Escalate immediately. Anything unresolved past a set interval goes through escalation — handing it to someone more senior — the same day.
6. Close it and write it up. When the exit condition is met or the deadline arrives, disband, then record what worked and what moves into normal operations as a postmortem.

Two to four weeks and five to seven people is the size that stays manageable. Larger than that and the daily meeting turns into a status round.

The people in the room fall into four roles: the lead carrying the problem, one practitioner from each function involved, a decision-maker who can approve what needs approving, and someone recording what was said and settled. The decision-maker doesn't need to sit there daily; twice a week to unblock stuck decisions is enough. A founder who attends every day turns everyone else's time into preparing updates.

There are three situations that open one. The first is a service outage or a serious slowdown. Incident management runs first there, and it becomes a war room after recovery when the cause spans several teams. The second is a number turning sharply. Churn doubling in a month or checkout conversion halving makes finding the cause a cross-team job on its own. The third is a large task with a deadline set from outside, such as a security review for a major contract or preparing for a listing.

It closes on the day the exit condition is met or on the date that was set. If the deadline arrives with the goal unmet, it doesn't get extended; the work moves into normal operations. Allow one extension and there is no argument left against the second.

Frequency is worth managing too. Once or twice a quarter is normal. Monthly means the problem isn't the war room but the ordinary planning around it, and catching warning signs in a regular business review reduces how often one is needed. Opening a war room pulls people off other work, so something else stops every time — which makes the decision to open one a resource allocation decision as much as anything.

"This goes to a war room. Push your other commitments back for three weeks."

Resources are being concentrated temporarily and the delay to other work is accepted.

"What's the exit condition? Without one it never closes."

Unless the goal and the date are written as numbers, it becomes a standing meeting.

"Nine-fifteen every morning, one screen up, ten minutes."

Meeting daily and meeting at length are different things.

Pagedeck opened two war rooms last year. One was the month three large accounts gave notice together. Sofia gathered what the three contacts had said on calls, Theo pulled the usage history on those accounts, and Mia looked for what they had in common, all three on it for three weeks. Grace came in Tuesdays and Fridays and handled only the blocked decisions.

What they found was that all three had doubled in headcount over the previous year and, without permission controls, their documents had become tangled in the process. The war room closed after three weeks and permissions went into the next quarter's product plan. The write-up also carried a rule for catching the signal earlier: flag customers whose user count is climbing quickly so customer success reaches out first.

The most common belief is that leaving a war room open longer is better. It moves fast, so working that way permanently sounds appealing. But the speed comes from stopping other work and concentrating people on one thing. Past a month the stopped work has piled up into a new problem and the people on it every day are worn out. Worse, the ordinary process dies. Once everyone knows urgent problems go to a war room, nobody raises anything in the regular meeting, and problems only surface after they have grown big enough to warrant one.

The other mistake is thinking the physical room is the point. The word room is right there, and photos of metrics taped to walls are common. What actually produces the speed is two things: not waiting, and deciding on the spot. A remote team meeting at the same time each day with real authority in the room gets the same effect. A team gathered in one room that still has to ask upstairs for decisions has only added a commute to its meeting.