Deciding When Both Forecasts Can Be Wrong: Lessons from Tetlock’s Superforecasting.
This week turned two numbers into facts, a flexible-megawatt promise and a declared peak. Both are forecasts of how a campus behaves under stress it hasn’t faced. Part III asks how to make that kind of forecast without fooling yourself, through Philip Tetlock and Dan Gardner’s Superforecasting (Crown, 2015).
Tetlock’s finding across years of forecasting tournaments: the best forecasters aren’t smarter about the future, they’re more disciplined about two things. They assign probabilities instead of narratives, and they update in small steps as the world moves, separating what’s known from what’s assumed for convenience. Organizations do the opposite: a connection date quoted once becomes a commitment, a utilization assumption becomes an unrevisited fact, and when reality diverges the paper gets defended, not revised. The running example, a case assuming a 30-month upgrade, 70% utilization and four-year payback, with none holding 18 months later, shows the Tetlock-style review re-ranking options against today’s probabilities rather than loyalty to the original case.
It needs no tournament, just a redesigned meeting: break the case into score-able variables (connection month, peak kW, utilization, price band), assign ranges not points, name the evidence that would move each number and who watches for it, review on a fixed cadence, and reward updating, punishing only the refusal to update. Your action this week: find the single-date assumption unexamined the longest and ask its probability today. Full design at renegrywnow.com.
Reflection questions
Which single-date assumption in your current case has gone unexamined the longest, and what’s its probability today?
Are your business cases written in ranges and probabilities, or single points that pretend to a precision nobody has?
Does your organization reward updating a number when evidence changes, or punish it, so the team stops telling you when numbers move?
Keywords: Superforecasting, Tetlock, Probabilistic Thinking, Forecast Updating, Decision Discipline, Ranges vs Points, Business Case Review, Grid Timeline, Capex Case, Leadership
Series: Energy Dominance · Week 42 · Part III
Previous: Part I — Flexible AI Data Centers · Part II — Why Peak Demand Kills Data Center Projects.
