Neither alignment nor delivery performance matter if success isn’t sustainable: this is what the health component aims to capture.

Health is about ensuring that we are creating a context for teams to deliver their best work durably.

Evaluating health

In Echoes, organization’s health encompasses multiple factors:

• Team constitution insights, as measured by the churn rate (percentage of team members having left the team in the past 12 months) and average tenure (average number of years the current members of the team have been part of it). This information is computed using the teams definitions known to Echoes.
• Qualitative insights, based on the challenges faced by the engineers during implementation. This information is collected from a set of labels which engineers can use to surface difficulties. For example, an engineer may use the GitHub label echoes/impediments: unclear-requirements on their pull request to express that the change was made more difficult than it should due to unclear requirements.