Erratic Leadership Burns Cycle Time

The Pattern That Looks Like Engagement

There is a type of leader who is always on. Always reacting. Always sending the Slack message that starts with "hey, something seems off, can everyone stop what they're doing."

From the outside, this looks like someone who cares deeply about the business. High energy. Paying attention. Constantly plugged in. And if you described the behavior to someone who had never experienced it, they might say it sounds like the kind of leader they'd want.

Inside the team, it's a different story. The team has learned that roughly every three days, the sky falls. They've also learned that if they wait it out, the sky usually un-falls, and the new priority gets replaced by an even newer one before anyone actually shipped anything on the last one. So they've gotten good at looking busy during the emergency without fully committing, because committing means abandoning something real.

That's the dysfunction. And it almost never shows up on a dashboard.

The Cycle-Time Math

Let me be specific about what actually happens when an erratic leader fires off a false emergency.

Say you have a team of five people, and someone drops a "DROP EVERYTHING" message at 10 a.m. on a Tuesday. Each person has to stop what they're doing, re-orient, get into a context they weren't in, assess whether this is actually a fire, and either join the chaos or quietly stay the course while managing upward pressure to look like they're joining the chaos.

Conservative estimate: 30 to 45 minutes per person to fully switch context. That's not the meeting time. That's the ramp-up before the meeting, the meeting itself, and the ramp-back afterward before anyone is actually productive again on what they were doing.

Five people at 40 minutes each is over three hours of team capacity. Gone. Not slow. Not degraded. Gone.

Now run that twice a week. For a year.

That's over 300 person-hours of lost output. For a team of five. And I'm not counting the downstream cost, which is where it really adds up. The ticket that didn't get finished. The project that slipped a week because two key contributors got pulled. The customer who didn't get their answer on time. Those don't show up as "leadership cost" anywhere. They show up as team performance problems. The wrong person takes the accountability for the miss.

The Signal Degradation Problem

Here is the other thing that happens, and it's sneakier than the cycle-time math.

When everything is urgent, nothing is. I've seen this play out in organizations I've been part of, and it follows a predictable arc. In month one, people respond to the urgent signal. They take it seriously. They shift. In month three, they've started triaging on their own, deciding quietly whether this one is real or whether it's going to blow over like the last six did. By month six, the word "urgent" in the subject line has lost all meaning. It's noise.

The sky can only fall so many times before your team stops looking up.

And here's the real problem with that: eventually, something will actually be on fire. A real emergency. Something that genuinely needs everyone's immediate attention. And you will have spent your credibility. The team will apply the same filter they've been using for months, and the real fire will get treated like another false alarm.

Erratic leadership doesn't just waste time in the present. It erodes your ability to mobilize when it actually matters.

Why Erratic Leaders Think They're Doing the Right Thing

I want to be honest about something here, because it's too easy to write off erratic leaders as just bad leaders.

Most of them are not malicious. Most of them are anxious. They feel responsible, they care about the outcome, and they have learned over time that signaling urgency gets attention. Maybe it worked once, in a crisis, when they pulled the alarm and the team rallied and they saved something real. And that was a legitimate success. The problem is the pattern that follows, where that tool gets used for everything because it worked once.

There is also an ego component that is worth naming. Some leaders genuinely like being at the center of the storm. The emergency keeps them relevant. It puts them in the room. It creates the feeling of leadership: high stakes, fast movement, decisions being made. That feels different from the quieter, less dramatic version of leadership, which is setting clear direction, removing obstacles, and then getting out of the way.

The quieter version produces more output. It just doesn't feel as exciting.

What the Calm Leader Absorbs

I've watched strong middle managers do something genuinely hard, and they rarely get credit for it.

They sit between an erratic senior leader and a team that needs to do work. And they spend a significant portion of their energy absorbing the chaos before it hits the team. They translate "DROP EVERYTHING" into "hey, let's take a look at this when you get a chance, it may be nothing." They filter. They buffer. They hold the perimeter.

This is a real skill and it protects real output. But it has a cost. The manager doing this is carrying anxiety that doesn't belong to them. They're doing double work: their actual job, and the translating and dampening of noise from above. Over time, that weight accumulates. Some of the best managers I've ever known have burned out not from their team load, but from the sustained effort of shielding their teams from leadership above them.

If you're a leader and someone on your team is doing this, you should know what it's costing them.

How to Ratchet Down Without Dropping Standards

If any of this sounds familiar because you recognize yourself in it, here's where I'd start.

Before you hit send on the next "something seems off" message, ask yourself one question: is this a problem to share, or a problem to investigate? Those are not the same action. Sharing a problem mid-panic creates chaos. Investigating it first takes you twenty minutes and often resolves the question entirely. If it doesn't resolve it, you now have actual information to share instead of a vague signal wrapped in urgency.

Second, build a norm with your team for how real escalations actually work. Not every issue needs the whole team. Not every observation needs a same-day response. If you have a consistent, reliable escalation path, your team knows when you use it that it's real. That restores the signal you've been degrading every time you cry wolf.

Third, and this is harder: pay attention to how your team responds when you send an urgent message. If they look tired instead of activated, if they go quiet instead of engaged, if they're doing a version of "here we go again" without saying it out loud, that's feedback. Take it seriously.

The Actual Job

Urgency is a tool. Like any tool, its usefulness depends entirely on how often and how accurately you use it.

The leaders I've seen build high-output teams over long periods of time are not the ones who are always in motion. They're the ones who know when to move fast and when to stay out of the way. They generate trust because their signals are reliable. When they say something matters, it matters, and everyone knows it.

That kind of credibility takes time to build. It takes almost no time to destroy.

Your team is not a fire brigade. Stop treating every Tuesday like it's the big one.