The organization health report provides a synthetic evaluation of a team's context across different axes. It aims to answer the questions: do the teams have the what they need to succeed? It helps quickly identify the teams doing well and who may be able to share their learnings, and the team who might be needing support.

All data in this table is compared against the organization's average, the color intensity indicating the outliers (the values which most significantly depart from the organization's norm).

The first group of columns covers team composition, with the following metrics:

• Tenure: the average time in years for which the current members of the team have participated in that team.
• Churn: the percentage of members having left the team over the past year.

They are automatically computed from your organization's data, and don't require any particular action other than keeping the teams definitions up-to-date.

The second group of columns covers software delivery performance, with the DORA metrics:

• Lead time

• Deployment frequency

• Mean time to recovery
• Change failure rate

Their prerequisites are explained in each individual metric page.

The last group of columns covers impediments declared by the teams, categorized as:

• Dependencies: the percentage of changes made difficult by external dependencies (e.g., blocked by another change or another team).
• Knowledge gap: the percentage of changes made difficult by a lack of available knowledge (e.g., documentation, code familiarity, particular technological stack).
• Technical debt: the percentage of changes made difficult by technical debt (e.g., high coupling, lack of tests).
• Unclear requirements: the percentage of changes made difficult by a lack of clear requirements.

They are computed from the echoes/impediments labels being applied to GitHub pull requests and GitLab merge requests.