Why composability matters
Composability gives leaders one answer to a business question, grounded in their own numbers. Instead of asking which version of a number is right, everyone works from the same definition.
- Consistency: Update a base measure once and every dependent KPI reflects the change. No more rival versions of "the truth."
- Auditability: You can trace a KPI to its ingredients and formula steps, for example "Profit Margin = (Revenue - Cost) ÷ Revenue."
- Efficiency: Reuse shared definitions to cut SQL sprawl and reduce maintenance across teams and tools.
How composability works with metrics
In a metric-centric approach, foundational metrics like "Total Revenue" or "Orders" are atomic definitions. Each lives in one governed place with a clear formula, data source, and time behaviour. New metrics are composed by referencing those building blocks rather than rewriting logic.
This layered approach reduces duplicate formulas, limits technical debt, and keeps business math transparent. When a base metric changes, every composed metric that depends on it updates automatically. The result is a consistent, auditable set of definitions that teams can reuse across dashboards, reports, and analyses.
Composability also improves collaboration. The people who know the data define the building blocks. Business users combine them to answer questions without touching SQL or wondering where a number came from.
Composability in practice
Start with atomic, governed measures:
- Base measures: "Revenue," "Cost," "Orders," "Active Customers."
- Composed metrics: Reference base measures to calculate "Average Order Value," "Return Rate," or "Profit Margin."
For example:
- Define "Revenue" and "Cost" as base measures.
- Define "Profit" as "Revenue - Cost."
- Define "Profit Margin" as "Profit ÷ Revenue."
If "Revenue" changes to exclude refunds, every dependent metric updates to match.
Pro tip
Name base metrics precisely and document their logic before creating calculated metrics. Clear names and descriptions are the fastest way to prevent formula drift.
What to consider before you adopt it
Composability works best when base definitions are agreed on first. The tradeoff is upfront effort: someone has to settle what "Revenue" or "Active Customers" means before metrics are built on top of it. A change to a base metric also flows to everything that depends on it, so review dependent metrics before you edit one.
Start with the five or six numbers your leadership team reviews most often. Write down each definition, confirm who owns it, and build other metrics from those.
Related terms
What is a metric?
A metric, in the context of analytics, is a calculated value that tracks performance for a business activity. Think of it as a consistent math formula applied to your data over time, like revenue, conversion rate, or churn rate. A metric includes a clear formula, time frame, and rules for how to slice the data. It turns raw numbers into a repeatable signal you can compare across periods, products, regions, or segments.
What is a semantic layer?
A semantic layer is the shared business vocabulary and rules that translate raw tables into consistent, human-readable metrics and dimensions. It turns questions like "What do we mean by revenue?" into reusable definitions every chart and query uses.
What is a metrics layer?
A metrics layer is a centralized abstraction layer that sits between your data warehouse and your downstream analytics tools. It lets you define business logic and KPI calculations, such as Gross Margin or Monthly Active Users, once in a single, governed location. Leaders then get the same answer no matter who asks or which tool they use.
What is a metric catalog?
A metric catalog is a centralized, governed repository of standardized business metrics and KPIs. It documents the name, calculation, and business context for every metric. With definitions in one place, Finance, Sales, and Marketing calculate progress the same way, so leaders get one answer instead of competing numbers.
What is a knowledge graph?
A knowledge graph is a structured network that represents real-world entities (people, places, products, metrics) and the relationships between them. It adds context to data, so leaders and systems can make better-grounded decisions. This entry explains how knowledge graphs work, why they matter, where they are used, and what to consider before building one.
What is data lineage?
Data lineage maps the journey of your data from origin to destination. It shows where data comes from, how it is transformed, and where it is used, so your team can trace any number in a dashboard back to its source and trust the answer before acting on it.
What is a metric tree?
A metric tree is a visual or conceptual model that maps how key business metrics relate to each other. It links a top-level outcome, like revenue or retention, to the drivers underneath that explain why it changed. You get a shared view of cause and effect, so your team can agree on what happened and what to do next.