Looking back: April 2026
There was a specific board meeting, years ago, that changed how I thought about forecasting. I hadn’t realized until that meeting how deeply I’d absorbed a culture where forecast commitment was treated as a display of confidence rather than as a probabilistic estimate. The board conversation that surfaced this was uncomfortable, instructive, and one of the more useful feedback moments of my career.
The Setup
I was walking the board through the current quarter’s forecast. Coverage looked reasonable. Pipeline quality was mixed. I’d committed to a number that was toward the optimistic end of the range because — as I told myself — that’s what you did. Boards wanted confidence. Leaders delivered confidence. The forecast was aspirational because aspiration was the expected register.
I walked through the slides. Numbers matched expectations. I was ready to move to the next topic.
An experienced board member interrupted. “I want to push on this. You’ve told us the commit number. I want to understand what you think the actual number is going to be.”
The Question That Reframed Everything
The question was simple but cracked something open. The commit number and the expected number had quietly become different things in my head — and I hadn’t been articulating the difference. The commit was aspirational. The expected was what I actually thought would happen. Those numbers differed by about 15%. I’d been showing the first and privately carrying the second.
I said something like: “The commit is X. My personal expectation is closer to Y.”
The board member nodded. “Thank you. That’s the number I want. I need to make decisions based on what you actually think, not on what you think you’re supposed to say.”
The meeting shifted. We spent the next 40 minutes talking about the honest forecast — the one I actually believed — and the uncertainty around it. Where were the biggest risks? What were the leading indicators? What would I see in the next 30 days that would update my estimate?
The conversation was more useful than any previous board conversation I’d had about revenue. Not because the number was better. Because the number was honest.
What I Realized Afterward
The lesson that took a few weeks to fully land: forecast commitment and forecast honesty are different things, and treating them as the same thing produces worse decisions.
I’d been trained — through years of watching leaders perform confidence, through cultural messaging about “missing your number” being unforgivable, through my own discomfort with presenting uncertainty — to converge on a single commit number that was optimistic by design. The optimism served a signaling function (look how confident the leader is) but undermined the real function of forecasting (help decision-makers plan).
The board member’s question forced a separation I hadn’t been making consciously: the commit is a promise to the team and the market; the expected is an analytical estimate. Different purposes, different numbers, different conversations.
How I Forecast Now
After that meeting, I shifted my forecasting practice in specific ways:
1. I present ranges, not point estimates.
The honest forecast has a low, mid, and high. The commit is usually somewhere between low and mid. The expected is around mid. The upside — what happens if things go unusually well — is the high. Three numbers, not one, force a real conversation about uncertainty.
2. I explicitly state what would move the forecast.
“If these three deals close on current timelines, we hit the upside. If any two slip, we hit the midpoint. If all three slip, we’re at the low end.” This gives the board (or any audience) the ability to track the forecast themselves, which builds trust faster than presenting a clean number ever did.
3. I separate commit from expectation deliberately.
The commit is what I’m willing to publicly stand behind and be measured on. The expectation is what I analytically believe. I present both, name them differently, and explain the gap. Some audiences find this jarring at first. They end up appreciating it.
4. I review my forecast accuracy quarterly, honestly.
The single most important forecasting discipline is looking back. Was my forecast within 5%? 10%? 20%? The pattern over four quarters tells me whether I’m a reliable forecaster, a systematically optimistic one, or a sandbagger. Every forecaster has a personal bias. Knowing yours is a precondition for adjusting.
The Broader Lesson
The board meeting taught me something beyond forecasting specifically. It taught me that performing confidence — in any domain — often costs more than it provides. Audiences (boards, teams, customers) are usually more sophisticated than the performance assumes. They can tell when the presentation is calibrated for signaling rather than for honesty. The leaders who consistently present honestly — with appropriate uncertainty, with explicit reasoning, with acknowledged risks — build trust that the performative leaders can’t match.
This is hard in cultures that reward confidence. It’s the right bet anyway, because the alternative is a long career of building trust on unstable ground. One honest forecast compounds into permission to be honest about everything else. One performative forecast forces the next one to also be performative.
What I’d Tell a First-Time CEO
If you’re a first-time CEO or a first-time revenue leader, resist the temptation to converge to a single commit number that performs confidence. Present the range. Explain the uncertainty. Separate commit from expectation. Your board will be more helpful, your team will trust you more, and your own decision-making will be cleaner.
The board meeting that taught me this was uncomfortable for me at the time. It’s also the meeting I most often refer back to when I think about what kind of operator I want to be.
Honesty about uncertainty is a professional muscle. Most leaders aren’t taught it. Many cultures actively punish it. The leaders who develop it anyway build something more durable than the confident-performer alternative.
It’s a quieter way to lead. Over time, it’s also more effective. I’m grateful for the board member who asked the question that forced me to see the difference.