Dashboards & Business Analytics

Chapter 6
Measures, KPIs and Performance Management

Certificate in Business Intelligence (Power Bi)
Dashboards & Business Analytics   •   Certificate

Measures, KPIs and Performance Management

Introduction

Business intelligence becomes useful when data is converted into evidence about performance and action. A dashboard may contain attractive charts, but its value depends on whether the underlying measures are valid, consistently defined, timely, and connected to decisions. Measures quantify an aspect of activity; key performance indicators (KPIs) identify measures that are especially important to strategic or operational success.

In Power BI, a measure is normally a reusable calculation evaluated in the current filter context. A KPI is not simply any number displayed with a colour. It combines a meaningful measure with a target, a comparison basis, a time horizon, and an interpretation of performance. Effective performance management therefore requires more than technical dashboard construction. It requires agreement about what success means, how it will be measured, and who is accountable for improvement.

This chapter examines reliable measures, targets, benchmarks, thresholds, leading and lagging indicators, SMART criteria, the Balanced Scorecard, and performance hierarchies. It also applies these ideas to a practical Power BI scenario.

Learning Objectives

By the end of this chapter, you should be able to:

  1. Distinguish measures, metrics, indicators, KPIs, targets, benchmarks, and thresholds.
  2. Define reliable measures and select suitable aggregation methods.
  3. Calculate and interpret common business measures responsibly.
  4. Distinguish leading indicators from lagging indicators.
  5. Evaluate KPIs using SMART criteria and Balanced Scorecard perspectives.
  6. Organize measures through organizational and performance hierarchies.
  7. Design practical KPI logic for Power BI dashboards.
  8. Recognize limitations, ethical risks, and governance requirements in performance reporting.

1. Measures, Metrics and KPIs

A measure is a quantified attribute of an event, object, or process. Examples include units sold, delivery time, revenue, defect count, and employee absence hours. A measure may be a raw count or a calculated value.

A metric is a measurement used to monitor or evaluate a condition. In everyday business language, “measure” and “metric” are often interchangeable, although a metric usually implies an intended use for comparison or management.

An indicator provides evidence about a condition or trend. It may be quantitative, qualitative, or categorical. A traffic-light status is an indicator, but it is meaningful only when the underlying rule is defined.

A key performance indicator is a limited, decision-relevant indicator linked to an important objective. The word “key” is essential. An organization that labels every available measure a KPI creates a crowded dashboard in which priorities are unclear.

A useful distinction is:

ConceptMeaningExample
MeasureQuantified attributeNumber of orders
MetricMeasure used for monitoringOrders per sales representative
IndicatorEvidence of a conditionOn-time delivery status
KPICritical indicator linked to an objectiveOn-time delivery rate against a 95% target
TargetDesired level by a specified timeAchieve 95% by quarter-end
BenchmarkReference point for comparisonIndustry median of 92%
ThresholdBoundary that triggers interpretation or actionEscalate when below 90%

A KPI should answer five questions: What is being measured? Why does it matter? Compared with what? Over what period? What action follows from the result?

2. Designing Reliable Measures

A reliable measure is not merely one that can be calculated. It must represent the intended concept consistently and transparently. Measure design should address the following dimensions.

2.1 Construct validity

The measure should represent the business concept it claims to represent. Revenue may be a reasonable measure of sales value, but it is not automatically a measure of profitability, customer loyalty, or sales quality. Using revenue as a proxy for customer success may encourage excessive discounting or unprofitable sales.

2.2 Operational definition

Every measure requires a precise definition. For example, “active customer” could mean a customer with a purchase in the last 30, 60, or 90 days. A documented definition should specify inclusion rules, exclusion rules, time zone, currency, treatment of cancellations, and source system.

2.3 Numerator and denominator

Rates and percentages are particularly vulnerable to ambiguity. A general rate is calculated as:

Rate = Numerator ÷ Denominator

The numerator must be a subset of the denominator when the measure is a proportion. For example, if 9,500 of 10,000 deliveries were on time, the on-time delivery rate is:

9,500 ÷ 10,000 = 0.95 = 95%

The units cancel, leaving a dimensionless proportion. The result is valid only if both values refer to the same population, period, and business rules.

2.4 Aggregation method

Different measures require different aggregation methods. Additive measures such as sales value can usually be summed across products and periods. Semi-additive measures such as account balance can be summed across accounts but should generally not be summed across time. Non-additive measures such as percentages should usually be recalculated from their components rather than averaged blindly.

For a weighted rate:

