The Miss Isn’t the Failure. What You Do Next Is
8 Sept 2026 · 16 min
Tony Uphoff, a CEO with 35 years of P&L experience, breaks down how to handle quarterly misses. He separates four financial numbers often confused together, introduces range-based forecasting to catch shortfalls early, then sorts every miss into one of four root causes: miscalculation, market dynamic, execution gap, or competitive gap. Each gets a specific bridge plan with targets and timeline.
Chapters
There are few questions that can cause more anxiety for a CEO than, hey, how's the quarter shaping up? From the first week in the quarter to the last, C-level leaders regularly get asked how the numbers are looking from boards, employees, and partners. Heck, even my wife would ask how the quarter was looking. The reason the question can create so much agita is based on several factors: who's asking, how the quarter actually is shaping up, and what number they're actually asking about. In 35 years of P&L responsibility, I've found that boards to C-level to operating teams to employees is very easy to get 4 key financial metrics confused and in turn miscommunicate or confuse how the business is or isn't performing. I have learned a ton about how to run a business to the numbers, how to set them, manage against them, make appropriate plans and changes if we're pacing ahead or behind, and how to communicate about them to boards, Executive teams and employees. In this episode, in the related Substack Upoff on Media post, I share the frameworks and systems for managing a business to the numbers. On Substack, you can download and use the four frameworks referenced in this podcast in your own business. Okay, let's get to work. This episode is called The Miss Isn't the Failure What You Do Next Is. The board wants answers. Your team is afraid to admit doubt. What you do— what to do before you say anything to either one. The board deck is due. The forecast came in soft a week ago, and everyone in the building already knows it. Nobody has said so out loud because the first person to say it risks sounding like they never believed in the plan. That's the position every CEO eventually finds themselves in. Above you, a board and investors who signed off on a number and are anxious to know how the business is performing. Below you, a management team that either doesn't know how bad it is yet or is too nervous to bring it to you first. Both conversations run through the same person, you. And most days, you're the only one standing there. A recent Harvard Business Review piece on delivering bad earnings news got the mechanics right. Say it early, quantify the shortfall in concrete terms, kill the speculation before it starts, pair the bad news with a plan. All very good advice. It also assumes you already know 2 things that are actually the hard part: what you told people to expect in the first place and what really happened, as opposed to the version you're telling yourself happened. In 5 CEO roles, I've missed numbers and exceeded them. Thankfully, while I was more often on the positive side, the misses taught me far more. What follows are the systems those misses forced me to build, how I manage a business against its budget, how to diagnose the cause of a shortfall. How to build a bridge plan, and how to communicate about performance with the board and your operating team. The charts and frameworks that come out of it are yours to download and use in your own business. Most misses get decided before the year starts. Ask 10 CEOs whether their team can tell the difference between the budget, the forecast, the pipeline, and the quota assignment. In my experience, most can't. Those are 4 different numbers doing 4 different jobs, and most organizations flatten them into a single phrase, the number. That flattening isn't harmless. It creates confusion at the leadership table, produces inaccurate numbers, breeds anxiety that has nothing to do with actual performance, and every so often sets up a mistake serious enough to be catastrophic. The budget is what the board approves, the number the business is actually run on, the baseline every operating decision gets measured against all year. The forecast is what you actually expect to deliver in the month, quarter, and year, updated as real data comes in. And it's usually the number the board cares most about, even though budget is the one they signed off on. Pipeline is the raw material underneath the forecast, always larger, larger than what will actually close, discounted by stage and probability. The quota assignment is what you've asked the sales organization to carry, often set above the forecast on purpose as a stretch, and it should never be confused with what the company expects to report. Confuse those 4 numbers and a casual comment turns into a real problem. An executive tells a board member in the hallway that the team is running 10% ahead of the number and everybody nods. That's a good update if the number in question is budget. If it's forecast and the forecast has been trending below budget for 6 weeks, that same comment is wrong. And by the time it gets corrected, the board has already recalibrated around a number that was never real. The discipline isn't more communication. It's specifying which of the 4 numbers you're talking about every single time. The tool I've used for 30 years to manage the forecast is a best-case, worst-case, realistic-case model built specifically for quarterly and annual forecasting. Not a single figure, but a range with a 10 to 15% variance band that tracks actual and projected performance against budget as the quarter unfolds, not after it closes. Run the business against that range every week and a short Shortfall shows up as a trend line long before it shows up as a surprise, which is what actually lets you act on it early. The board benefit is real, but it's a byproduct. A board that has already seen the worst case in writing doesn't treat a shortfall as a betrayal. Here's some examples. InformationWeek was a $15 million business and losing money, and we took it to $175 million and $75 million in EBITDA in 4 years. We built the plan on a series of key indicators, not the year-end target, qualified pipeline by vertical, ad page growth against the prior year, market share against 6 competitors, and market share by individual advertisers. Every leader could recite them, so nobody was surprised by the outcome. But growth that fast creates its own pressure. Systems built for a $15 million business buckled at $75 million, and the leader who gets a business from one tier to the next isn't always the leader who gets it to the tier after that. Scaling meant rebuilding systems, changing out people who weren't scaling with us, and resetting expectations upward every quarter because a board that just watched you beat the number by 20% won't accept a repeat of last year's target. The Hollywood Reporter: 30% growth in a single year against a legacy print category everyone assumed was done growing. The number came from a specific plan built around total reach and early integrated print and digital offering, not a guess. We passed Variety in share of market for the first time, and the board never had to ask what was driving it because they'd seen the components every quarter. Dramatic growth curves are the trickiest forecast of all. No history to build a plan from. The Game Developer Conference and the event Black Hat both grew more than 40% a year on plans built from real registration sponsorship data, not hope. The pattern I've watched repeat, the target got set to satisfy a board conversation, not because everyone, anyone had evidence it was achievable. A recent survey of more than 2,000 business leaders found 81% of companies missed their sales forecast in at least one quarter over a 2-year stretch. Most misses aren't a market surprise. They're the plan finding out in public that it was never that precise to begin with. Don't explain it before you understand it. The moment the number turns negative, there are 2 instincts and both are wrong. The first is to defend the plan. The market's soft, the timing's off, give it another quarter. The second is to overcorrect, blow up the strategy, replace the team, apologize your way through the next board meeting. Both are a way of deciding what happened before you've actually found out. I give myself, and I tell any operator to give themselves, roughly a week before forming an opinion out loud. Not a week of silence, a week of gathering the actual signal. Pipeline conversion by stage, not just pipeline size. Win-loss detail on the specific deals that slipped, not a summary someone else wrote for you. What customers say when I get them on the phone myself, not the paraphrase in a deal review. What's actually changed with competitors? A price move, a new feature, a new entrant, and whether they're seeing the same softness we are. Whether customers are telling us directly that budgets are under pressure, which is a market signal, not an excuse, whether the shortfall is broad across the business or concentrated in one product, one region, or one team, the diagnosis takes discipline precisely because the pressure to have an answer arrives faster than the evidence does. This is where most leadership teams skip a step. They jump straight from we missed to here's the plan to fix it without ever confirming what actually broke. A recovery plan built on the wrong diagnosis doesn't just fail to fix the problem, it burns the credibility you'll need the next time something goes wrong. And there will be a next time. Every miss traces back to one of 4 places. After 35 years of this, almost every miss I've seen sorts into one of 4 categories, and the category determines nearly everything about what you do next. Miscalculation. That's ours. It was wrong from the start. The gap shows up in month 1, not month 9, because the leading indicators were off before you ever went to market. This is the most common cause behind a new launch that misses. Not a market that turned, but a target nobody had real evidence for. The fix is to rebuild the model instead of defending it. Reforecast off of real data, set the new number, and hold it. Market dynamic. The target was fair when you set it, but the market has contracted. The whole category slows at once and peers are missing similar numbers. This is what happened across most B2B print brands after the internet arrived faster and cut deeper than any of us modeled. The plan wasn't naive, the ground underneath it moved. The move here is to adjust the timeline, not the thesis, protect the plan's core assumptions and reset the pace against them. Execution gap. That's on us. And the target was right. Pipeline, hiring, or launch dates slipped against a plan nobody disputes. The math still works. This is the one that's hardest to admit because it's the one closest to home, and the fix is operating discipline. Name what didn't get done, who owns it, and the date it gets done by. Competitive gap. Our competitive position moved under us. You're losing competitive deals you used to win. Win rate is down against a market that isn't shrinking. Which is a different challenge than a market that is. The fix is to fund the product gap directly. No amount of sales effort outruns an uncompetitive offer. The distinction matters because each of these 4 demands a completely different conversation with the board and a completely different set of actions with your executive team. Mistake an execution gap for a market dynamic and you'll spend 2 quarters waiting for a recovery the market was never going to hand you. Mistake a market dynamic for an execution gap, and you'll fire people for a problem that was never theirs to own. A shortfall should never arrive without a plan attached. Every company I've run, the rule was simple. If you're forecasting a shortfall, you don't bring me the problem alone. You bring a bridge plan, a specific plan to close the gap and get back to or above budget within the next 2 quarters with the specifics, the owner, and the dates attached. Not a general purpose to work harder, an actual bridge from where the number is heading to where it needs to land. This does 2 things a recovery conversation after the fact never can. It surfaces the shortfall while it's still fixable, months before it would otherwise show up in a board deck. And it forces the person closest to the problem to do their own version of the diagnosis, diagnosis above miscalculation, market execution, or competitive, before it ever reaches me. Because nobody can build a credible bridge without knowing which one they're actually standing on. The board and the team need 2 different conversations, not one memo. The board wants the diagnosis, the revised trajectory, and the plan in that order delivered before they have to ask. State the shortfall in dollars and percent against the number they approved, not a description of how things feel. Tell them which of the 4 categories you've landed on and why, with the evidence, not the instinct. Give them a revised number with a date attached and be available for the follow-up questions instead of hiding behind a deck. What kills credibility with the board isn't the miss, it's finding out later that you knew more than you said when you said it. The team needs something different, clarity about what's actually being asked of them now and honest signal about whether this is about them or not. If the diagnosis says market dynamic or miscalculation, say so plainly and protect the team from carrying blame that isn't theirs. If it's an execution gap, say that plainly too, with names, owners, and dates, because a team that already knows something went wrong, wrong respects a direct conversation far more than a vague one. Silence in front of the team gets read as either panic or indifference. Neither is true, and both are worse than whatever you're actually feeling. What actually happens in the next 30 days? Get the real numbers before you get an opinion. A week of diagnosis before any external conversation. Board included. Diagnose before you communicate. Know which of the 4 categories you're in before you draft a single sentence to anyone outside the leadership team. Ask whoever owns the shortfall for a bridge plan, not an explanation. A specific plan to or above the number within 2 quarters with an owner and a date, not a promise to try harder. Tell the board first in writing before the meeting. State the shortfall in dollars and percent against the number they approved, not how things feel. Match the message to the diagnosis, not to your mood. A market dynamic gets a timeline reset. An execution gap gets names, owners, and dates. Don't apologize for a market you don't control, and don't excuse a team that didn't do its job. Tell the team the same week, not after the board reacts. A delay reads as evidence you don't trust them with the truth, which is a worse problem than the miss itself. Put a recheck on the calendar before you leave the room. 30, 60, 90 days out tied to the same leading indicators. You should have flagged this the first time. If you don't have those indicators yet, building them is the actual fix, not the recovery plan itself. The number was never the hardest part. Go back to the room I opened with. The board deck is due, the number is soft, and nobody has said it out loud yet. The instinct in that room is to treat silence as safety. It isn't. Every day that passes without confronting the truth and diagnosing the problem is a day the board and the team are each writing their own version of what happened, and neither version is likely to be generous. I've missed numbers plenty of times across 5 CEO roles. Print brands that declined faster than the plan accounted for, launches where the market taught us something the projections couldn't have. None of those misses cost me what a bad diagnosis or a slow, evasive conversation would have. The number is never actually the hardest part of the job. Deciding what it means and saying so before someone else decides it for you is. Hey, that's it for this episode. If you found this useful, please do one thing. Follow the Uphoff on Media podcast on Apple or Spotify, and please leave a rating. It's the single best way to help another operator find this. I'm Tony Uphoff, back at it next week.










