[quaunaut]

I love the shift in focus, specifically toward what your organizational goals are. However, it isn't clear to me where many of these metrics are coming from- are they manually input, or is it possible to connect them to a data source?

I've found that often without connecting to actual measurements, it's easy for teams to do dozens of hours of effort where a single hour of that effort achieves the majority of the effect, because when measurements aren't used directly, people will often just throw energy at the problem until it "feels" done. Sometimes this even means all that effort accomplished nothing. This is why I'm such a big fan of Impact Mapping[1].

1. Impact Mapping: https://smile.amazon.com/Impact-Mapping-Software-Products-Pr...

[icecrime]

At this point Echoes doesn't let you connect goals to actual metrics. In other words: we measures efforts invested into the goals, but not the observable impact of these efforts (yet!).

Your question is however absolutely spot on as this is where we going. But in order to measure impact we needed to start by capturing _why_ we're doing what we're doing in the first place, and what we realized is that this in itself was solving a significant pain point for engineering organizations.

I haven't read Impact Mapping, thank you for the recommendation!