EnglishENPolskiPLDeutschDEEspañolESBahasa IndonesiaID
Start free
Documentation

Run your first team health check

View as Markdown
Ask AI

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. Expand Team health and choose Health checks. On a phone, use Menu → Team health → Health checks.
  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 is optional. Open & notify creates the check and notifies the roster; Save draft keeps it unopened. The check stays open until you close it.
  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 room's toolbar: the "here" count opens Manage participants, which invites someone from another team or removes a person, which also deletes their answers. An anonymous run withholds names, so it reports how many have answered, not who.
  5. Discuss opens on the Overview: the radar, the lowest dimension, the most divided one and the biggest change since the last check. The agenda beside it lists every dimension, lowest first. The facilitator walks it with the one button at the bottom right of the stage ("Start with ...", "Next: ...", "Wrap up") or the arrow keys, and can start a shared countdown timer of 1, 2, 3, 5, 10 or 15 minutes from the toolbar. Everyone else follows the facilitator's step.
  6. Move the run on with that same button - Draft → Collect → Discuss → Closed. The "..." menu steps back (Discuss to Collect, Collect to Draft) or closes early. Close check, at Wrap up, asks "Close for everyone?" first: it freezes the results and destroys the run's anonymity key, so the account-to-answer link cannot be restored. A free-text answer may still identify someone from what they wrote. A closed run cannot be reopened.
  7. Read the results - per-dimension averages, a distribution chart for each dimension, and a radar once three dimensions have an average. Discuss reveals every dimension regardless of the floor. On a closed run, anyone can open any dimension from the agenda, and 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 with Add action on the dimension (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. Within two days, 4 of 5 have submitted. She moves the run into Discuss, starts with Workload - the lowest-scoring dimension, first on the agenda - gives the team two minutes to talk about it, walks the rest, then closes the run at Wrap up 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.