Balanced Scorecard: Linking Strategy and Measures

Connect measures to a strategy

A balanced scorecard translates a strategy into a small set of objectives and measures that can be reviewed together. Its common perspectives concern financial results, customers, internal processes and the capabilities needed for improvement. The value of the tool comes from showing how these areas relate. A list of attractive metrics without an explanation of those relationships is only a dashboard.

Start with a concrete strategic choice. A service organization may want to retain customers by resolving problems accurately and promptly. That aim suggests questions about employee capability, the design of the service process, customer experience and the cost of delivering it. The scorecard should make those links visible so managers can test whether their actions support the intended outcome.

Draw a balanced scorecard strategy map

Define each objective in language that describes a result. “Train employees” is an activity; “enable staff to resolve common requests without avoidable escalation” states a capability. Explain which process that capability should improve and why customers would value the improvement. Then identify the financial or mission result the organization expects. These are hypotheses about how change will work, not facts guaranteed by placing them on a chart.

Avoid assuming every relationship is one-directional. Faster response may increase satisfaction, but speed can also reduce the quality of resolution if staff feel pressured to close cases early. Lower costs may free resources for improvement or undermine the very capability the strategy needs. Recording these trade-offs helps a scorecard serve decisions rather than endorse a preferred narrative.

Select the unit and time period for each objective. An organization-wide measure can mask different experiences across teams or customer groups; an overly narrow measure can distract from the wider strategy. Decide what can be compared fairly, what is affected by seasonal demand and when an expected result should reasonably appear. A capability investment may take longer to affect retention than a process change takes to affect queue time.

Choose measures that people can use

Give every indicator a clear definition, source, owner, reporting frequency and reason for inclusion. Specify what counts as a completed case, which customers are included and how missing data are handled. An ambiguous measure invites inconsistent reporting and argument about the numbers instead of learning from them. A target should be grounded in a baseline and operational reality, with a threshold that prompts investigation.

Combine evidence about drivers with evidence about outcomes. Training completion and system availability may be leading measures of capability; resolution quality and customer retention are later outcomes. A leading indicator is useful only if its link to the desired result remains plausible. Counting course attendance without checking what employees can do afterward is a weak proxy for capability.

Watch for incentives created by the scorecard. If managers are judged solely by average handling time, they may shorten conversations while leaving problems unresolved. Pair speed with repeat-contact rates, case quality or customer feedback. If a metric can be improved by excluding difficult work, define the denominator and inspect who is missing. The aim is to encourage the right behavior, not to maximize a convenient number.

Work through a conflicting result

Suppose a service team reduces its response time but customer retention falls. A simple scorecard might declare process success and treat retention as a separate problem. A useful one asks whether cases are actually resolved, whether a change in customer mix affected the comparison and whether staff have authority to handle complicated requests. Review complaints, repeat contacts and customer accounts alongside the time measure.

The investigation may show that automation handles routine inquiries quickly while difficult cases wait longer. Averages conceal the split. The organization could revise routing, equip staff to solve complex issues and report the two case types separately. It should then check both process quality and retention over a suitable period. The example illustrates how a scorecard tests the strategy’s causal logic instead of merely displaying a green or red result.

Data quality matters throughout. Ask how the figures were collected, whether definitions changed and whether a result is large enough to matter. When survey response rates differ across groups, a customer score may not represent the full population. A manager should state uncertainty and seek the evidence needed for a decision, rather than treating every movement as a trend.

Use review meetings to make choices

Assign an owner to each objective and a time for reviewing it. At the meeting, compare trends with the expected logic, note competing explanations and decide whether to maintain, adjust or stop an initiative. Record who will act and what evidence will be examined next. If a target is repeatedly missed, distinguish a poor strategy from weak execution or an unrealistic measure before changing the number.

Keep the scorecard limited enough for a genuine conversation. Adding every available metric makes priorities harder to see. Retire an indicator when it no longer informs decisions, but preserve enough historical definition to interpret changes over time. Review the strategy map itself when conditions change: a new customer need or technology may alter which capabilities and processes matter most.

Document decisions made at each review. A brief record of the evidence, competing explanations, chosen action and next review date helps the organization learn whether its interpretation was sound. It also prevents a changed target from concealing an unresolved performance problem.

Conclusion

A balanced scorecard works when it joins strategic objectives, credible measures and regular decisions. It should show the proposed path from capability and process to customer and financial or mission outcomes, while making room for conflicting evidence. Define measures carefully, examine the behavior they encourage and revise the strategy when the observed results challenge its assumptions.