A real SignalTrue weekly leadership risk report. See exactly what your team would receive, act on, and close with — before you book a single call.
Signal Health dropped 7 points this week to 71/100, driven by a sharp rise in after-hours activity across the Engineering and Customer Success teams. 3 team clusters show early burnout indicators — meeting density has exceeded sustainable baseline for 11 consecutive days. One positive signal: the Product team's focus-time recovery is on track for the third week running. Recommended leadership action: redistribute load in Engineering before sprint planning on Thursday.
Engineering cluster: Meeting density 2.4σ above baseline
The Engineering team's average meeting load has exceeded sustainable threshold for 11 consecutive days. Historical pattern: this configuration precedes burnout signals within 3–4 weeks.
Customer Success: After-hours activity spike (+47% vs 4-week avg)
After-hours work in Customer Success has risen sharply this week — likely linked to the Q2 renewal cycle. Load redistribution or temporary capacity support recommended before this becomes structural.
Product team: Focus-time recovery — Week 3 of positive trend
Since the meeting audit in mid-April, the Product team has gained +1.1h of deep focus time per person per week. This trend is structurally stable and indicates the intervention is holding.
| Team | Risk Score | Primary Signal | Trend | Recommended Action |
|---|---|---|---|---|
| Engineering | 87 | 🔴 Meeting density 🟡 After-hours | ↑ Worsening | Pause non-essential ceremonies before Thursday sprint |
| Customer Success | 79 | 🟡 After-hours spike | ↑ New this week | Assign Q2 renewal support cover — temporary |
| Sales | 61 | 🟡 Focus-time low | → Stable | Monitor; no action required this week |
| Product | 31 | 🟢 Focus-time rising | ↓ Improving | Continue meeting audit protocol — working |
| Team | Risk Score | Primary Signal | Trend | Recommended Action |
|---|---|---|---|---|
| Finance | 28 | 🟢 Stable load | → | No action |
| Marketing | 55 | 🟡 Meeting load | ↑ | Review calendar |
| Operations | 40 | 🟢 Focus recovering | ↓ | Monitor |
| People & HR | 58 | 🟡 After-hours | ↑ | Check workload |
| Legal | 22 | 🟢 Low density | → | No action |
Tactical · Act within 7 days
Pause two recurring Engineering ceremonies this sprint
The weekly architecture sync and cross-team standup are adding 3.4h of meeting load per engineer without a decision record. Suspending both for one sprint would recover the focus-time needed to address the current density alert before it becomes structural.
Act by: Thursday May 9 — before sprint planning locks the calendar.
Tactical · Act within 14 days
Assign temporary Q2 renewal support to Customer Success
The after-hours spike in Customer Success is time-bound to the Q2 renewal cycle. Assigning one additional resource or redistributing two accounts to Sales Engineering would reduce load to within baseline before the pattern becomes habitual.
Act by: May 16 — cycle peak expected May 19–23.
Strategic · 60–90 day view
Formalise Product team's meeting audit as a company-wide protocol
The Product team's 3-week focus-time recovery is the strongest positive signal in the organisation this quarter. The intervention (weekly meeting audit + async-first default) is replicable. Rolling it out to Engineering and Customer Success is projected to recover 2.1h of focus time per person per week across both teams.
Strategic priority: Q3 planning window.
Every number above is generated automatically from calendar and collaboration signals — no surveys, no analyst, no manual work. Just signal, every Monday morning.
Or start a 30-day free trial — no credit card required