Product Team Health Diagnostic

When to Use

Use this skill when you are:

• New to a leadership role — need a structured baseline assessment of product team health before making changes
• Responding to CEO/board concerns — told teams are "too slow" or "not innovative" and need to diagnose root causes
• Running an org health review — periodic check on whether teams are operating in a strong or weak product model
• Preparing a remediation plan — need to prioritize which problems to fix first and justify the investment
• Onboarding a coach or consultant — need a common diagnostic language to align on what's broken

Preconditions: you have at least one of:

• Direct observations of team behaviors over at least a few weeks
• A written description of how teams operate (processes, rituals, structure)
• Interview notes or survey data from team members
• Access to team artifacts (roadmaps, sprint boards, release logs, design files)

Agent: Clarify the scope before beginning — are you assessing one team, a portfolio of teams, or the entire engineering/product organization? The scoring applies per team; an org-level report aggregates across teams.