Overall Rate = ∑Numeratorᵢ ÷ ∑Denominatorᵢ

This differs from the simple average of subgroup rates unless all subgroup denominators are equal. Suppose Region A has 90 on-time deliveries from 100, and Region B has 9 on-time deliveries from 10. The correct overall rate is:

(90 + 9) ÷ (100 + 10) = 99 ÷ 110 = 90%

The average of 90% and 90% is also 90% in this example, but if Region B had 8 on-time deliveries, the overall rate would be 98 ÷ 110 ≈ 89.1%, not the simple average of 89% and 90% if the subgroup sizes differed.

2.5 Timeliness and completeness

A measure can be accurate but too late to support action. A daily inventory measure is less useful if updated monthly. Completeness is also important: missing transactions may make performance appear better or worse than it is. Dashboards should expose data freshness, coverage, and known exclusions.

2.6 Reproducibility and reconciliation

A measure should produce the same result when the same data and filters are used. Totals should reconcile with authoritative financial or operational systems. Differences between a Power BI measure and a source-system report should be explainable rather than dismissed as technical variation.

3. Targets, Benchmarks and Thresholds

A target is a desired level of performance. It should include a measure, value, period, population, and owner. “Improve service” is not a target; “achieve an on-time delivery rate of at least 95% for domestic orders by 30 June” is more actionable.

A benchmark is a reference value. Common types include:

  • Historical benchmark: comparison with the organization’s previous period.
  • Internal benchmark: comparison with another branch, team, or product.
  • External benchmark: comparison with an industry or professional standard.
  • Best-practice benchmark: comparison with a recognized high-performing process.

Benchmarks require caution. Different organizations may use different definitions, customer segments, accounting policies, or operating environments. A direct comparison can be misleading unless the populations and definitions are comparable.

A threshold is a boundary used to classify or trigger action. For example, an organization might define on-time delivery as green at ≥95%, amber at 90%–94.99%, and red below 90%. Thresholds should be documented, reviewed, and linked to actions. Colour without action is decoration rather than management.

Targets should be challenging but credible. An arbitrary target can generate dysfunctional behaviour: employees may delay recording bad news, reject difficult customers, or focus on easily improved numbers while neglecting important outcomes.

4. Leading and Lagging Indicators

A lagging indicator records an outcome after an activity has occurred. Examples include quarterly profit, customer churn, completed sales, accident frequency, and annual employee turnover. Lagging indicators are important because they show whether results were achieved, but they often provide limited time for corrective action.

A leading indicator provides information about activities or conditions likely to influence future outcomes. Examples include sales opportunities in qualified stages, staff training completion, preventive maintenance completion, response time to complaints, and website conversion activity.

The distinction is relative rather than absolute. A measure may be leading for one outcome and lagging for another. Training completion is leading for employee capability, but it may be lagging relative to the decision to schedule training.

A balanced performance system combines both types. Leading indicators should have a plausible causal connection to outcomes, not merely a convenient association. For example, the number of sales calls may be a poor leading indicator if calls are low quality. Measures of activity should be combined with measures of effectiveness.

A practical chain is:

Resources → Activities → Outputs → Outcomes → Strategic impact

Training resources enable training activities; activities produce trained employees; trained employees may improve service quality; improved service may increase retention and profitability. The farther a measure is from the activity, the more it may function as a lagging outcome indicator.

5. SMART KPIs

The SMART framework helps convert broad intentions into operational KPIs:

  • Specific: identifies exactly what is measured.
  • Measurable: uses observable data and a defined calculation.
  • Achievable: is feasible given resources and constraints.
  • Relevant: supports a meaningful organizational objective.
  • Time-bound: specifies a period or deadline.

SMART criteria improve clarity but do not guarantee strategic value. A KPI can be specific and measurable yet irrelevant. For instance, “process 1,000 emails per day” may be SMART but harmful if the objective is to resolve customer problems effectively.

A useful KPI specification includes:

FieldExample
ObjectiveImprove delivery reliability
KPI nameOn-time delivery rate
DefinitionDeliveries completed by promised date ÷ completed deliveries
UnitPercentage
FrequencyDaily, with weekly review
TargetAt least 95%
ThresholdsGreen ≥95%; amber 90%–94.99%; red <90%
OwnerDistribution manager
Data sourceTransport management system
ExclusionsCancelled orders and customer-requested date changes
ActionInvestigate red status by depot and carrier

6. Balanced Scorecard Perspectives

