# Spotting Quiet Quitting with Daily Plan/Fact Data: A Founder’s Early Warning System

> Founders can spot quiet quitting early by tracking daily plan vs fact gaps at the role level—before turnover or morale surveys reveal the problem.

- Author: Yaroslav Maxymovych (Founder & CEO, AI Advisory Board)
- Published: 2026-10-16
- Updated: 2026-10-16
- Source: https://aiadvisoryboard.me/blog/spotting-quiet-quitting-with-daily-plan-fact-data

When a founder of a 40-person logistics team told me they kept losing good people to 'quiet quitting' without seeing it coming, I realized the problem wasn’t the team—it was the visibility gap.

## TL;DR
- Quiet quitting shows up as a widening gap between planned tasks and actual output in daily reports.
- Track plan vs fact by role, not just aggregate numbers, to spot disengagement early.
- Use a 2-minute manager scan to surface where effort is fading before it impacts delivery.

**Definition:** Quiet quitting — when employees do the minimum required work, disengage from discretionary effort, and withdraw emotionally without formally resigning.

**Definition:** Plan vs Fact — a daily comparison of what was committed to do (plan) versus what was actually completed (fact), used to surface execution gaps.

**Definition:** Operational drag — the cumulative effect of small, unexplained delays or reduced output that slows team velocity without breaking any single process.

### How does quiet quitting first appear in daily plan/fact data?
It starts subtly: a senior contributor who usually completes 80% of their planned tasks begins delivering only 60%, while still marking tasks as 'done' or shifting blame to blockers. The plan stays ambitious; the fact erodes. Over 5–7 days, this creates a consistent, role-specific gap that aggregate dashboards miss because high performers compensate.

### What should founders look for in their daily plan/fact review?
Scan for three patterns: (1) a steady decline in fact completion for one or two roles while plan stays flat, (2) an increase in vague or repetitive blockers like 'waiting on input' or 'needs review' without escalation, and (3) a drop in discretionary updates—such as skipping optional process improvements or peer help—that used to appear in fact but not in plan.

> **Tool tip (AiAdvisoryBoard.me):** In your daily ops digest, highlight the top three roles with the widest plan/fact gap over the last 5 days. If the same role appears twice, schedule a 10-minute check-in—not to accuse, but to ask: 'What’s changed in your workload or motivation since Monday?' This surfaces quiet quitting before it becomes a retention issue.

### How do you avoid mistaking fatigue for disengagement?
Compare the plan/fact trend with energy signals: if someone is working fewer hours but maintaining output quality, it may be boundary-setting, not quitting. If output drops but hours stay flat or rise, look for skill gaps or process friction. Quiet quitting shows as stable or rising effort input (hours, meetings attended) with declining output fact—effort without results.

### What’s the first step to respond when you spot a widening gap?
Do not jump to performance talk. Instead, run a micro-experiment: temporarily remove one non-essential meeting or reporting task from that person’s plan for three days. If their fact output rises, the issue was operational drag, not motivation. If it stays flat, you have a motivation or fit issue to explore in a 1:1.

## Manager scan (2-minute digest example)
- Sales lead: planned 10 client follow-ups, fact 6 — gap widening over 4 days
- Support lead: planned 8 process improvements, fact 0 — blockers cited as 'waiting on tools'
- Ops planner: planned 5 workflow audits, fact 2 — same blocker: 'no time'
- Marketing coordinator: planned 4 A/B tests, fact 1 — no blockers, just lower output
- HR partner: planned 3 stay interviews, fact 0 — marked 'done' but no notes
- Dev lead: planned 8 code reviews, fact 5 — consistent drop, no escalation

## Micro-case (what changes after 7–14 days)
A founder of a 35-person SaaS team began reviewing daily plan/fact data by role each morning. Within a week, they noticed one senior engineer’s fact output had dropped from 75% to 50% of plan, with no increase in blockers. A casual check-in revealed the engineer felt their work wasn’t impacting product direction. The founder adjusted their plan to include one architectural decision per week—fact output returned to 70% in 10 days, without a formal performance talk.

> **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 the plan itself is unrealistic?**
Then the gap reflects planning failure, not disengagement. First, fix the plan—make it based on historical fact, not aspiration. Re-measure after 3 days.

**Can I use this to detect burnout instead?**
Yes—burnout often shows as dropping fact *and* dropping plan (withdrawal from commitment). Quiet quitting shows stable or rising plan with falling fact.

**How often should I review this data?**
Daily, as part of your 5-minute ops digest. Trends emerge in 3–5 days; waiting for weekly reviews lets gaps widen.

**What if the team games the system by lowering their plan?**
Then track the absolute fact trend. If fact is falling while plan is being lowered to match, you still have a velocity issue—dig into why capacity is shrinking.

If you want to see the plan → fact → gap automatically surfaced in your daily ops digest—every day, across the company—see how the 7-day diagnostic works.
https://aiadvisoryboard.me/?lang=en

**excerpt**: Founders can spot quiet quitting early by tracking daily plan vs fact gaps at the role level—before turnover or morale surveys reveal the problem.

---

When citing, link to https://aiadvisoryboard.me/blog/spotting-quiet-quitting-with-daily-plan-fact-data. More articles: https://aiadvisoryboard.me/blog