Your question is Healthy Team vs Busy Team. 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).
Figma's collaboration product supports thousands of internal product squads that ship features every quarter. The COO wants a standard way to tell whether a team is genuinely healthy or simply generating a lot of activity without durable outcomes.
Two product teams look similar on output but different on outcomes over the last 90 days. Team Alpha shipped 28 tickets per engineer per month, held 41 meetings per person per month, and closed 96% of sprint commitments. However, employee pulse score fell from 8.1 to 6.9, regrettable attrition rose from 4% to 11% annualized, on-call incidents increased from 6 to 14 per month, and 90-day feature adoption was only 18%. Team Beta shipped 21 tickets per engineer per month and closed 88% of sprint commitments, but pulse score improved from 7.4 to 8.2, attrition stayed at 3%, incidents fell from 9 to 4, and 90-day feature adoption reached 37%. Leadership asks which signals indicate a healthy team versus a merely busy team, and what KPI framework should be used in quarterly reviews.
engineering_activity_daily: tickets created/closed, PRs merged, deploys, sprint commitmentsincident_log: severity, count, MTTR, on-call pagesemployee_pulse_surveys: weekly engagement, burnout risk, manager supporthr_roster_events: tenure, transfers, regrettable attrition, backfillsfeature_usage_90d: launches, adoption, retention, usage depth by feature/team