Improve with insights
Echoes mission is to help engineering leaders lift their teams to their full potential. To do so, Echoes automatically identifies opportunities for improvements, and issues that are holding your teams back.
Echoes goes beyond measuring and reporting engineering metrics for your own interpretation: it acts as your engineering leader's copilot by surfacing the right information at the right time. For example, Echoes may identify that:
- A team’s lead time is higher than the rest of the organization.
- A team seems to be dependent on another one for code reviews.
- Some of your coworkers has been working a lot over these last weeks.
… and many more.
Insights is an early release, and we have ambitious plans to enrich the catalog of insights in the upcoming months, in no small part based on your feedback! Don't hesitate to share them with us ([email protected]), or to let us know what you think via the feedback module in Echoes.
Insights are distributed across the three components of engineering success:
- Alignment: insights related to the team's alignment to business objectives, or its ability to deliver the most impact. These insights typically leverage categorized engineering activity.
- Delivery: insights related to the team’s delivery performance. This category is typically based on performance metrics.
- Health: insights related to a team's context and its conditions to thrive.
A history page is also available in order to retrace the different signals that has been pushed to the organisation, and remind what actions had been taken.
Echoes leverages the teams configuration to present insights to the manager closest to the finding. As a result, you are presented with the insights of your team, and any other teams under your direct responsibility.
The insights that you see in Echoes are the identified risks and opportunities that you are expected to act on.
Insights are computed based on live data, therefore many of them are time-sensitive and may lose relevance over time. For that reason, Echoes will consider an insight open for several weeks as stale and automatically mark it as expired.
Opening an insight provides with all the information you need to make a decision based on this finding.
The insight is pinned to your Echoes home for reference until a resolution is reached.
The insight is marked as resolved and disappears. You can find this insight in the "Insights history" page and see its resolution timeline.
The insight is marked as dismissed and disappears. Echoes will ask for additional details regarding the reason for dismissal, and allow you to dismiss for 1, 2, 4 weeks, or forever. Echoes will not surface that same insight for the selected period of time.
Echoes may surface an insight which doesn't apply to your particular context. For example it is possible that cross-team code reviews are something your organization encourages, or something that is expected due to the nature of your team. In that case, the insight should be dismissed forever with the corresponding reasoning.
Do you have a proposal for an insight?
Do you have an idea for an insight that you would like to see implemented? Use this form to suggest it to the team, and we'll make sure to consider it.