How do the very best forecasting teams actually run their week?
They separate three meetings that most teams collapse into one. A deal review, where the conversation is about strategy on named opportunities and nobody says a number. A forecast submission, where every manager submits a written commit early in the period and it is logged so it can be graded later. And a variance review, where last period's called number is compared against the result and the misses are dissected by cause, not by person. The discipline that makes it work is that the forecast is submitted in writing before the discussion, so the room cannot anchor on the loudest voice. Underneath it all sits the operating cadence: the same meetings, the same order, every week, so the forecast is a routine output rather than a quarterly panic.
Go deeper
4 resources, 4 link-checked.
📄 Article
✓ Link checkedFreeAdvanced
The full explanation of the operating rhythm Sacks ran at Yammer, with the audience Q and A that surfaces the edge cases. Use this version rather than the Medium original, which blocks a lot of readers.
Defines accuracy against the day one forecast rather than the revised one, which is the single change that makes the metric honest. Includes the grading bands most leaders now quote.
Gives testable definitions for pipeline, best case and commit, including the entry criteria a deal must meet. Copy these into your CRM and most forecast arguments disappear.
This is the question restated as an episode: which meetings happen when, what gets submitted in writing before anyone talks, and how last period's miss gets reviewed. Zech built a forecasting product, so he has seen a lot of these calendars.
