Team wellbeing setup
Anonymous check-ins, workload signals and the aggregation rules.
Team wellbeing setup
Team wellbeing combines two signals: a short self-reported check-in and workload numbers that already exist in the workspace. It never reads message content.
What it collects
- A wellbeing score from the member's own check-in.
- A workload label (one of the fixed set, defaulting to Balanced).
- An optional free-text note the member writes.
- Task load derived from assigned tasks and their statuses.
That is the whole input surface. There is no sentiment analysis of chat, no keyboard or activity tracking, and no reading of communications.
First run
- Open /dashboard/team-wellbeing.
- Submit a check-in. It posts to /api/dashboard/wellbeing and creates a row in wellbeing_metrics.
- The page then shows the 14-day happiness trend, the mood distribution, per-member wellbeing, and a workload-vs-wellbeing comparison.
- Read the "About anonymity" card before sharing any of this with the wider team — it states the aggregation rules in the same place the data is shown.
Alerts
When a check-in moves a member's score, the write path creates a wellbeing notification for that member naming the previous and current score. The workspace switch wellbeingAlert in /dashboard/team/settings controls whether that notification is recorded at all.
Editing a check-in
PATCH and DELETE /api/dashboard/wellbeing/<id> let a member correct or remove their own entry. Removing it also removes it from the trends on the next render.
Using it well
- Treat the numbers as a prompt for a conversation, not a verdict on a person.
- Compare workload against wellbeing rather than ranking either one.
- Keep the anonymity rules intact: small groups should be merged rather than shown individually.
- Pair this page with /dashboard/ethical-metrics, which prints the formula behind every indicator.