The Leadership Skill of Absorbing a Bad Number Before You Act
Third-quarter results are in, and some of them aren't what anyone hoped to see. Fiscal calendars differ by company and by market, so your own quarter may have closed months ago or may still be open. The moment is the same either way. A number arrives that is worse than the plan, and everyone in the room watches what you do with it.
Two reactions come up often enough to name. One leader treats the number as an emergency and starts issuing orders. Another treats it as noise and moves to the next agenda item. Both feel decisive. Neither has done the work yet.
This isn't a results review. The number could be revenue, margin, customer retention, safety performance, or a project milestone. What matters here is the decision-making skill underneath it. Can you take in disappointing information, keep your judgment intact, and choose your next move on purpose?
A Bad Number Tests Judgment Before It Tests Strategy
Your first response is your first decision. I'd argue it's the one with the widest reach, because it sets the terms for every decision that follows.
A disappointing number invites an instant story. Either it's a crisis that demands action today, or it's a blip that will correct itself. Both stories arrive before the evidence does. Each one feels like leadership because it ends the discomfort of not knowing.
Absorbing a bad number means holding two facts at once. The number is real, and you don't yet know why it happened. Most leaders can hold one of those. Holding both takes practice.
Why a Quick Verdict Is So Tempting
Uncertainty is uncomfortable, and a verdict relieves it. Losses also weigh heavily. Daniel Kahneman and Amos Tversky modeled choice in Prospect Theory: An Analysis of Decision under Risk as valuing gains and losses rather than final wealth, with losses generally weighing more than comparable gains. That helps explain why a miss can feel larger than an equal beat would have.
A disappointing number can also feel like a verdict on you. It often sits next to a forecast, a plan, or a decision you made earlier, so reading it honestly can feel like grading your own competence. The instinct then runs in one of two directions. You fix something fast so the plan looks intact, or you explain the gap away so the plan looks sound.
Pressure from outside adds to it. Boards, lenders, customers, and your own people all want to know what the number means, and they want to know now. Speed earns approval in the short run, which is why the quick verdict survives even when it's wrong. The way out isn't to suppress the instinct. It's to build a pause between the number and the verdict, and to fill that pause with specific work.
Panic and Minimizing Fail the Same Way
Barry Staw, Lance Sandelands, and Jane Dutton drew on evidence across individuals, groups, and organizations in Threat-Rigidity Effects in Organizational Behavior: A Multilevel Analysis, published in Administrative Science Quarterly. They argued that threat narrows the information people take in, tightens control, and pushes people back toward familiar responses. That pattern describes panic well. The room gets quieter and the questions get fewer.
Karl Weick and Kathleen Sutcliffe describe both failures in Managing the Unexpected. Organizations rush to decide before they understand a situation, act on first impressions, and seek evidence that confirms their response, so weak cues of trouble get discounted. Their remedy includes looking for disconfirming evidence and refusing to normalize an unexpected event just to preserve a prior expectation. That second habit is minimizing at work. The room learns the number doesn't deserve a hard look, so nobody asks what it means.
The theory describes a tendency, not a certainty. Leaders can resist it. But you can't resist a pattern you haven't named.
Your Reaction Sets How the Room Reads the Number
Thomas Sy, Stéphane Côté, and Richard Saavedra compared leaders in a positive mood with leaders in a negative mood in The Contagious Leader: Impact of the Leader's Mood on the Mood of Group Members, Group Affective Tone, and Group Processes, published in the Journal of Applied Psychology. Group members took on the leader's mood, the groups developed a matching emotional tone, and groups with leaders in a positive mood coordinated better. Groups with leaders in a negative mood exerted more effort, and the authors cautioned against relying on negative mood to raise it.
The limits matter. The study used 189 undergraduates on a short blindfolded tent-building task, with leader mood induced by film clips. It tested mood, not bad news, and it can't tell you how any one team will respond. Still, the mechanism deserves your attention. Your team reads you at the same moment it reads the number. The authors also suggest that leaders benefit from learning to regulate their mood displays.
Composure doesn't mean concealment or cheerfulness. Forced optimism is another form of minimizing, and people see through it quickly. Composure means stating the figure plainly, in the same words you'd use for a good one, saying how significant you judge it to be without inflating or shrinking it, and showing that you're still thinking. If leaders meet unwelcome numbers with defensiveness or quick reassurance, people will likely start softening what they report. That's my judgment, not a finding from these studies.
Judge the Decision Apart From the Outcome
A disappointing result doesn't automatically mean a past decision was flawed, and a good result doesn't prove one was sound. Jonathan Baron and John Hershey tested this in Outcome Bias in Decision Evaluation. Across five experiments, participants rated decisions made under uncertainty as better thought out, and the decision makers as more competent, when outcomes were favorable, even though they said outcomes shouldn't count.
So test the decision, not just the result. Did the market conditions or customer behavior your plan assumed change, or did execution miss the plan? Did the effort get enough capital, capacity, and leadership attention? Was the original decision made through a sound process, or built on unverified optimism? Those questions keep the review on judgment and off blame.
This gets harder when the miss challenges a decision you championed. In 1976, Barry Staw gave 240 business students a role-play investment case in Knee-Deep in the Big Muddy: A Study of Escalating Commitment to a Chosen Course of Action. Participants who had personally chosen an investment that then declined allocated more money to it than participants in any other condition. Staw read the result as consistent with a need to justify earlier decisions, while noting competing explanations. Later replication attempts, listed by FORRT in its FLoRA Replication Atlas, returned mixed or failed results, so treat it as a tendency to watch for, not a law. One question helps. If I hadn't made the original decision, would I still recommend continuing it today? It can't remove bias, but it exposes the pull of ownership.
Separate the Signal From the Story
Start by naming the number once, without adjectives. Then sort what you know from what you're inferring. You know the figure and, perhaps, the size of the gap. You're inferring the cause. You may not yet know the timing, the scale, or whether it will repeat.
Next, sort your decisions by urgency. Some can't wait, such as a customer you could lose this week or a safety issue. Others can wait for evidence. Tell your team which are which. That single act keeps urgency from spreading to every decision.
Set a date for the next look and give each open question an owner. Decide who will validate the facts, who will weigh the alternatives, and when decisions will be made. A review date gives your team permission to keep working without a verdict, and it keeps patience from turning into delay.
Then make it safe to disagree with you. Research psychologist Gary Klein addressed this in Performing a Project Premortem, published in Harvard Business Review. His subject was project planning, but his point carries over. People often hold reservations they don't voice, and outcomes improve when leaders make speaking up safe. Harvard professor Amy Edmondson found a related pattern in Psychological Safety and Learning Behavior in Work Teams. In 51 teams at one manufacturing company, shared safety for interpersonal risk-taking was associated with more learning behavior, which in turn linked to team performance. One company is a narrow base, but it points the same way. Ask for the account that contradicts yours.
Four questions help:
What does this number measure, and what does it leave out?
What would change my reading of it?
Which decision can't wait, and which one can?
Who closest to the work hasn't spoken yet?
Where Culture and Context Change the Practice
Norms for speaking up differ across organizations and across countries. In some workplaces, challenging a senior leader's reading is routine. In others it carries a real cost. Where it does, one open invitation won't be enough. You may need to ask people individually, in writing, or through someone the team trusts.
Disclosure duties differ too. Where a number must be reported externally on a fixed date, the window for careful internal reading shrinks, and separating the known from the inferred matters even more. Your counsel and auditors set those constraints, not this article. The principle travels. The practice has to fit the local rules, culture, and calendar.
The research cited here also leans on student samples, laboratory tasks, and a single company. None of it measures a leader's response to a missed business number, so read it as direction, not proof.
Choose Your Response Before the Number Arrives
In the premortem described in Performing a Project Premortem, Gary Klein has team members assume a project has already failed and then generate plausible reasons why. This adapts his technique to a leader's own reaction, and his article doesn't test that use. The logic still works.
Before the next reporting date, imagine a bad number comes in well short. Decide in advance what you would say first, what you would ask for, and which decisions you would refuse to make until the evidence arrives. Write it down. A response you've rehearsed is harder for the moment to hijack.
This is a skill, which means it can be built, and organizations can build it on purpose. Do emerging leaders get to present unfavorable results without being punished for the result itself? Are managers taught to tell investigative questions from accusatory ones? Does the organization recognize people who surface problems early, or does it reward the appearance of control? The practice isn't reserved for people with executive titles either. Anyone who owns a result, a team, or a commitment faces this moment on some scale.
You don't choose the number. You do choose what the people around you learn from how you receive it. What did your team learn about you the last time a number came in short?
Support for the Decisions Between Quarters
Aspirations Consulting Group works with executives and other leaders at growth, transition, and performance-pressure moments, when a decision has to be made before the picture is complete. The work helps leadership teams sharpen judgment, set priorities, and act with clarity across the organizational challenges that tend to arrive together. See how we support leadership teams.
Keep Sound Judgment in Your Inbox Every Weekday
Request a complimentary subscription to ACG Strategic Insights™ and receive practical perspective on leadership, strategy, finance, and technology every weekday, shared with more than 10 million current and aspiring executives and other leaders worldwide.
Thanks for reading!
~ Jerry Justice
Living to Serve, Serving to Lead™
Comments