Sara's output has been climbing steeply for three consecutive weeks, reaching 4.2× her personal baseline in the current period. Activity includes a consistent weekend push pattern — three of the last four weekends show commits on Saturday or Sunday. This is not her historical norm.
Her MR review activity remains stable, which suggests she is not simply compensating for blocked code — she is actively shipping. The volume increase is self-driven or deadline-driven. There is no visible external trigger (no new project, no team size change) in the connected data.
Sustained output at this level over 3+ weeks carries high burnout risk. Engineers who sustain 3× baseline for more than two weeks without a visible wind-down tend to either drop sharply (sudden disengagement) or burn out into low-quality output followed by leave.
Schedule a 1:1 this week focused on workload, not delivery. Ask directly whether the pace is sustainable. Explore whether the load is distributed fairly across the team and whether there is anything Sara is absorbing that should be delegated or deprioritised.
| Week | Commits | MRs | Reviews | Active days | Index | vs baseline |
|---|---|---|---|---|---|---|
| WK 10 (May 12–18) | 22 | 2 | 4 | 5/5 | 78 | ↑ +190% |
| WK 11 (May 19–25) | 34 | 4 | 5 | 6/5 ⚠ | 91 | ↑ +310% |
| WK 12 (May 26–30) | 31 | 3 | 5 | 5/5 + Sat | 94 | ↑ +280% |
| Baseline avg (WK 1–9) | ~11 | ~2 | ~3 | 4/5 | ~62 | — |
Output at 4.2× personal baseline for 9 of last 14 days.
Pattern duration: 3 weeks — above threshold.
Commits on 3 of last 4 weekends. Not observed in weeks 1–9.
AI assessment: high-complexity work pattern with increasing MR size. Risk of quality degradation.