Team Wellbeing
Illustrative scenario · GlobalTech — 200-person engineering org
GlobalTech wires after-hours drift into an alert
A scenario for an org that keeps saying it cares about burnout but has no signal until someone resigns: which indicators to enable, what to deliberately leave off, and who is allowed to see what.
- Team
- 200 engineers across 14 teams
- Cadence
- Continuous flow, no fixed sprint boundary
- Existing tooling
- Calendar plus a ticket tracker
GlobalTech is a fictitious team. This is not a customer story and contains no result figures or attributed quotes. What it does contain is real: every route below exists in the product, and every measure states where its number is computed.
Where it starts
- Two senior engineers left in a quarter and both exit interviews named workload.
- The org measures output by tickets closed, which rewards the people working nights.
- Managers see individual numbers and start comparing them aloud.
- There is no agreed threshold for 'too much', so nobody raises it early.
What to turn on, in order
Order matters — each step assumes the one before it is already in place.
- 1
Agree the refusal list first
Before any indicator is enabled, decide what will never be measured: no lines of code, no per-person velocity, no activity or keyboard-time scores, no default ranking of people against each other. Writing this down is what makes the rest of the rollout survivable.
- 2
Enable the four team-level indicators
Predictability, workload distribution, review equity and after-hours drift. All four aggregate to team level; each card expands to show its formula, the source events and the exclusions.
- 3
Set thresholds and who gets alerted
Threshold configuration is stored per workspace. Alerts go to the people who can change the work — the team lead and the delivery manager — not to the whole org.
- 4
Restrict who can see individual data at all
Roles decide whether a member, lead or admin can open per-person views. Individual ranking exists only behind an explicit switch that states its consequences before you turn it on.
- 5
Give the check-in somewhere to land
Wellbeing check-ins are stored per member and feed the team-level trend. They are the only self-reported input in the model, so the page says so rather than blending them silently into computed figures.
- 6
Export the numbers you publish upward
Any report dataset downloads as CSV or JSON. Publishing the same export leadership sees removes the temptation to re-narrate the numbers on the way up.
What to watch
No target values. Each row says where the number is computed and what feeds it, so you can decide what good looks like on your own data.
| Measure | Where the number comes from |
|---|---|
| After-hours drift | Task events timestamped outside the member's configured working hours, aggregated to team level on /dashboard/ethical-metrics. |
| Review equity | Who reviews whose work, computed from review events in the workspace — the page shows the matrix it is built from. |
| Load against seniority | Whether the heaviest load lands on the least experienced members, from the member profiles and their open task load. |
| Check-in trend | Self-reported, per member, aggregated to team level. Treated as a signal to ask about, never as a score. |
Walk this scenario on your own workspace
Every route above is live. The fit quiz will tell you which of these scenarios is closest to your team before you start.