Plan vs Actual: The Daily Ritual That Surfaces Drift Early

If you're an owner who looks at the same KPI dashboard every Monday and still gets blindsided by the same problems on Friday, the dashboard isn't the issue. The cadence is. Quarterly reviews catch drift after it's already cost you a quarter.

Why does quarterly review fail to catch drift?

Because by the time a quarterly number is "off," the cause is six to ten weeks upstream and the people involved have moved on. You're doing forensics, not management.

Definition: Operational drift — the gap between what a team plans to do and what they actually do, accumulating quietly over days while looking fine at the weekly level.

Weekly catches it later than daily. Monthly catches it later still. By quarterly, you're writing a post-mortem.

What is Plan → Fact → Gap?

A three-step daily loop. Plan is what you said you'd do. Fact is what actually happened. Gap is the delta — and more importantly, the reason for it.

Definition: Plan → Fact → Gap — a daily review pattern where the morning's intended outputs are compared to the evening's actual outputs, and the cause of any difference is named before it compounds.

The loop is boring and unsexy. That's the feature. Anything dramatic enough to be exciting was caught too late.

How does the 5-minute version actually run?

Two slots, total 10 minutes, every working day.

Morning Plan (5 minutes)

At the start of your workday, write three to five concrete outputs you expect by end of day. Not tasks — outputs. "Draft sent to legal" is an output. "Work on contract" is not.

Constraint: must fit on one screen. Must be specific enough that a stranger could verify them at 6pm.

Evening Fact + Gap (5 minutes)

At the end of your workday, three columns: Plan / Fact / Gap. For each item, write what actually happened and a one-line reason for the delta. If the gap is zero, you write "—". If it's not zero, you write the cause, not the excuse.

The discipline is in the cause. "Got distracted" is not a cause. "Procurement question from CFO took 90 minutes" is a cause.

Copy/paste owner-CEO diary template

This is the version we hand to founders running this for the first time. It fits in any note app.

Date: [YYYY-MM-DD]

MORNING PLAN (write at 9:00, before email)
1. [Output]
2. [Output]
3. [Output]
4. [Output]  (optional)
5. [Output]  (optional)

EVENING FACT (write at 18:00, before closing the laptop)
1. Plan: [...] | Fact: [...] | Gap: [...]
2. Plan: [...] | Fact: [...] | Gap: [...]
3. Plan: [...] | Fact: [...] | Gap: [...]

GAP DIAGNOSIS (one sentence)
The single recurring cause of today's gaps was: [...]

TOMORROW'S TOP 1
Item I will not let slip tomorrow: [...]

The "single recurring cause" line is what makes the diary compound. After two weeks you can read 10 of these and see your actual bottleneck — almost never what you thought it was on day one.

Tool tip (AIAdvisoryBoard.me): Most owners running this manually for the first time discover the same pattern: the daily ritual reveals one or two recurring Gap causes that no weekly review surfaces. Our daily-management OS automates the Plan → Fact → Gap loop across the whole company — every team posts plan in the morning, fact in the evening, and the system surfaces aggregated gaps with cause patterns to leadership before they compound. See how the 7-day diagnostic works at https://aiadvisoryboard.me/?lang=en.

Manager scan (2-minute digest example)

Plan (this morning, across 6 functions):

• Sales: 12 outbound, 4 demos booked
• Ops: invoice run closed for May
• Product: shipping fix v2.1 to staging
• Support: SLA backlog under 8 hours
• Finance: payroll prep complete
• HR: 3 first-round interviews

Fact (this evening):

• Sales: 9 outbound, 2 demos booked
• Ops: invoice run delayed — bank file format change
• Product: fix shipped, 1 regression discovered late
• Support: SLA backlog 6 hours (under target)
• Finance: complete
• HR: 2 interviews, 1 rescheduled by candidate

Gap (top three causes):

• Bank format change unowned for 6 weeks (recurring)
• Sales head pulled into pricing call for 3 hours (planning miss)
• Regression test depth — same gap, third time this month

The Gap column is the only one that matters. It's also the only one that quarterly reviews never see in real time.

What does the Gap column teach you after two weeks?

Three things, usually. First, the same cause keeps appearing — and it's almost never the cause you'd have named at the start. Second, "external surprise" is a much smaller share than founders assume — most gaps are scheduling collisions or unowned dependencies. Third, the Plan itself is often too aspirational — and learning to write a Plan you can hit is half the lesson.

Definition: Recurring cause — the same gap-driver appearing in three or more daily logs within a two-week window. The signal that something is structural, not incidental.

What kind of Plan items should you avoid?

Three categories never belong in a daily Plan, because they cannot be verified by 6pm. Avoid status verbs ("review," "think about," "explore") — they can be done badly all day and still get checked off. Avoid multi-day deliverables disguised as daily items ("ship the new pricing page") — break them down or pull them out. Avoid items where you're not the owner — those belong in a different log entirely.

A good Plan item passes a stranger test: someone with no context could open the artifact at end of day and verify whether the output exists.

Micro-case (what changes after 7-14 days)

A 75-person logistics SMB had a Wednesday-morning leadership review that had felt useful for years and was quietly becoming theatre. The founder started the daily Plan → Fact → Gap ritual personally — five minutes morning, five minutes evening. By day eight he could name his actual top recurring cause: a dispatcher escalation pattern that nobody on the weekly review ever surfaced because by Wednesday it was old news. Day eleven he made one staffing change. By the end of week three the dispatcher pattern was gone, the Wednesday review had been cut from 90 minutes to 30, and the team was running the same diary at function-head level. Net change in actual operational throughput: roughly a 15% lift in same-day deliveries.

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.

Tool tip (AIAdvisoryBoard.me): Running the Plan → Fact → Gap ritual manually works at the founder level for one person. At team scale it falls apart inside a week — too much coordination overhead. The 7-day diagnostic shows you exactly which functions have the largest hidden gap and what the recurring cause is, before you spin up the company-wide cadence. Start the diagnostic at https://aiadvisoryboard.me/?lang=en.

FAQ

Won't my team see this as micromanagement? Only if you impose it on them before running it on yourself. Founders who run their own Plan → Fact → Gap diary for two weeks before asking anyone else to do it almost never get pushback — because by then they're naming structural causes, not individual blame.

Can I do this weekly instead of daily? No. The whole point is that weekly can't see day-to-day drift. The daily cadence is what makes recurring causes visible. Weekly cadence is for retrospective summary, not gap detection.

What if my day is too unpredictable to plan? Then write 3 outputs you'd accept as a good day, not 5 you'd love. The exercise is also a calibration exercise — your Plan accuracy improves week by week, and that's a finding in itself.

How does this differ from OKRs or weekly KPIs? OKRs measure quarterly outcome. KPIs measure trend. Plan → Fact → Gap measures execution at the day level — the layer where drift actually happens. They're complementary; they don't replace each other.

Do I need a tool for this? For one founder, a note app is enough. For a 30+ person company, the coordination overhead of running it manually across functions becomes the bottleneck — which is when the daily-management OS pattern matters.

Conclusion

The reason founders get blindsided isn't bad dashboards. It's that the review cadence is slower than the drift cadence. Quarterly catches the post-mortem. Weekly catches the symptom. Daily catches the cause.

Run the diary on yourself for two weeks. Find your one recurring cause. Then decide whether to scale the ritual to your team.

If you want a system that surfaces the Plan → Fact → Gap automatically — every day, across the company — see how the 7-day diagnostic works at https://aiadvisoryboard.me/?lang=en.