Documentation

Run your first team health check

Create a check, get participants to respond, close it, and turn the result into an action

A health check moves through four phases - Draft, Collect, Discuss, Closed - and the closed run feeds improvement actions and trends.

How

  1. Open Team health → Health checks in the sidebar.
  2. Click New health check. Pick a Team - everyone on that team is invited - and a Health model (Pulse 5, say). Response identity is Anonymous, Aliases or Named, and defaults to Anonymous. Show results after is how many answers a dimension needs before the snapshot frozen at close carries its average and distribution; it starts at 3. Title and Automatically closes are optional; once that deadline passes, ratings are refused. Open & notify creates the check and notifies the roster; Save draft keeps it unopened.
  3. Participants rate each dimension on the run page, with an optional comment (shown per the run's anonymity mode) and an optional up/flat/down "felt direction" vote.
  4. Watch participation from the Recent checks list, which carries a responded count on every row, or from the run's Participants panel. Manage participants there invites someone from another team or removes a person, which also deletes their answers. An anonymous run withholds names, so the panel reports how many have answered, not who.
  5. In Discuss, a facilitator puts one dimension On stage for everyone and can start a shared countdown timer of 1, 2, 3, 5, 10 or 15 minutes.
  6. Move the run through the stepper - Draft → Collect → Discuss → Closed. A facilitator can step back too, from Discuss to Collect or from Collect to Draft. Close check is separate and confirmed: it freezes the results and destroys the run's anonymity key, so alias and anonymous answers can never be re-linked. A closed run cannot be reopened.
  7. Read the results - per-dimension averages, a distribution chart for the selected dimension, and a radar once three dimensions have an average. Discuss reveals every dimension regardless of the floor. On a closed run, Generate summary writes an AI summary of the themes in the comments and saves it, so everyone after that reads the same one.
  8. Turn a result straight into an action from the run page (title, owner, due date); it also lands on Team health → Improvement actions for that team.

Worked example

Marta runs a Pulse 5 check for Northlake's 5-person Platform team, anonymous, no auto-close date. Within two days, 4 of 5 have submitted. She moves the run into Discuss, puts Workload - the lowest-scoring dimension - on stage, gives the team two minutes to talk about it, then closes the run and generates the summary, which flags repeated mentions of on-call load in the comments. She creates an action: "Rebalance Platform's on-call rotation," owner Marta, due in a week.