Composability

In Depth

In a metric-centric architecture, you treat foundational measures like “Total Revenue” or “Orders” as atomic definitions. Each lives in one governed place with a clear formula, data source, and time behaviour. You then compose new metrics by referencing those same building blocks rather than rewriting logic.

This layered approach reduces duplicate formulas, shrinks technical debt, and keeps business math transparent. When a base measure changes, every composed metric that depends on it updates automatically. The result is a consistent, auditable, and scalable metric layer that teams can reuse across dashboards, reports, and analyses.

Composability also improves collaboration. Analysts define the building blocks. Business users combine them safely to answer questions fast, without needing to touch SQL or remember where a number came from.

Pro Tip

Name base measures precisely and document their logic before creating calculated metrics. Clear names and descriptions are the fastest way to prevent formula drift.

Why Composability Matters

• 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.

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.”

Example:

1. Define “Revenue” and “Cost” as base measures.
2. Define “Profit” as “Revenue − Cost.”
3. Define “Profit Margin” as “Profit ÷ Revenue.”

If “Revenue” changes to exclude refunds, all dependent metrics align instantly.

Composability and PowerMetrics

PowerMetrics takes a metrics-first approach that operationalizes composability.

• Instant and Custom Metrics (Base): Create governed base measures directly from sources like spreadsheets, databases, or APIs. Each metric is a first-class object with history and consistent formatting.
• Calculated Metrics (Composed): Build new metrics by combining existing ones with formulas. Example: “Return Rate” = “Returns” ÷ “Total Sales.”
• Metric Knowledge Graph: See how metrics relate to each other. Trace dependencies from a KPI back to its base measures for clarity and trust.
• Reusability Across Dashboards: Once defined, a base metric can be reused anywhere. Teams assemble dashboards quickly without recreating logic.

This structure forms a metric-centric semantic layer that standardizes definitions, keeps lineage visible, and enables confident self-serve analysis.