Measure and communicate the success of your engineering organization. Shine a lights on engineers work, and create the best conditions for your teams to thrive.
Hi PH! We’re very excited to show the v2 of our product today 🤗
Echoes helps engineering leaders measure and communicate their organization’s success.
How to even define engineering success, you may think? Good question! Echoes provides a universal framing, and the tools to specialize it for any particular organization. It defines success as three components:
🎯 Alignment: are we putting our efforts in the right places? Echoes lets you manage the categories of work that matter to your organization, such as the split between bugs / features / maintenance, or your company objectives. Echoes then gives a seamless way for builders to tag their day-to-day work directly from within their development tools of choice (e.g., GitHub, GitLab, Linear, JIRA, Shortcut). It doesn’t even require teams to adopt the same processes and tools, which makes it the most flexible, scalable, and developer-friendly way to measure the allocation of engineering efforts.
⚡️ Delivery: are we delivering software efficiently? Echoes measures delivery performance using the industry-standard DORA metrics (lead time, deployment frequency, mean time to restore, change failure rate) over time and on a team-per-team basis.
❤️ Health: are we creating a context favorable to durable success? Echoes collects qualitative data which engineers can add during the development flow, for example how a code change was made more difficult than it should have been due to unclear requirements, or a high level of technical debt. This helps puts quantitative metrics into context, and gives managers the data to support their teams in the best possible way.
What makes us different than other engineering metrics products? A good question again! We believe that the “software development as a factory” analogy, in which success is reduced to productivity, is outdated and detrimental to the builders. Our goal is to shift the focus away from the developers’ productivity and to the organization’s collective ability to succeed, because velocity only matters when you’re headed in the right direction. We’re putting our experiences building widely-adopted developer tools and managing large engineering groups in solving this problem.
Where do I sign up? Well good news, everyone! This launch introduces a new pricing model, with per-team pricing and an unlimited free plan for a single team. Give us a try and let us know what you think!
@kevin_piacentini Thank you Kevin! DORA metrics are a must, but I'd argue that allocation and general sentiment of the team is sometime as much, if not _more_ important. DORA metrics are particularly helpful when catching-up on best practices, but not as useful once you are part of the top performers. At that point, delivery performance might not be as important as working on the right things, sustainably.
@igorpavlov Thank you Igor! It is primarily used for software engineering teams, because we expect a significant portion of the work to happen in git (GitHub or GitLab).
Echoes HQ