I Had a Team and Still Became the Bottleneck

I delegated the technical work during an incident, then kept every update, phone call, and written report for myself.

Several hours into a long incident, I had an analyst waiting for me to approve the next step, a leader waiting for me to return a call, and a half-written situation report open on my screen. Messages kept arriving faster than I could answer them. I was doing a little bit of everything, which is a generous way to describe finishing almost nothing.

The strange part was that I had a team. They were capable, available, and already doing most of the technical work. I had delegated the investigation because I understood that four people could review evidence faster than one. Then I treated every communication task as though it required my fingerprints.

I briefed leadership, drafted the written updates, and answered routine questions from people following the incident. Between those tasks, I kept the timeline, checked the shared notes, and tried to notice when a new finding changed what we had already said. Each responsibility made sense on its own. Together, they turned me into a help desk with approval authority.

At the time, keeping communication close felt responsible. The wording mattered. A loose statement about scope could travel upward and become a fact before the team had confirmed it. I knew which details leadership cared about and which working theories were still too soft to brief. Handing any part of that to someone else felt like creating another place for the message to go wrong.

Instead, I created one place for everything to wait.

The analysts needed decisions from me, but I was on the phone. The written report needed current findings, but I had not caught up with the technical channel. Leadership needed an answer, but I was trying to recover the context I had lost while drafting the written report. I had become the most carefully managed single point of failure in the room.

The fix was less dramatic than the problem. I assigned someone to handle the communication work that did not require my specific judgment. They drafted the routine updates, maintained the timeline, tracked what we had promised to deliver, and watched the technical channel for findings that changed the picture. I still reviewed what went upward and handled the conversations where a decision, recommendation, or uncomfortable answer needed to come from me.

That distinction helped. Delegating communication did not mean telling someone else to “keep everybody informed,” then hoping for the best. The role had a clear boundary. They collected and organized the information. I owned the judgment about what it meant and what we should do next.

It also gave the team one version of the incident to work from. Before that, the current picture was scattered across my notes, a chat thread, and whatever I remembered from the last phone call. Once someone was maintaining the timeline and briefing log, an analyst could see what leadership had already been told without interrupting me. The next update started from the last one instead of being rebuilt from memory.

This does not need to become an elaborate command structure for every suspicious email. A short investigation with one affected person can survive without a communications deputy, a shared document, and a small constitutional convention. The need appears when the incident outgrows the number of conversations one person can hold in their head.

That point usually arrives before it feels convenient to bring someone in. Early in an incident, doing it yourself may still be faster. You know the facts, the audience, and the history. Then another stakeholder appears, the incident stretches into a second shift, or the scope changes while you are briefing the old scope. By the time the workload proves that help is necessary, communication debt has already started collecting interest.

I used to think being the incident lead meant I should be the only person speaking for the response. What leadership actually needed was a consistent picture, delivered by a team that knew which parts required the lead and which parts required someone with a clear head and an open document.

My team had been there the entire time. They could not help with a job I had never admitted existed.

I cover communication roles, shared incident narratives, and upward briefings in Talking To Your Boss.