Your question is Measure Team Health at Asana. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
Asana's Product Analytics team has grown from 12 to 28 people in the last 9 months. The VP of Data says delivery output is still high, but managers report rising burnout risk, slower onboarding, and more unplanned work. Leadership wants a clear, repeatable way to measure whether the team is healthy.
In the last quarter, the team shipped 31 projects vs. 29 in the prior quarter, but average weekly after-hours Slack messages rose from 180 to 340, voluntary attrition increased from 4% to 9%, and employee pulse survey favorability fell from 78% to 69%. Average project cycle time increased from 18 to 24 days, while sprint spillover rose from 12% to 21%. The Head of Analytics asks you to define a small set of KPIs that captures team health without over-indexing on output alone.
employee_pulse_surveys: employee_id, survey_date, engagement_score, manager_support_score, workload_score, free_text_themehr_roster: employee_id, team, level, manager_id, start_date, termination_date, termination_typeproject_delivery: project_id, owner_id, team, created_date, shipped_date, planned_ship_date, spillover_flagslack_activity: employee_id, message_timestamp, channel_type, is_after_hourspto_and_hours: employee_id, week_start, pto_days_taken, estimated_hours_worked, oncall_flag