The problem: a culture of hidden overtime
Burnout often goes unspoken. Status meetings look green, boards fill with Done, yet Slack stays active late, PTO goes unused, and "just this sprint" repeats for the third time.
Chronic overtime usually comes from:
- Underestimated capacity — demand exceeds committed hours
- Invisible WIP — off-board or "small" work that never totals
- Hero culture — praise for rescue without fixing the system
Short-term velocity rises; then bugs, turnover, and bigger slips follow.
Symptoms and costs
| Symptom | Cost |
|---|---|
| Same names on every critical task | Key-person risk |
| Estimates always optimistic | Planning distrust |
| Shallow pre-release review | Quality debt |
| Absenteeism or quiet quitting | HR and delivery |
| "We can't say no" | Chronic scope creep |
Exact burnout rates vary by organization—the pattern repeats: sustained demand > sustainable capacity.
Framework: Capacity truth → Limits → Recovery
1. Capacity truth
Each week:
- Remaining hours per person on open tasks
time_summary— logged vs estimated for calibration, not punishment- Subtract meetings and support from capacity—40 calendar hours ≠ 40 delivery hours
If next week's heatmap is red, talk today—not Friday night.
2. Limits — WIP and policy
- WIP limits per person and column
- Rule: red cell → no new assign without trade-off
- 15-minute manager sync on heatmap—not 60-minute status theater
Limits without enforcement are decoration. PMs must say no with data.
3. Recovery — after crunch
After a hard release:
- Cool-down sprint — real capacity for debt
- Retro on why overtime happened—not only celebrate ship
- Adjust default estimates
Skipping recovery guarantees the next burnout cycle.
What leads should do
Rebalance before re-estimate — moving one task off a saturated person often suffices.
See fragmentation — ten small tasks can weigh more than two epics.
Protect PTO — block calendar in sprint planning.
Praise sustainable pace — not only rescue stories.
Where WKFGo helps (honestly)
WKFGo is not a burnout cure. Useful capabilities:
workload_heatmap— open tasks and remaining estimate per usertime_summary— time calibration views- Kanban WIP — limits on the board
- Portfolio overview — cross-project overload
If culture rewards heroes at all costs, the tool only shows red—leadership must accept trade-offs.
The burnout cycle: how it forms
Week one: a critical task slips—volunteer overtime.
Week two: the same volunteer becomes default owner on the next item.
Week three: review quality drops—bugs escape.
Week four: hotfix overtime—"just this once."
Without a heatmap the cycle stays invisible. Managers think the team is resilient until a resignation letter arrives.
Break the cycle: red-cell policy, recovery sprint, public praise for sustainable delivery.
Calibrating with time summary
Use time_summary for learning, not surveillance:
- Compare estimated vs logged time per work type
- Adjust defaults next sprint
- Discuss outliers in retro—blocked? underestimated?
Teams that never weaponize time data collect more honest numbers.
Temporary pressure vs chronic burnout
Short pressure (real deadline, incident) differs from chronic burnout:
| Temporary pressure | Burnout | |
|---|---|---|
| Duration | Days | Weeks plus |
| Recovery | After ship | Does not return |
| Volunteers | Occasional | Same names always |
| Quality | May hold | Degrades |
PMs should schedule recovery after crunch—not a fuller next sprint.
Anti-patterns
- Treating overtime as a positive KPI
- Using heatmaps only to find underutilized people
- Time tracking for punishment
- Skipping retro after crunch
Getting started this week
Days 1–2: Open the heatmap—list anyone with a red cell next week.
Day 3: Defer or reassign one task per red person; document trade-offs.
Days 4–5: Add policy: new assignments on red require PM approval.
After two sprints, compare hotfix count and PTO usage—qualitative signals alongside the heatmap.
Frequently Asked Questions
Should we ban overtime?
Not always—real occasional crunch happens. The issue is pattern. Track frequency per team.
Is time tracking mandatory?
Useful for calibration; toxic for surveillance. Make purpose transparent.
What about small teams?
Smaller teams burn faster. Weekly heatmap glances help even with four people.
Burnout vs disengagement?
Burnout pairs exhaustion with cynicism; disengagement is withdrawal. Both worsen with overload and unclear priorities.
Summary
Recurring overtime is a symptom. Capacity truth, WIP limits, and recovery sprints after crunch break the burnout cycle. Use time summaries for calibration; heatmaps for conversations before crisis.
Lead with sustainable pace
Open the heatmap in standup. One red person—defer or reassign one task. Policy: "new assign on red requires PM approval." Repeat two sprints.