The Reactive Manager's Wake-Up Call

I used to manage by urgency. Not on purpose. Not because I thought it was a good system. It just happened, gradually, until it was the only system I had.

My day looked like this: I'd open Slack, see what was on fire, respond to the loudest thing, move to the next. Tyler had a problem with a client deliverable, I'd drop in. A deadline snuck up on the Harrison project, I'd scramble to find out where things stood. A team member caught me in the hallway looking frazzled: I'd spend the next 90 minutes in an impromptu session I hadn't planned for and had nothing to follow up with.

I thought I was being a good manager. I was available. I cared. I was always in the mix. Looking back, I was doing something that looked like managing but wasn't: I was being managed by circumstances instead of managing them.

The moment I understood this clearly was a Thursday afternoon, about 18 months into leading a team of five. I was in the middle of helping one person fix a report that had gone out wrong. I had two unread messages from two other people, both needing something I hadn't anticipated. My calendar showed a team meeting the next morning that I hadn't prepared anything for. And when I stopped to think about it, really think about it, I had no idea which of my five direct reports was blocked on something that actually mattered. I knew only what had hit me most recently.

I was five people's manager. I had no idea what was going on with four of them.

Not because I didn't care. Because I had no system that required me to look.

That was the moment I understood that responsiveness and rhythm are not the same thing, and that I'd been confusing them for over a year.

Reactive managers aren't bad managers. They're unstructured ones.

The easy story about reactive management is that it's a motivation problem. Lazy managers, checked-out managers, managers who don't care. That's almost never what I've seen.

Most reactive managers care too much. They're responsive because they want to help. Liz Wiseman writes about this in Multipliers: she describes the "accidental diminisher," the well-intentioned manager whose constant involvement actually shrinks the team's capacity rather than growing it. The manager who jumps in because they care, who answers before the team can think, who solves before the team can struggle. That was me. I thought being available was the same as being effective.

They drop structure when things get busy because the structure feels optional and the fire feels urgent. And then the structure that was supposed to prevent fires is the first thing to go when fires break out, which is exactly backwards.

The real problem is structural, not motivational. Without a consistent rhythm, a set of recurring touchpoints that happen whether the week is calm or chaotic, you don't have a system. You have a series of reactions. And in a series of reactions, the loudest thing always wins. The team member who surfaces problems urgently gets more attention than the one who quietly absorbs pressure. The deadline you can see from close up gets more focus than the one two weeks out that you haven't thought about.

Your team feels this, even if they can't name it. They learn that the way to get your attention is to have a crisis. They stop surfacing small problems early because there's no standing channel to surface them in. And the small problems become the fires you spend all your time putting out.

What a real rhythm looks like

When I finally built a rhythm, I was surprised by how simple it was. Not easy, it takes discipline to protect. But simple.

The core of it was three recurring structures. Weekly 1:1s with each direct report: same time, same rough agenda, every week. A short Monday team check-in, fifteen minutes maximum, just to surface what's moving and what's stuck. And a Friday lookback, which I did alone: a ten-minute scan of what the team accomplished, what's open, and what needs my attention in the week ahead.

That's it. Three structures. Maybe four hours of calendar time per week when you add it all up.

What they bought me was something I didn't know I was missing: visibility before things became urgent. In the 1:1s, I found out that Priya had been grinding on the same data export problem since Monday. I found out on Wednesday. Not on Friday, when it became a missed deadline. In the Monday check-in, I saw blockers forming before they calcified. In the Friday review, I caught things that needed my attention the following week instead of discovering them Thursday afternoon when it was too late.

Andy Grove wrote in High Output Management that a manager's output is the output of their team, not their individual work. I had been measuring my own days by how busy I felt. The rhythm forced me to start measuring by what my team was actually producing.

"A management rhythm doesn't eliminate fires. It means you see them forming before they're out of control."

The 1:1 structure mattered most. I ran them with a simple agenda: what's top of mind for you, what's in the way, what do you need from me this week. Fifteen minutes of their agenda, ten minutes of mine, five minutes of something forward-looking. I took notes after every one. I looked at the notes before the next one. That habit, actually reviewing what was said the week before, changed the conversations more than anything else.

