Many solutions capture work where it's described, for example in a ticketing system, rather than where it happens. The result is both partial (not all work is tracked in these systems) and biased (tickets tend to capture the plan rather than the work actually being done).

By measuring work where it happens, Echoes provides feedback from the field and allows you to compare plans to reality. Getting a realtime view of your team's current direction is crucial to make decisions and to communicate effectively.

We started Echoes with a mission of empowering developers everywhere. This mission is what drives our passion for organizations and leadership, and what got us to work in the past on products developers love such as Docker.

Echoes shines a light on the engineers work, surfaces the reality of their day-to-day, and helps management create a context where they can deliver their best work. The reports are centered on teams rather than individuals, and on outcomes over outputs. It shifts focus away from local efficiency (individual developer productivity) to the bigger goal: the organization's collective ability to succeed.

We take security at heart and strive to collect no more data than strictly needed. In particular, Echoes does not require access to your codebase.

When used with GitHub, Echoes is restricted to metadata (e.g., title and bodies of pull requests, labels, commit messages). It cannot clone repositories, examine filenames, nor look at the changes within a particular commit.