The Balanced Scorecard, associated with Kaplan and Norton, organizes strategic performance across four perspectives:

  1. Financial: How do owners or funders view performance? Measures may include operating margin, cash conversion, revenue growth, or return on capital.
  2. Customer: How do customers experience the organization? Measures may include satisfaction, retention, complaints, service reliability, and customer lifetime value.
  3. Internal process: Which processes must perform well? Measures may include cycle time, first-pass yield, defect rate, and order accuracy.
  4. Learning and growth: How does the organization sustain future capability? Measures may include employee capability, training completion, innovation activity, and system reliability.

The perspectives should not be treated as four unrelated scorecards. A strategy map often expresses hypothesized relationships: learning and growth support better internal processes; better processes improve customer outcomes; customer outcomes contribute to financial results. These relationships are strategic assumptions that should be tested rather than accepted automatically.

A Balanced Scorecard also reduces the risk of financial short-termism. However, adding four categories does not automatically create balance. An organization can still overload the scorecard, select poor measures, or ignore environmental and social responsibilities. Additional perspectives may be appropriate where material to the mission.

7. Performance Hierarchies and Drill-Down Design

Performance hierarchies organize measures from strategic outcomes to operational drivers. A hierarchy can be vertical, such as enterprise → division → region → branch → team, or causal, such as profit → revenue and cost → price, volume, mix, labour, and overhead drivers.

A well-designed Power BI report commonly contains:

  • Executive layer: a small number of strategic KPIs and exceptions.
  • Management layer: trends, targets, variance analysis, and comparisons.
  • Operational layer: transaction-level details, queues, and assigned actions.

Drill-down should preserve meaning. A regional on-time rate should be decomposable into branches using the same numerator and denominator rules. A KPI should not change definition merely because a user moves from the executive page to an operational page.

Common variance measures include absolute variance and percentage variance:

Absolute Variance = Actual − Target
Percentage Variance = (Actual − Target) ÷ Target × 100%

These formulas assume that the target is non-zero and that actual and target have compatible units. For measures where a lower value is better, such as complaint resolution time, a negative variance may indicate favourable performance. Therefore, the dashboard must define whether “favourable” means above or below target.

In Power BI, DAX measures should generally be created rather than calculated columns when the result must respond to filters. Conceptually, a measure may be defined as:

Total Sales = SUM(Sales[SalesAmount])

A rate should usually be calculated from components:

On-Time Rate = DIVIDE([On-Time Deliveries], [Completed Deliveries])

DIVIDE is preferable to direct division because it can handle a zero or blank denominator through an explicit alternate result. The model should use a proper date table, controlled relationships, consistent data types, and a documented semantic layer.

8. Worked Example: Evaluating a Service KPI

A service centre completed 2,400 cases in April. Of these, 2,232 met the service-level agreement. The target is 95%.

The rate is:

2,232 ÷ 2,400 = 0.93 = 93%

The absolute variance expressed in percentage points is:

93% − 95% = −2 percentage points

The relative percentage variance is:

(93% − 95%) ÷ 95% × 100% ≈ −2.1%

These are different statements. The centre is two percentage points below target, which is approximately 2.1% below the target value. If the threshold for escalation is below 94%, the result should be classified as red or amber according to the organization’s policy. Further analysis might segment the result by channel, case type, shift, or agent tenure. Segmentation should support diagnosis, not encourage unfair comparison where case complexity differs substantially.

9. Illustrative Case: Northstar Retail Distribution

Background

Northstar Retail Distribution supplies consumer goods to 180 stores. Its executive dashboard previously displayed sales, delivery volume, warehouse activity, and customer complaints. Managers disagreed about definitions, and the dashboard showed green status even when customers reported repeated late deliveries.

Problem

The organization had three problems. First, “on-time delivery” included orders whose promised dates had been changed after dispatch. Second, the dashboard averaged depot percentages without considering different shipment volumes. Third, the organization tracked completed deliveries but not leading indicators such as picking accuracy and carrier capacity.

Analysis

A cross-functional team documented the KPI definition. The numerator became deliveries completed by the original confirmed promised date. The denominator became all completed, non-cancelled deliveries with a valid promise date. Customer-requested date changes were reported separately rather than silently excluded.

The team designed a KPI hierarchy:

  • Strategic outcome: customer retention and distribution cost.
  • Customer KPI: on-time delivery rate and complaint rate.
  • Process KPIs: pick accuracy, dispatch cycle time, and carrier capacity utilization.
  • Leading indicators: open exception orders, unstaffed delivery routes, and overdue replenishment tasks.

