Loading content
Metric hierarchies provide a clear overview of metrics, their relationships, and hierarchies within organizations. They enable efficient analysis and decision-making based on relevant data.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
A metric hierarchy connects an overarching goal to measurable outcomes, drivers, and operational signals.
Metric hierarchies grew from management and data-analysis practice, where strategic goals had to be connected to measurable outcomes and influencing factors. As KPI reporting and dashboarding spread, this became an explicit tree structure: outcome metrics are traced to operational drivers so reports can support decisions.
Picture a tree: the goal is the trunk, outcome metrics are branches, and actionable drivers are leaves. The further down the tree, the closer the metric is to a concrete action.
It shows whether a desired result was achieved, such as revenue or retention.
It describes an influencing factor a team can change through decisions or work.
Metric hierarchies help teams choose useful measures, distinguish cause from effect, and turn a report into concrete next actions.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.