Echoes connects day-to-day product development work to your company's strategy and goals. Echoes helps you define the outcomes and initiatives you are pursuing as an organization, and integrates with your existing product development tools to help you seamlessly connect work to purpose. Echoes collects these inputs to give you insights into your organization's value creation pipeline.
Echoes requires an integration to a source control manager ( or ), and can optionally integrate with a ticketing or project management platform (, , or ). Each integration leverages the target platform's features to create the best possible user experience.
Connecting efforts to purpose starts by defining what you are working towards as an organization: in Echoes terminology these are and . Echoes comes with a default set of outcomes applicable to most product engineering organization but specific to none.
Echoes configuration is published through integrations to your product development tools of choice. From there, teams will be able to seamlessly connect they day-to-day efforts to purpose.
Help with the initial configuration
We have worked with a companies of all types and sizes, and we'd be happy to advise you on the setup which could work best for your particular context. For more general advice:
- Keep it simple. A synthetic report on key goals is often better than being drown in details.
- Don't aim for perfection. Echoes configuration is meant to be dynamic: it's perfectly fine to start with the default set of outcomes and to iterate as you progress in clarifying your goals.
- Read our configuration guides. They contain useful resources for using Echoes with popular methodologies.
Echoes publishes the outcomes and initiatives you configure to its integrations, leveraging each platform's specific features to make the task of connecting efforts to purpose as seasmless as possible. Take a moment to realize how powerful that is:
- Echoes guarantees consistency with its configuration. Your product development tools have a representation of the outcomes and initiatives that matter to your organization at every point in time. Echoes constantly looks for discrepancies to eliminate, and changes to its configuration are immediately propagated.
- Echoes guarantees consistency across your entire product development toolchain. Whether one team chooses to operate with JIRA, a second with Linear, and a third with GitHub issues doesn't matter anymore. Echoes will ensure that efforts, regardless of where they originate and how they are described, are homogeneously linked to centrally defined company goals.
Echoes most often relies on a platform's labeling feature by automating the creation of labels to match its configuration. For GitHub and GitLab, Echoes takes its data from labels applied to merged pull requests (GitHub) or merge requests (GitLab).
Connecting efforts to purpose using the platform's native labeling feature takes seconds. Nevertheless, Echoes always strive to automate what can be and eliminate unnecessary inputs. For example, Echoes automatically follows linked issues to infer the intent. Read about our to get more details on what each can do.
Echoes collects signals from the product development tools on which it is installed in realtime. The reports are populated as pull requests get merged and issues get resolved.
- Reports are centered on teams rather than individuals. Echoes holds its own configuration of the organization, which can be optionally imported from file descriptions or an HR information system.
- Echoes reports the reality of the work. By instrumenting your product development toolchain, Echoes acts as your field-level sensor of the activity. It helps understand in which direction the team is headed, giving you an opportunity to course correct when execution doesn't match the expectations.
- Echoes helps you communicate on the activity, including to non-technical stakeholders. Outcomes and initiatives are the universal language for the company, and Echoes reports are deliberately devoid of engineering jargon.