The overall rate was calculated from total on-time deliveries divided by total eligible deliveries, rather than by averaging depot rates. Targets were set by customer segment because retail stores with different delivery windows had different operational conditions.

Power BI approach

The semantic model included a delivery fact table, date dimension, depot dimension, carrier dimension, customer dimension, and a target table. Measures were named consistently and accompanied by descriptions. A KPI page displayed actual, target, variance, trend, last refresh time, and status. A drill-through page showed late deliveries by reason code and accountable owner.

Row-level security restricted depot managers to their own operational data, while executives could view the consolidated organization. Data-quality flags identified missing promise dates and duplicate delivery identifiers.

Outcome

After two reporting cycles, managers found that late deliveries were concentrated in two carriers and one product category requiring special handling. The organization improved carrier scheduling and revised the special-handling process. The dashboard did not itself cause the improvement; its value came from a shared definition, accountable ownership, and a clear action process.

Learning points

  1. A KPI must be governed as a business definition, not merely coded as a visual.
  2. Aggregation choices can materially change reported performance.
  3. Leading indicators help managers act before lagging outcomes deteriorate.
  4. Exception-focused drill-down is more useful than displaying every available metric.
  5. Data quality and security are part of performance management.

10. Challenges, Ethics and Governance

Goodhart’s law and gaming

When a measure becomes a target, people may optimize the measure rather than the underlying objective. A call centre that rewards short call duration may increase premature call termination. Controls include complementary quality measures, periodic review, and attention to unintended consequences.

Correlation and causation

A leading indicator may correlate with an outcome without causing it. Management should avoid claiming that an activity caused improvement unless the evidence supports that conclusion. A dashboard is primarily a monitoring tool, not automatically a causal research design.

Fairness and comparability

Comparing teams without adjusting for workload, customer complexity, geography, or resources can produce unfair conclusions. Performance dashboards should distinguish controllable from uncontrollable factors and provide context alongside rankings.

Privacy and access

Employee-level KPIs can become surveillance systems. Access should follow legitimate business need, data minimization, and applicable privacy law. Sensitive information should not be displayed merely because it is technically available. Row-level security, role design, audit logs, and retention rules are essential controls.

Data governance

A KPI catalogue should record definitions, owners, sources, refresh frequency, calculation logic, targets, thresholds, and change history. Changes to definitions should be versioned so that trends remain interpretable. Source lineage allows users to understand where a number originated and how it was transformed.

11. Contemporary Developments and Best Practice

Modern BI platforms increasingly provide anomaly detection, natural-language querying, forecasting, and AI-generated summaries. These capabilities can help identify unusual changes, but they do not replace KPI governance. AI may misinterpret a business definition, infer causation incorrectly, or expose sensitive information. Human review, documented assumptions, and access controls remain necessary.

Best practice is to:

  • Begin with strategic and operational decisions, not available data.
  • Define each KPI in business language before implementing it in DAX.
  • Use a small, balanced set of outcome and driver indicators.
  • Recalculate rates from components where possible.
  • Display targets, benchmarks, thresholds, trend, and data freshness together.
  • Make status rules explicit and accessible.
  • Test measures against known cases and reconcile them to source systems.
  • Provide drill-down that supports diagnosis and action.
  • Assign owners and review KPI usefulness periodically.
  • Monitor unintended consequences, fairness, privacy, and security.

Chapter Summary

Measures quantify business attributes, while KPIs are selected measures linked to important objectives and decisions. Reliable measures require valid concepts, precise operational definitions, appropriate aggregation, complete and timely data, reproducibility, and reconciliation. Targets state desired performance; benchmarks provide comparison points; thresholds classify results and trigger action.

Leading indicators provide information about drivers and future outcomes, whereas lagging indicators report completed results. Effective performance management uses both. SMART criteria improve KPI clarity, while the Balanced Scorecard encourages attention to financial, customer, internal-process, and learning-and-growth perspectives. Performance hierarchies connect strategic outcomes to operational drivers and enable meaningful Power BI drill-down.

A professional dashboard is therefore a governed performance system rather than a collection of charts. Its success depends on definitions, data quality, accountability, ethical use, and the organization’s willingness to act on evidence.

Key Terms

Measure: A quantified attribute of an event, object, or process.

Metric: A measure used for monitoring or evaluation.

Indicator: Evidence about a condition, status, or trend.

Key performance indicator (KPI): A decision-relevant indicator linked to an important objective.

Target: A desired level of performance for a specified period.

Benchmark: A reference value used for comparison.

