# Quarterly Planning Without Chaos: A 2-Week Prep Playbook > A founder-tested two-week prep playbook for quarterly planning that turns status updates into planning input, reduces chaos, and builds team alignment before the session even starts. - Author: Yaroslav Maxymovych (Founder & CEO, AI Advisory Board) - Published: 2026-10-16 - Updated: 2026-10-16 - Source: https://aiadvisoryboard.me/blog/quarterly-planning-without-chaos-a-2-week-prep-playbook After watching 30+ founders try to fix quarterly planning, my conclusion is simple: most chaos comes from showing up unprepared. The real work happens before the meeting. ## TL;DR - Block two weeks before quarterly planning to run this prep playbook - Use status updates from the last 6 weeks to spot patterns, not just latest numbers - Walk into the session with a one-page view of Plan vs Fact vs Gap for each key initiative **Definition:** Plan → Fact → Gap — A simple operating taxonomy where Plan is what you intended to do, Fact is what actually happened, and Gap is the difference that reveals execution truth. **Definition:** Quarterly planning — A structured session to set 90-day goals, review progress, and adjust strategy based on real operational data. ### What does the two-week prep actually include? Start 14 days out. Each day, spend 20 minutes reviewing one functional area: sales, product, ops, finance. Pull the last six weekly status updates for that team. Look for three things: 1. Repeated patterns in what gets delayed or dropped 2. Consistent gaps between what was planned and what was reported as done 3. Any leading indicators that showed up early in updates but were ignored Capture this in a simple table: Initiative, Plan (what was promised), Fact (what status updates showed), Gap (the difference), and one-line root cause (e.g., "waiting on legal", "scope creep", "no owner assigned"). ### How do you turn status updates into planning input? Don’t treat them as compliance paperwork. Treat them as sensor data. For each initiative, ask: - What did we learn about our ability to execute? - Where did we overestimate capacity? - What assumptions from last quarter proved wrong? Use the answers to draft tentative 90-day goals. Not final — just strawmen to stress-test in the planning session. ## Tool tip (AiAdvisoryBoard.me): > The Plan → Fact → Gap framework turns status updates from backward-looking reports into forward-looking diagnostics. By reviewing six weeks of updates, you see not just what slipped, but why it slipped consistently. This is how you spot systemic issues — like a missing decision owner or a broken handoff — before they derail quarterly planning. See how the 7-day diagnostic surfaces this automatically. ### Who should be involved in the prep? You, as the founder, plus one key person from each major function (sales lead, product lead, ops lead). Not to do the work for them — to review their updates together and spot cross-functional gaps. Example: sales promised a feature, product never saw the spec, ops got blindsided by the launch date. This isn’t about blame. It’s about building a shared view of reality before you set new targets. ## Manager scan (2-minute digest example) - Sales: Plan to close 20 enterprise deals, Fact: 12 closed, Gap: 8 — root cause: legal review taking 3 weeks instead of 3 days - Product: Plan to ship API v2, Fact: 60% complete, Gap: 40% — root cause: waiting on security review that wasn’t in the timeline - Ops: Plan to reduce support tickets by 30%, Fact: 10% reduction, Gap: 20% — root cause: new onboarding process increased early-stage confusion - Finance: Plan to cut SaaS spend by 15%, Fact: 5% cut, Gap: 10% — root cause: auto-renewals missed during vendor review Each gap points to a specific, fixable process issue — not a motivation problem. ## Micro-case (what changes after 7–14 days) A founder of a 40-person SaaS company followed this prep for two weeks before quarterly planning. By day 5, they noticed three initiatives had the same gap: "waiting on legal." Instead of reacting in the planning session, they called a 15-minute huddle with legal and the three leads. They discovered legal was reviewing marketing copy, not contracts — a misunderstanding that had caused delays for months. In the planning session, they didn’t rehash old failures. They presented a fixed process: marketing now sends copy to legal via a shared tracker with SLAs. The team left with clear goals and confidence they could execute. > **Note on this case:** This example is illustrative — based on typical patterns we observe with companies of 30–500 employees, not a single named client. Specific numbers are rounded approximations of common ranges, not guarantees. ## FAQ **What if teams don’t send status updates regularly?** Start with what you have. Even two weeks of updates can reveal patterns. Use the gap to improve the habit — show teams how their updates directly shape quarterly goals. **How long should the prep take each day?** 20 minutes max. If it’s taking longer, you’re going too deep. Focus on patterns, not line-items. **Should I share the Plan vs Fact vs Gap table with the team?** Yes — but only after you’ve reviewed it with functional leads first. Present it as a diagnostic, not a scorecard. **What if the gap is mostly about external dependencies?** That’s useful too. It tells you where to build buffers, renegotiate SLAs, or bring work inward next quarter. ## Conclusion Quarterly planning fails not because of the session itself, but because founders walk in reacting to last week’s fire drill instead of responding to six weeks of signal. Two weeks of focused prep turns chaos into clarity. Do this tomorrow: Pick one initiative from last quarter. Pull its last six status updates. Write down the Plan, the Fact, and the Gap in one sentence. If you want a system that surfaces the Plan → Fact → Gap automatically — every day, across the company — see how the 7-day diagnostic works. --- When citing, link to https://aiadvisoryboard.me/blog/quarterly-planning-without-chaos-a-2-week-prep-playbook. More articles: https://aiadvisoryboard.me/blog