Alignment

alignment is about putting our engineering efforts in the right places this is arguably the most important aspect of engineering success in the current era work in the post covid world is distributed, and engineers have come to expect a higher degree of autonomy resources are scarce and the ability to hire are limited when the economic context is less favorable separate product and engineering functions is the de facto standard for modern organizations, and that collaboration is key to success it is more important than ever for engineering leaders to measure and demonstrate that progress is being made in the right direction evaluating alignment echoes helps you evaluate engineering alignment by measuring how efforts are distributed across categories of your choosing define your buckets of work the combination of categories docid\ v vyntdrcapwmderrjlui and initiatives docid\ auolbydwwbaqfuxrazrpx lets you define the areas of work relevant to your particular context this taxonomy is the cornerstone of data aggregation and reporting it is designed to evolve over time, as some categories of work become obsolete and new ones appear for example categorize engineering efforts across the business goals they contribute to categorize engineering efforts going toward new features versus bug fixing categorize engineering efforts across user personas, business lines, or countries they intend to serve identify engineering efforts specifically invested into a project to decommission a legacy platform tag day to day engineering work the taxonomy is automatically published and kept in sync with your production development tools through 🔌 integrations docid\ flrfioflhvgc98hluhupf this enables a consistent way of labeling efforts regardless of how different teams have chosen to operate, all from within your product development tools of choice for example, one team may be rigorous in its use of jira to track development tickets, while another uses ad hoc github issues to track a subset of their work echoes taxonomy is published to both jira (as a custom field) and github (as repository labels) such that work gets tagged consistently while teams continue using the processes and tools that make them most productive echoes establishes a contract in which work must be tagged following the centrally defined taxonomy, but leaves the “how” at the discretion of the teams