Threshold: A boundary that classifies performance or triggers action.

Operational definition: A precise specification of how a concept is measured.

Leading indicator: A measure that provides information about likely future performance.

Lagging indicator: A measure that records an outcome after activity has occurred.

SMART: Specific, Measurable, Achievable, Relevant, and Time-bound.

Balanced Scorecard: A framework organizing performance across financial, customer, internal-process, and learning-and-growth perspectives.

Variance: The difference between actual performance and a target or comparison value.

Semantic model: The governed data model containing business entities, relationships, measures, and definitions.

Filter context: The set of filters under which a Power BI measure is evaluated.

Data lineage: The documented path from an output back to its source and transformations.

Row-level security: Access control that limits users to permitted rows of data.

Goodhart’s law: The principle that a measure may become a poor measure when used as a target.

Review Questions

Short Answer Questions

  1. What is the difference between a measure and a KPI?
  2. Why should percentages generally be recalculated from their numerator and denominator?
  3. Define a leading indicator and give one example.
  4. What are the four traditional Balanced Scorecard perspectives?
  5. Why are thresholds useful in a performance dashboard?

Long Answer Questions

  1. Explain the characteristics of a reliable business measure and illustrate each with an example.
  2. Discuss the differences among targets, benchmarks, and thresholds, including risks associated with poor design.
  3. Explain how SMART criteria can improve KPI specifications while still failing to guarantee strategic relevance.
  4. Describe how a Power BI performance hierarchy can connect executive reporting with operational action.
  5. Evaluate the benefits and limitations of combining leading and lagging indicators.

Analytical / Application Questions

  1. A company reports an average on-time delivery rate of 94% across three depots. Explain what additional data is needed to determine whether the reported average is correctly calculated.
  2. Design a SMART KPI for customer complaint resolution. Include its definition, target, threshold, owner, frequency, and likely leading indicators.
  3. A sales team increases the number of calls per employee, but customer retention declines. Use Goodhart’s law and the leading/lagging indicator distinction to diagnose the problem and recommend a revised KPI set.

Multiple Choice Questions with Answers

Question 1

Which statement best describes a key performance indicator?

A. Any number available in a database

B. A decision-relevant measure linked to an important objective

C. A colour used on a dashboard

D. A target without a defined measure

Correct Answer: B. A decision-relevant measure linked to an important objective

Question 2

A delivery operation completes 950 on-time deliveries out of 1,000 eligible deliveries. What is the on-time delivery rate?

A. 90%

B. 92.5%

C. 95%

D. 105%

Correct Answer: C. 95%

Question 3

Why is a weighted overall rate usually preferable to a simple average of subgroup rates?

A. It ignores subgroup volumes

B. It uses the combined numerators and denominators

C. It always produces a higher result

D. It removes the need for a target

Correct Answer: B. It uses the combined numerators and denominators

Question 4

Which is most likely to be a leading indicator of future employee performance?

A. Annual profit

B. Completed customer complaints

C. Training completion

D. Year-end turnover

Correct Answer: C. Training completion

Question 5

Which Balanced Scorecard perspective includes cycle time and defect rate?

A. Financial

B. Customer

C. Internal process

D. Learning and growth

Correct Answer: C. Internal process

Question 6

A target is 95% and actual performance is 92%. What is the absolute variance in percentage points?

A. −3 percentage points

B. −3.2 percentage points

C. 3 percentage points

D. 3.2 percentage points

Correct Answer: A. −3 percentage points

Question 7

Which practice best supports KPI reliability in Power BI?

A. Averaging all displayed percentages regardless of volume

B. Changing definitions for each report page

C. Documenting definitions and calculating rates from components

D. Removing data-quality warnings

Correct Answer: C. Documenting definitions and calculating rates from components

Question 8

What is the main purpose of a performance threshold?

A. To replace the KPI definition

B. To classify performance or trigger an action

C. To guarantee causation

D. To eliminate the need for targets

Correct Answer: B. To classify performance or trigger an action

Question 9

Which example best illustrates Goodhart’s law?

A. A measure is reconciled with its source system

B. A call centre improves call counts while service quality declines

C. A dashboard displays data freshness

D. A target is assigned an owner

Correct Answer: B. A call centre improves call counts while service quality declines

Question 10

Which control most directly limits a depot manager’s access to other depots’ records in Power BI?

A. A benchmark

B. A threshold

C. Row-level security

D. A lagging indicator

Correct Answer: C. Row-level security

Dashboards & Business Analytics
Chapter 6 of 14