Click the diagram to open the interactive DA Browser, where you can learn more about the decision points and options of this goal.
Why This is Important
There are several reasons why this goal is important:
- Metrics should be driven by context, not by mandate. Every team has unique outcomes and improvement goals to measure. This observation is the critical driver for context-based metrics strategies such as objectives and key results (OKR) and goal question metrics (GQM). Where these strategies walk you through how to take a contextualized approach to measurement, they don’t go that final step to help you to select metrics that are right for you.
- There are many things you could measure, but only a few things you need to measure right now. This is why an outcome/goal driven approach is critical – you want to focus on collecting the metrics that will provide insights into the decisions you need to make.
- Process improvement requires contextualized measurement. With validated learning strategies such as Guided Continuous Improvement (GCI), part of running an improvement experiment is to assess the effectiveness of the new way of working (WoW), and to do that you need to measure what you’re hoping to affect.
- Effective governance requires contextualized measurement. You need to provide visibility to whomever is governing you, thereby providing them the information that they need to govern well. An important aspect of that visibility is access to metrics, ideally in real-time.
- The measurements take for a team should be driven by the outcomes or improvement goals they are trying to achieve.
- Every team is unique, therefore each will potentially collect and report a unique set of metrics.
- Your metrics strategy must evolve over time as your situation evolves.