Why rhythm works (it's not just efficiency)

You could frame management rhythm as a productivity thing. More structure, less wasted time, fewer surprises. That's real. But there's something more important going on underneath it.

Daniel Coyle writes in The Culture Code about "belonging cues," the small signals that tell people they're safe and seen. Consistency is one of the most powerful belonging cues a manager can send. When your team has a predictable rhythm, they know the 1:1 is happening Tuesday at 2, they know the Monday check-in covers blockers, they know you'll circle back on open items from last week. They start treating those containers differently. They save things for them. They think between sessions about what they want to bring up. They stop interrupting you with every question because they know there's a standing channel for the non-urgent ones.

A former manager I had once told me something that took me years to fully understand. "Unpredictability is a form of instability," she said. "Your team can't do their best work if they're always managing the uncertainty of when they'll see you." She was right. The teams I've seen that perform best almost always have a manager who shows up the same way, week after week.

This is the psychological function of rhythm that nobody talks about: it tells your team that the future is predictable. That there will be a place and time to raise the thing they're worried about. That they don't have to manufacture urgency to get your attention.

The reactive manager's team learns the opposite lesson: urgency is the currency. You want face time? Create a crisis.

"Consistency signals safety. When your team knows the rhythm will hold, they stop hoarding problems and start surfacing them early."

Try this week: Look at your calendar and find the first standing 1:1 that's been skipped or shortened in the last three weeks. Restore it. Then before that meeting, review whatever notes you have from the last time you met. Show up with one specific thing you remember from the last conversation. See what shifts.

When the rhythm breaks

Rhythms break. They break when a big project hits, when someone's out sick, when there's a sprint that demands everything. I've broken mine more than once.

I'm not sure there's a perfect way to prevent this. The weeks when rhythm is hardest to hold are almost always the weeks when it matters most. I know that, and I still let it slip. That's honest. What I've figured out is that the mistake isn't breaking the rhythm. It's not knowing how to restart it.

You don't have to rebuild from scratch. Find the one element you can restart immediately and start there. Usually that's the 1:1. Get one back on the calendar. Show up prepared for it. The act of doing one thing right resets the pattern better than any retrospective about what went wrong.

Common mistake: Treating the rhythm as optional during busy weeks. This is exactly wrong. The weeks when the rhythm is hardest to keep are the weeks when your team needs it most. A canceled 1:1 during a high-pressure sprint doesn't just mean a missed conversation, it tells everyone that structure is decorative, that the container disappears when things get hard. The seasons when I skipped 1:1s the most were always the seasons I had the least visibility into what my team actually needed. I thought I was saving time. I was spending it later, on problems that would have been smaller if I'd caught them earlier.

Try this week: Every Monday morning for the next three weeks, spend ten minutes writing down the name of each direct report and one sentence about what you know is going on for them right now. If you can't write that sentence, it means the rhythm has slipped somewhere. Use the gap as a diagnostic.

Start with one thing

If you're not running a consistent rhythm right now, don't try to build the whole system at once. Pick one structure and hold it for four weeks without skipping. One 1:1. One Monday touchpoint. One Friday ten-minute review. Just one.

Four weeks is long enough to feel the difference. You'll notice things you weren't noticing before: blockers that used to surprise you on Thursday, visible a week earlier in a Wednesday 1:1. A team member who seemed fine, whose answers to "what's in the way" started to follow a pattern you'd have missed without the structure.

That's the rhythm working. Then you build from there.

I built Cadence partly because I kept losing the rhythm I'd built. Not because I didn't want it, but because it lived across four different tools, and the friction of pulling it together before each meeting was the first thing to go when the week got hard. I wanted the prep to be low enough that I'd actually do it on a difficult week, not just a calm one. That's the bar a management tool has to clear: not "is it useful when I have time?" but "will I open it when I'm already overwhelmed?"

Ready to stop firefighting and start managing?

Cadence gives you 1:1s, team meeting agendas, task tracking, and a single place to track what matters. Built for managers of 3–8. 14-day free trial.