How Reactive Leadership Turns One Bad Month Into a Bad Year
A client of mine had an incredible first quarter this year. Then came a less than desirable second quarter, with May landing as one of their worst months on recent record.
I want to talk about what almost always happens the week after a month like that, because the decision that gets made in that window could be one of the most expensive ones in business.
What a Bad Month Does to a Leadership Team
Here’s the pattern I’ve watched play out across nearly 30 years of operations work, and it’s remarkably consistent whether the company does $5 million, $500 million, or $5 billion.
The monthly numbers land and they’re ugly. Revenue down, profit down, and suddenly everything feels broken. The reaction is a total shift: we need to change our messaging, we need more outreach, we need to rework the strategy, and while we’re at it, let’s implement a new tool to track all of it. Drastic measures and everything at once.
I call it the panic pivot, and I want to be clear about what it actually is, because in the room it never feels like panic. It feels decisive. You’re reacting, you’re making decisions, you’re changing course. Leadership walks out of that meeting feeling like something got done.
But here’s what you’re actually showing your team: you’re fearful. You don’t have confidence that the direction you set is the direction. Your team can read that, whether anyone says it out loud or not.
The First Cost: You Erase Everything You Were Learning
The worst thing about changing everything at once isn’t the effort or the disruption, although both are real. It’s that you never get a baseline.
Think about what a strategy actually is: a set of activities you believe will produce an outcome, running long enough to prove or disprove the belief. That’s an experiment, and experiments only teach you something if you can connect the result back to the variables.
Now change the messaging, the outreach volume, the target list, and the tooling in the same two weeks. Whatever happens next, good or bad, you have no idea what caused it. You didn’t just lose the months you invested in the old approach. You lost the evidence it was generating. Every future decision starts from zero again.
That’s the part nobody prices in. A panic pivot is worse than doing nothing, because doing nothing at least lets the experiment finish. I’d rather a client stay on a mediocre course for one more quarter and learn something definitive than scrap it mid-stream and learn nothing.
Here’s the kicker: taking June to enact a bunch of changes does nothing to help you understand what created the bad May in the first place. Did the leading activities slip back in March? Did market dynamics shift? Was the goal wrong to begin with? Those questions have answers, but not if you bulldoze the site before anyone can inspect it.
The Second Cost: Your Team Stops Believing You
The baseline problem costs you information. The second cost is bigger, and it compounds quickly.
Let me tell you about a print manufacturer I worked with. Two partners, one of them from a brokerage background, running a full production operation the way a broker runs a book of business. Every job he touched became an emergency. He’d walk onto the floor and stop a press run mid-job to push through one order for one customer who, by the production team’s own account, could have waited. The schedule would take two days to recover, and it wasn’t a once-in-a-while thing. One of the veterans put it plainly: it’s every job he gets involved in.
After every blow-up came a new rule. One week it was a new proofing policy. Another week, a new way to write up tickets. Procedures changed constantly, and the team described it exactly the way you’d expect: today we’re going to do it this way, tomorrow we’re going to do it that way.
Here’s the thing about that operation: the processes weren’t a mystery. The team had documented everything, as one of them told me, nine times over. The knowledge existed. What didn’t exist was any reason to believe the current version of the plan would still be the plan next month.
So watch what the team does. Production meetings end with shrugged shoulders and back to business as usual. The veterans start saying the quiet part out loud: I’m not doing it, you do it if you want it done. And the person keeping the books, the one watching the money leak out one fire drill at a time, summed up the whole culture in one sentence: they’re really at the point where they just don’t care anymore.
That’s what eroded trust actually looks like. It isn’t conflict. It’s apathy. I describe it as the tornado: there’s a big blow-up, and then everybody who survives is left to pick up the pieces.
Every time you announce a new direction, you’re spending trust. If the change comes with transparency and a real reason, you can actually build trust by bringing people into it. But if it’s the flavor of the month, every announcement withdraws a little more, and eventually the team’s working conclusion becomes: leadership doesn’t know what they’re doing. After that, they stop investing effort in any initiative, because why would they? It’ll be replaced in six weeks anyway.
One more detail from that story, and it’s the one that should make every leader uncomfortable. A completely different client of mine knows that operation, and their leadership team now uses it as shorthand for their own waffling. In a planning session, one of the owners caught himself mid-sentence and said, sometimes I feel like we fall into the same trap: we know what we need to do. They had watched someone else’s fire-drill culture up close, laughed about it, and still found themselves reproducing it. This pattern doesn’t spare smart people. It recruits them.
Why Smart Leaders Keep Doing This
The panic pivot isn’t a character flaw. It’s a measurement problem.
Most leadership teams review their business through lagging indicators: revenue, margin, on-time delivery, the monthly P&L. Those numbers are real, but they’re history. They tell you what already happened, weeks or months after the work that caused it. I’ve written before about leading versus lagging indicators in manufacturing, and the same principle applies in the front office: reacting to a lagging indicator is reading the scoreboard after the game ended and trying to coach from there.
The bad May was almost certainly written in March and April, in activity levels and pipeline behavior nobody was watching closely. By the time it showed up in the financials, there was nothing left to react to. The panic pivot is what happens when a leadership team has no earlier signal to act on, so they act on the only thing they can see, at the only moment they can see it, which is the worst possible moment to make a calm decision.
What Holding Your Nerve Actually Looks Like
Back to my client with the terrible May. Same company, same month, and here’s what the rest of the dashboard said: new contacts added from existing customers had beaten its target every month since we started tracking it. Revenue per customer was up. The quote pipeline had grown. Year to date, they were single-digit percentage points below target, well within striking distance, and the revenue trend line was still climbing with one bad month sitting inside it.
I was looking at that trend chart on a call and told them: you scroll down, and I don’t see anything but a pattern. One bad month inside a rising trend isn’t a crisis. It’s a data point.
That’s what leading indicators buy you. Not comfort, but the ability to distinguish a results problem from a patience problem. If the activities are happening and the early numbers are moving, the outcome is coming and the right move is to hold. If the activities are happening and nothing upstream is moving, now you have a real conversation, and you can have it about one specific thing instead of everything at once.
You don’t need sophisticated infrastructure for this either. When I ran manufacturing operations, two weeks into the month I already knew roughly where we’d land, because the leading activity told me what was coming. A whiteboard with a daily number on it beats a beautiful monthly report that arrives too late to matter.
Signals: The Layer Most Leaders Never Look At
Underneath the leading indicators there’s one more layer, and it’s the one I lean on most in my own business: signals. Qualitative evidence, often not measurable at all, that tells you whether you’re directionally right before any number moves.
I’ll use myself as the example. There was a stretch building my business where I could have scrapped everything and shifted to a different model entirely, and the lagging numbers alone might have justified it. What kept me on course were the conversations. I was getting into more rooms with people who could actually engage me, and even though I wasn’t converting all of them, the quality and depth of those conversations kept improving. I was directionally appropriate, not completely dialed in. That’s a critical distinction, because those two situations call for completely different responses.
The signals also told me what to fix. What I was really fighting in those conversations was irrelevance, risk, and the status quo. So instead of changing everything, I changed one thing: I crafted an offer built around speed to value and risk mitigation, so people could crawl, walk, and run with me instead of having to make one big leap of faith. One variable, informed by a signal, tested against a baseline. That’s iteration. That’s the opposite of a panic pivot.
The same layer exists in your operation. On the operations side, it sounds like unprompted customer feedback about quality or turnaround time, the secondhand comment that tells you you’re providing value through the lens of the customer before it shows up in retention numbers. On the front end, it looks like relationships expanding inside existing accounts, or a churned customer taking a re-engagement conversation. As a side note, most companies chase new logos while their biggest growth opportunity is sitting in existing and previously churned customers, and the early signals of both are visible months before revenue moves.
So When Is Changing Course Actually Right?
None of this means you never change. Sometimes a bad month really is the front edge of something real, and waiting too long makes you the fool who should have pivoted earlier. Reality lives between the two extremes, and every leadership team is navigating it with incomplete information.
The rule I use, for myself and with clients: has materially new information come your way, information you didn’t have when you set the strategy? If yes, get it on the table and talk about it. But if you’re simply reacting to a miss, a gap between the goal and the actual, while the tactical activities you outlined are still in motion and initiatives are still open on the board, I’d caution you strongly against significant change, and in some cases against any change at all.
In my experience it follows the 80/20 rule. The majority of the time, the right move after a bad month is to take a breath and continue on the path, because the indicators underneath the bad number are still pointing the right way. This connects straight to how I think about continuous improvement: plan, execute, review, revise, repeat. The panic pivot skips review entirely. It jumps from a bad result straight back to a brand new plan, gutting the one step that would have told you what actually happened. Iterating on a plan is a feature. Replacing the plan every time it produces an uncomfortable number is how you guarantee no plan ever gets a fair test.
When you do change, only change one thing. Keep the baseline alive so the change can teach you something. If the situation is genuinely significant, that decision deserves a real planning effort before you execute, because what’s at risk isn’t just the quarter. It’s the trust you’ve built across the organization.
The Two Choices
I’ll leave you with the thing I come back to when the results aren’t showing up yet, in my business or anyone else’s.
Most people say they’re willing to do the work required to win. The reality is that most of us find reasons not to do it consistently, and a bad month is the most convincing reason ever invented.
But when you’ve done the planning, and the signals and leading indicators say you’re directionally right, there are only two choices: you either give up, or you wake up tomorrow and keep going. It doesn’t mean it’s easy. It means it’s reality, and the leaders who internalize that are the ones whose teams still believe them in month eleven.
What to Do Monday Morning
We just closed the first half of the year, which makes this the exact window where panic pivots get made. Before you change anything, do this:
1. Zoom out before you react. Put June and the first half against history. Are you looking at a broken trend, or one bad month inside an intact one?
2. Find your leading indicators. Pick two or three activities that reliably precede your results: quotes out, contacts added, meetings booked, backlog trend. If you have nothing, start with a whiteboard and a daily number.
3. Ask what actually caused the miss. Not what feels broken, what actually broke. Work the problem back to a root cause before you fund a single change. If the honest answer is “we don’t know,” that’s your project, not a pivot.
4. Write your change rule down now, while you’re calm. Ours is simple: materially new information gets a conversation; a miss alone gets a review, not a rewrite. Decide yours before the next bad month, because you won’t decide it well during one.
5. If you must change, change one thing. Keep the baseline. Let the change teach you something.
That’s it for today.
See you all again next week!
Dave
FAQs
What is reactive leadership?
Reactive leadership is running the business off what already happened instead of what’s happening now. It shows up as decisions made in the heat of a bad monthly report: sweeping changes, new initiatives, new tools, all triggered by a lagging indicator. The tell is timing. If most of your significant changes get decided in the 48 hours after bad news lands, you’re reacting to history, and the team feels it as whiplash. The fix isn’t to stop changing things, it’s to build the leading indicators and signals that let you act earlier, on better information, with a calmer hand.
How do I know whether to change strategy or stay the course after bad results?
Ask one question first: do I have materially new information that I didn’t have when I set this strategy? If yes, bring it to the table and evaluate honestly. If no, and you’re simply reacting to a gap between goal and actual while your planned activities are still in motion, the odds heavily favor staying the course. Check the layers underneath the bad number: are leading indicators still moving in the right direction? Are qualitative signals, like the depth of customer conversations or unprompted positive feedback, still improving? If the underlying layers are healthy, you have a patience problem, not a results problem.
What's the difference between signals, leading indicators, and lagging indicators?
Lagging indicators are the scoreboard: revenue, margin, on-time delivery. They’re accurate but late, reflecting work done weeks or months ago. Leading indicators are the measurable activities that precede those results: quotes sent, contacts added, meetings booked, backlog trend. Signals sit underneath both, and they’re qualitative: the changing depth of sales conversations, a customer mentioning your turnaround time unprompted, relationships expanding inside an existing account. Signals tell you you’re directionally right before the leading indicators confirm it, and long before the lagging numbers prove it.
Why do frequent strategy changes hurt team morale and trust?
Because every announced change spends organizational trust, and constant changes spend it faster than results can rebuild it. When direction changes every time a number disappoints, teams learn that investing effort in any initiative is wasted, since it’ll be replaced soon anyway. The end state isn’t conflict, it’s apathy: meetings that end in shrugged shoulders, documented processes nobody follows, and your best people quietly concluding that leadership doesn’t know where it’s going. Rebuilding from that point costs far more than any single bad month ever did.
How long should I give a strategy before judging the results?
Longer than one month, almost always. Beyond that, honest answer: it depends on the length of your operating cycle. If your sales cycle runs six months, judging a new business development motion at 30 days is measuring noise. Sometimes the right window is a quarter, sometimes a half, sometimes a full year for a significant strategic move. The practical approach is to stop asking “how long until I can judge the outcome” and instead define the leading indicators and signals you expect to move first, then judge those on a shorter clock. You’ll know you’re directionally right long before the finish line.
Ready to see what's holding your operation back?
Take the Operations Diagnostic: your top 3 priorities, plus a quick win for each. I personally review every one and send your insights within 24 hours.
Already know you need a hand? Let's Talk → 20-Minute Strategy Call