team-health

# Team Health Check > **Two lenses, always.** "Development" asks: is this person growing and performing? "Wellbeing" asks: is this person thriving, connected, and energised? Great managers hold both. A periodic overview of team dynamics, engagement signals, wellbeing, and development trajectory across all direct reports. ## When to Use - Weekly or biweekly team health review - Before calibration or planning meetings - When the manager says "how's my team doing?", "team health check", "anyone I should check in with?" - When preparing for skip-level conversations ## Instructions If any MCP connector is unavailable, follow the connector unavailability protocol in `references/operating-principles.md`. ### 1. Load Team Context Read from `manager-context/`: - `manager-profile.md`: full list of direct reports - `team/`: individual profiles with goals, projects, last review dates - `sources.md`: channels and data locations per team member If context is missing, note it and work with available sources. ### 2. Scan Per Team Member For each direct report, gather data from the last 14 days (or since last health check): **Activity & Engagement (Slack):** - Message volume in team/project channels (relative to their baseline if known) - Types of messages: asking questions, answering questions, sharing updates, celebrating, flagging issues - Channels they're active in - Any public wins or recognition received - Any public frustration or repeated blockers **1:1 Cadence (Calendar)...