The Balanced Scorecard Translating Strategy into Action

1. 1Classify the business unit into its strategy stage first — growth, sustain, or harvest — because profitability and asset-utilization targets differ radically across them. Do not impose one corporate ROCE or EVA target on every unit.
2. 2Select the two financial themes that pair to drive this construct: cost reduction/productivity improvement and asset utilization/investment strategy. Revenue growth is the third theme but treat profitability and asset use as the efficiency engines here.
3. 3For cost reduction/productivity, set specific objectives to lower the direct costs of products and services, reduce indirect costs, and share common resources across business units. Attach a measurable metric to each (e.g., unit cost, expense-to-revenue ratio).
4. 4For asset utilization, target working-capital reduction needed to support a given volume and mix of business, and improve fixed-asset use by directing new business to under-capacity resources, using scarce resources more efficiently, and disposing of assets earning inadequate returns on market value.
5. 5Anchor every operational improvement measure to a cause-and-effect chain that culminates in a financial outcome. Explicitly state how a quality, cycle-time, or productivity gain converts to improved sales, reduced operating expense, or higher asset utilization.
6. 6Retain periodic financial statements as a reality check on operational programs. If financial measures fail to respond to sustained operational improvement, treat that gap as a signal to reexamine the strategy itself, not to keep pushing the same programs.
7. 7Design an explicit conversion plan: identify how to increase sales to existing customers, market new products with attractive capabilities, and reach entirely new customer and market segments — otherwise operational gains cannot become profit if customers won't absorb more volume.
8. 8Overlay a risk objective so short-term profitability gains don't mask fragility — for example, diversify revenue sources away from a narrow set of customers, one or two lines of business, or particular geographic regions.

Xerox held a virtual monopoly on plain paper copiers through the mid-1970s, leasing machines and earning revenue on every copy plus paper and toner — sales and profits were large and growing. Customers were disgruntled by high breakdown rates on these expensive machines. Rather than redesign the machines to break down less, Xerox executives saw a way to enhance financial results further: they permitted direct purchase and set up an extensive field service force as a separate profit center to repair broken machines at customer sites. Given the demand, that division soon became a substantial contributor to profit growth, and because no output could be produced while waiting for service, customers bought backup machines. This illustrates the trap: reported profitability rose while the underlying asset (customer loyalty and product quality) was being depleted, leaving Xerox vulnerable to competitors who eventually offered more reliable machines. Real profitability improvement would have redesigned the process; instead financial gains masked a deteriorating position.

• If operational improvements (quality, cycle time, productivity) are not translating into improved sales, reduced operating expenses, or higher asset utilization, then send executives back to rethink strategy or its implementation plan — improvement is a means, not the end.
• If a customer's own sales are flat or declining, or the customer wants backup suppliers, then better quality and on-time delivery will not automatically yield higher profitability — plan to redirect freed capacity to new customers or segments.
• If the corporation is imposing one identical financial target (e.g., 16% ROCE) across business units following different strategies, then override it — determine financial metrics appropriate to each unit's own strategy.
• If short-term financial results can be raised by cutting new product development, process improvement, or by high prices/low service, then treat that reported income gain as suspect: it likely cannibalizes the asset stock and future economic value.
• If fixed assets or scarce resources are under-utilized, then direct new business to them before adding capacity, and dispose of any asset earning inadequate returns on its market value.

• Treating financial improvement as an automatic outcome of quality/cycle-time programs. Tell: operational metrics improve but the income statement stays flat and no one connects the two.
• Boosting reported profitability by cutting spending on R&D, process improvement, human resources, IT, and databases. Tell: reported income rises in the short run while the stock of intangible assets quietly erodes (the IBM/DEC/GM pattern).
• Exploiting customers via high prices or lower service to hit short-term numbers. Tell: profitability up now, customer satisfaction and loyalty down — competitive inroads follow (the Xerox service-center trap).
• Applying a single uniform financial target to every business unit regardless of its growth/sustain/harvest stage. Tell: managers of growth units are penalized against a return metric that only suits mature units.
• Ignoring the financial signal when measures fail to respond to a long-term investment strategy. Tell: leadership keeps funding the vision instead of rethinking the business model the market now rewards.

• ▸Business unit strategy stage: mark growth, sustain, or harvest to set the right target basis.
• ▸Cost reduction objective: name the direct/indirect cost or shared-resource target and its metric.
• ▸Asset utilization objective: state working-capital or fixed-asset target (e.g., redirect idle capacity, dispose of low-return asset).
• ▸Operational driver: the quality/cycle-time/productivity improvement being pursued.
• ▸Conversion path: how this driver becomes higher sales, lower operating expense, or better asset use.
• ▸Demand check: can existing or new customers/segments absorb the freed capacity? (yes/no + plan).
• ▸Financial signal: the periodic metric watched to confirm operational gains hit the bottom line.
• ▸Risk overlay: revenue/customer/geographic diversification objective complementing the return target.
• ▸Reexamine trigger: the threshold at which non-responding financials force a strategy review.

1. 1Treat the financial perspective's top objective as the terminus of every causal chain: require that each customer, internal-process, and learning measure trace forward to higher sales, greater operating margins, faster asset turnover, or reduced operating expenses.
2. 2Reject a single uniform financial metric across business units. Determine appropriate financial metrics per business unit strategy rather than applying one metric or one target company-wide.
3. 3Classify each business unit into its life-cycle stage — Growth, Sustain, or Harvest — because financial objectives differ considerably at each stage.
4. 4Decompose the value objective into its two drivers — revenue growth and profitability/productivity improvement — then assign specific measures under each (new sales, existing-customer sales, operating margin, asset turnover, ROCE).
5. 5Set 3-5 year stretch targets for each strategic financial measure, then forecast year-one milestones so you can assess near-term progress along the long-term trajectory.
6. 6Guard against short-term myopia: keep financial measures as ultimate outcomes but do not let an exclusive focus on improving short-term financial numbers distort the other perspectives.
7. 7Link the strategy to the annual budget so the resources and mechanisms for hitting the long-term financial outcome are actually funded, not just declared.

Rockwater under CEO Norman Chambers and FMC under Larry Brady both used the scorecard to shift away from a historic, short-term focus on cost reduction and low-price competition. Rather than compete on low price, they targeted generating growth opportunities by offering customized, value-added products and services to customers. Their work made explicit that the measures had to tie to strategy: the truly strategic processes — those that must be performed exceptionally well for the strategy to succeed — were identified rather than improving any process where gains were easy. The reengineering targets they set (dramatic time reductions in order-fulfillment cycles, shorter time-to-market, enhanced employee capabilities) were treated not as ends but as capabilities that, through cause-and-effect chains, eventually translate into superior financial performance. This reframes the value-added strategy as a revenue-growth path to the financial objective, not a cost-savings path.

• If the business unit is early in its life cycle with high-growth-potential products, then set financial objectives around revenue growth and accept possibly negative near-term cash flow while committing resources to build capabilities.
• If a measure in another perspective cannot be traced through a cause-and-effect path to a financial objective, then it does not belong on the scorecard.
• If managers propose one financial metric with one target for all business units, then reject it — different strategies demand different metrics.
• If the strategy is value-added differentiation (customized products/services), then measure growth in sales to existing and new customer segments, not just cost reduction.
• If a reengineering or improvement program lacks a link to a specific financial or economic outcome, then treat its promised 'breakthrough' as unverified.

• Managing to quarterly and annual financial reports alone, monitoring and controlling only past-performance measures — the tell is a scorecard full of lagging financial numbers with no leading drivers.
• Applying a single uniform financial metric across all units because it feels fair and consistent — the tell is identical targets imposed on growth and harvest businesses alike.
• Running fragmented improvement programs (TQM, JIT, reengineering) not linked to strategy or economic outcomes — the tell is 'demonstrated success stories' with disappointing aggregate results.
• Slash-and-burn reengineering measured by cost savings alone — the tell is cost-cutting targets with no time-reduction or capability targets tied to future revenue.
• Exclusive focus on improving short-term financial measures — the tell is rising near-term numbers alongside eroding customer and capability investments (myopia and distortion).

• ▸Business unit & strategy: name the unit and its chosen strategy (growth/value-added/cost).
• ▸Life-cycle stage: Growth, Sustain, or Harvest.
• ▸Top financial objective: the ultimate outcome measure for this unit.
• ▸Revenue-growth drivers: sales to existing customers, new products, new segments.
• ▸Productivity/profitability drivers: operating margin, asset turnover, operating-expense reduction, ROCE.
• ▸3-5 year stretch target: quantified long-term outcome.
• ▸Year-one milestone: near-term target for progress along the trajectory.
• ▸Cause-and-effect trace: which customer/process/learning measures link to this objective.
• ▸Budget link: resources and mechanisms funded to achieve the outcome.

1. 1Start from the customer and internal-business-process objectives already set on the scorecard, then ask what people, systems, and organizational procedures those objectives assume you have. The gap between today's capabilities and what the objectives require is the raw material for this perspective.
2. 2Name the gap in each of the three source categories explicitly: people (employee skills, motivation, flexibility), systems (information technology, databases), and organizational procedures (climate for motivation, empowerment, alignment). Do not collapse them into a single 'training' line item.
3. 3For the people gap, specify reskilling targets tied to the analytic functions the strategy now demands — engineering, marketing, management, administration — reflecting that even direct-production workers are now valued for problem-solving, not physical output.
4. 4For the systems gap, define what data, databases, and information technology frontline staff need to act on the moment they face a customer or process. Treat information access as a capability the strategy stands on, not overhead.
5. 5For the organizational-procedures gap, build measures of motivation, empowerment, and alignment so that employee suggestions and specific knowledge are actually channeled toward strategic goals.
6. 6Trace each capability investment forward through a cause-and-effect chain: reskilling and IT deployment improve internal processes, which improve customer outcomes, which drive future financial performance. If an investment cannot be linked along this trajectory, question it.
7. 7Keep the whole set small — the passages show 20–25 measures across all four perspectives can communicate a single strategy — so allocate only a handful of measures to learning and growth rather than a sprawling training dashboard.
8. 8Review the gaps periodically as customer and process targets change, because today's technologies and capabilities will not meet long-term targets under intense global competition.

Consider the refurbished Ford engine plant cited in the passages. The machines are designed to run automatically, so the plant manager redefines the workers' job: 'The people's job is to think, to problem solve, to ensure quality, not to watch the parts go by.' In Balanced Scorecard terms, this is a learning-and-growth decision. The internal-process objective (high-quality, low-cost engine output) can no longer be met by direct labor used only for physical capabilities, so the capability gap is a workforce that can problem-solve and improve quality. The investment addresses all three sources: people are reskilled toward analytic, problem-solving work; systems must give them the information to diagnose quality issues; and procedures must treat people as problem-solvers, not variable costs, so their suggestions are captured. The payoff is not measured directly in dollars but through the trajectory — better problem-solving improves quality and cycle time, which serves customers, which eventually improves financial results.

• If a customer or internal-process target cannot be met with today's technologies and capabilities, then it is generating a learning-and-growth objective that must be funded, not deferred.
• If a proposed capability investment cannot be linked through cause-and-effect to a process, customer, and eventually financial outcome, then it is discretionary spending, not strategic investment.
• If employees still perform tasks under direct supervision without contributing knowledge or suggestions, then the organizational-procedures gap (empowerment and alignment) is unaddressed regardless of how much training you buy.
• If frontline people cannot get the data they need at the point of decision, then treat information technology and databases as a capability shortfall, not an IT budget line.
• If your measure set is ballooning, then cut back toward the 20–25 total across four perspectives — a bloated learning-and-growth section signals you have stopped choosing.

• Treating people as variable costs rather than problem-solvers — the tell is that improvement suggestions from direct staff are never solicited or measured.
• Funding physical and financial assets well while starving intangible assets (skills, motivation, databases, systems) — the tell is a strategy that assumes efficient asset management alone will sustain advantage, which the passages say no longer works.
• Managing this perspective by past financial reports — the tell is that capability investments get cut in a weak quarter because their value never appears on the historical-cost balance sheet.
• Investing in skills but not in the systems and procedures that let those skills act — the tell is trained employees who still lack the information or authority to change anything.
• Piling on nonfinancial measures without cause-and-effect linkage — the tell is a long list of learning metrics that no one can connect to customer or financial outcomes, so they get ignored.

• ▸Triggering objective: name the customer or internal-process target that today's capabilities cannot meet.
• ▸People gap: which skills, motivation, or flexibility are missing (specify analytic/problem-solving functions).
• ▸Systems gap: which data, databases, or information technology the relevant people lack at the point of decision.
• ▸Procedures gap: where motivation, empowerment, or alignment breaks down.
• ▸Reskilling action: the specific investment closing the people gap.
• ▸Cause-and-effect link: how this investment flows to process → customer → financial outcome.
• ▸Measure: the one metric (kept minimal) that tracks progress on this gap.
• ▸Owner and review date: who is accountable and when the gap is reassessed against changing targets.

1. 1Sequence the perspectives, don't parallelize them: establish financial objectives, then customer objectives (who the targeted segments are and what superior service means to them), and only then derive internal-process objectives — because the internal processes you must excel at are defined by the customer value proposition, not by whatever you already run.
2. 2Map the full internal value chain in three linked stages: the innovation process (anticipating future needs, devising new product/service offerings), the operations process (producing and delivering customized high-quality products at low cost with short lead times), and postsale service. Identify where value is actually created for the targeted segments across all three.
3. 3Distinguish 'existing processes to improve' from 'processes that are truly strategic.' For each candidate process, ask whether it must be performed exceptionally well for the strategy to succeed. If a process is not strategic, resist the reflex to pour measurement into it.
4. 4Search deliberately for entirely new processes. The scorecard's benefit is that customer/financial objectives often reveal internal processes the organization does not yet perform. Do not limit measurement to cost, quality, and cycle time of what already exists — that traps you in incremental improvement of the wrong things.
5. 5Redesign around integrated, cross-functional processes rather than functional silos. Trigger operations from customer orders (pull), not production plans that push through the value chain, so cost, quality, and response times improve across every unit along the chain.
6. 6Select measures per stage: for innovation, effectiveness of new product developments and speed of deploying new technologies into operations; for operations, manufacturing cycle times, quality, and delivery times; for postsale service, response and resolution measures. Keep the total lean — 20 to 25 measures across all four perspectives can carry a single strategy.
7. 7Link each internal-process measure through cause-and-effect to a customer outcome and a financial result, so measures read as a connected chain, not a list requiring complex trade-offs.
8. 8Force consensus before finalizing: run the definition process across the executive team to expose disagreements about what 'superior service' and 'targeted customers' actually mean, because those hidden differences dictate which internal processes matter.

The banking case in the passages shows the mechanism. Twenty-five senior executives all agreed on the strategy: 'provide superior service to targeted customers.' But when they moved to formulating customer objectives, it became clear each executive held a different definition of what superior service represented and who the targeted customers were. The act of developing operational scorecard measures forced consensus on the most desirable customer segments and the products and services to offer them. Only with financial and customer objectives settled could they identify the internal business processes needed to deliver that value. That sequence — and the disagreement it surfaced — is exactly why internal-process definition is called one of the principal innovations of the scorecard: it revealed processes the bank had to excel at that a purely internal, cost-focused review would never have named.

• If a process only lowers cost, improves quality, or shortens response time of something you already do, then treat it as continuous improvement — not necessarily a strategic scorecard process.
• If a process must be performed exceptionally well for the strategy to succeed, then it belongs on the scorecard even if you don't currently perform it at all.
• If executives cannot agree on who the targeted customers are, then stop and resolve customer objectives before defining any internal-process measures — the internal processes depend on that answer.
• If you compete in an industry with rapid technological innovation, then weight the innovation process heavily (anticipating future needs, radical new offerings, rapid deployment); if product life cycles are long, then still keep continuous process improvement as a strategic measure.
• If operations are still triggered by production plans rather than customer orders, then flag the operations process for redesign toward an integrated, order-triggered value chain.

• Measuring only existing processes. The tell: your internal-process metrics are all cost/quality/cycle-time of current operations and no genuinely new process ever appears — you're improving the wrong things efficiently.
• Skipping the innovation and postsale stages. The tell: the scorecard covers manufacturing and delivery but is silent on new-product-development effectiveness and on service after the sale, leaving two-thirds of the value chain unmeasured.
• Defining internal processes before customer segments. The tell: process owners choose metrics that flatter their function rather than serve a targeted segment, because no one agreed who the customer is.
• Preserving functional silos. The tell: measures live inside purchasing, manufacturing, marketing separately, with hand-offs and slow response between departments and no cross-functional process measure.
• Overloading the scorecard. The tell: dozens of internal measures presented as independent trade-offs rather than a lean set (20–25 total across four perspectives) tied in cause-and-effect chains — the strategy story becomes unreadable.

• ▸Targeted customer segment: name the specific segment this process serves.
• ▸Customer value proposition: state what 'superior' means to that segment (e.g., customization, low cost, short lead time).
• ▸Value-chain stage: mark innovation / operations / postsale service.
• ▸Process name: the specific internal process under review.
• ▸New or existing: is this a process you already run, or one the objectives reveal you must create?
• ▸Strategic test: must this be performed exceptionally well for the strategy to succeed? (yes/no + why).
• ▸Cross-functional span: which functions must integrate to run it end-to-end.
• ▸Measure(s): 1–3 metrics — e.g., new-product-development effectiveness, cycle/delivery time, quality, service response.
• ▸Cause-and-effect link: which customer outcome and which financial result this measure drives.

1. 1Define the target customer segments first. Do not build one value proposition for all buyers; the passages note that once basic needs are met, customers 'want more individualized solutions to their wants,' so segment before proposing value.
2. 2Specify the value proposition as a combination of three attribute classes: product/service attributes (price, quality, functionality), relationship characteristics (service, partnership), and image/reputation. Write down what you promise on each for each segment.
3. 3Pick the strategic stance explicitly: away from 'historic, short-term focus on cost reduction and low-price competition,' toward 'generating growth opportunities by offering customized, value-added products and services to customers' — the stance Chambers and Brady adopted.
4. 4Attach measures from the Customer Perspective to that proposition, and balance lagging outcome indicators (retention, satisfaction) with leading drivers (delivery time, quality) so you can see whether the proposition is landing before financials confirm it.
5. 5Integrate supply, production, and delivery so operations are 'triggered by customer orders, not by production plans that push products and services through the value chain' — this is how you deliver customization without the usual high-variety cost penalty.
6. 6Cascade the customer objective down: decompose a business-unit measure such as on-time delivery (OTD) into local targets like 'reduce setup times at a specific machine' or 'rapid transfer of orders from one process to the next.'
7. 7Communicate the proposition and its measures across the organization via newsletters, bulletin boards, and networked systems so every employee sees the customer objectives that must be met for the strategy to succeed.
8. 8Review whether the proposition still fits: with shrinking product life cycles, keep 'anticipating customers' future needs' and feed new offerings back into efficient delivery processes.

Analog Devices, described in the passages, built a 'Corporate Scorecard' that carried, alongside traditional financial measures, performance measures on customer delivery times, quality, and manufacturing cycle times. This ties value delivery to concrete operational drivers: delivery time and quality are exactly the product/service attributes customers experience. Art Schneiderman, then VP of quality improvement and productivity, brought this to the study group as a live case. The scorecard let Analog track rates of progress in continuous improvement rather than waiting for financial results to reveal whether customers were being served well. In practice you would take a customer promise — say, on-time delivery — and translate it, as the passages show, into a local goal such as reducing setup time at a specific machine. That connects the customer value proposition to the shop-floor actions that actually produce it.

• If a customer segment has satisfied basic needs, then compete on customized, value-added offerings rather than low-cost standardized products.
• If you promise customization, then integrate supply-production-delivery so operations trigger off customer orders — otherwise you pay 'the usual cost penalty for high-variety, low-volume operations.'
• If a process must be performed exceptionally well for the strategy to succeed, then treat it as strategic and measure it; don't just improve existing processes generically.
• If a high-level customer measure (e.g., OTD) exists, then decompose it into specific local objectives so improvement efforts align with the proposition.
• If you compete in a rapid-innovation industry, then a current-generation advantage does not carry forward — reassess the value proposition each product cycle.

• Measuring only summary financials: the tell is that you can report ROCE but cannot say what customer delivery time or quality trend is driving it. The passages warn financial measures were 'hindering organizations' abilities to create future economic value.'
• Improving processes without linking them to strategy: the tell is broad cost/quality/response programs running while 'not identifying the processes that were truly strategic.'
• Pushing products by production plan instead of pulling by customer orders: the tell is inventory and slow response despite 'arm's-length' order handling.
• Fragmented improvement programs (TQM, empowerment, reengineering) not tied to the customer proposition or to financial outcomes: the tell is disappointing results and champions competing for executive time.
• Defaulting to low-price competition when the segment now wants individualized solutions: the tell is a Henry-Ford 'any color as long as it's black' offering in a market that has moved past standardization.

• ▸Target segment: name the specific customer group this proposition serves
• ▸Product/service attributes: state your promise on price, quality, and functionality
• ▸Relationship characteristics: state your service and partnership commitments
• ▸Image/reputation: state the perception you intend to build with this segment
• ▸Strategic stance: low-cost/standardized vs. customized/value-added — pick one and justify
• ▸Outcome (lagging) measures: e.g., retention, satisfaction for this segment
• ▸Driver (leading) measures: e.g., delivery time, quality, cycle time
• ▸Local cascade: decompose one measure into a specific operational target (machine/process/hand-off)
• ▸Communication channel: how every employee will learn this objective

1. 1Define the targeted customer segments first — loyalty measures mean nothing until you specify from whom you expect your greatest growth and profitability. Customize the core measures to those segments rather than tracking loyalty across the whole customer base.
2. 2Install the core measurement group in the customer perspective: market share, customer retention, customer acquisition, customer satisfaction, and customer profitability. Arrange them as a causal chain, not a scattered dashboard.
3. 3Do not stop at 'satisfied.' Segment satisfaction scores so you can isolate the 'completely or extremely satisfied' band — research shows only this top band predicts repeat purchasing. Treat merely-adequate satisfaction as a warning, not a win.
4. 4Identify the performance drivers behind loyalty by analyzing customer preferences: ask which attributes your targeted customers actually value (e.g., on-time delivery), then place those value-proposition attributes in the customer perspective as leading indicators of loyalty.
5. 5Trace the cause-and-effect chain upward and downward: link loyalty to financial outcomes (repeat and expanded sales → ROCE) and downward to the internal processes (short cycle times, high internal quality) and learning-and-growth capabilities (employee reskilling) required to deliver the valued attributes.
6. 6Establish feedback mechanisms to measure satisfaction directly — either capture voluntary supplier report cards from customers or run systematic customer satisfaction surveys rather than assuming customers will proactively report.
7. 7Guard loyalty against short-term financial pressure: audit whether reported profit gains come from higher prices or reduced service, which enhance current income while depleting loyalty and leaving you vulnerable to competitors.
8. 8Validate the loyalty hypothesis over time — the strategy is a set of cause-and-effect hypotheses, so check whether improvements in the drivers (satisfaction, on-time delivery) actually move retention and expanded sales, and revise if the linkage fails.

Xerox up through the mid-1970s held a virtual monopoly on plain paper copiers, leasing machines and earning revenue on every copy plus paper and toner. Sales and profits were large and growing, so the financial measures told a strong story. But customers were disgruntled about high breakdown rates and malfunctions on expensive machines. Rather than redesign the machines to break down less, Xerox executives permitted direct purchase and built a separate field-service profit center to repair machines — and because no output could be produced while waiting for a service person, customers bought backup machines, inflating sales further. This is the loyalty trap in reverse: reported profitability rose while customer satisfaction and loyalty eroded, leaving Xerox highly vulnerable to more efficient and innovative competitors once alternatives appeared. Had Xerox carried a satisfaction and loyalty measure in a customer perspective alongside its financials, the depletion of this intangible asset would have surfaced before competitors exploited it.

• If a customer rates their experience merely 'adequate' rather than 'completely or extremely satisfied,' then do not count on repeat purchasing — treat it as at-risk, not retained.
• If reported income rose but it came from higher prices or lower service, then flag the gain as cannibalized future value, not genuine performance.
• If a customer attribute (e.g., on-time delivery) shows up as highly valued in preference analysis, then promote it to a performance-driver measure in the customer perspective and connect it to your internal-process targets.
• If the required employee reskilling to deliver the value proposition is high across a large share of the workforce, then add a strategic job coverage ratio to the learning-and-growth perspective, because loyalty depends on delivering what employees are not yet equipped to deliver.
• If targeted customers do not proactively supply feedback, then run systematic satisfaction surveys rather than inferring loyalty from sales volume alone.

• Reading rising sales and profit as loyalty. Tell: financials are strong but breakdown rates, complaints, or backup purchases (as at Xerox) are climbing — you are measuring lagging outcomes only.
• Measuring loyalty across the whole customer base instead of targeted segments. Tell: your retention number looks fine but you cannot say which segment is defecting or growing.
• Settling for 'satisfied' scores. Tell: high average satisfaction coexists with flat or declining repeat purchasing because only the extremely-satisfied band actually returns.
• Tracking loyalty as a standalone number with no drivers. Tell: satisfaction dips and you have no measured attribute (delivery, quality, cycle time) to explain why or to act on.
• Cutting service, product development, or customer investment to hit short-term numbers. Tell: income rises this quarter while the stock of customer goodwill quietly erodes, exposing you to competitive inroads.

• ▸Targeted segment: name the customer group expected to drive greatest growth/profitability
• ▸Loyalty outcome measure: retention rate and % of expanded/repeat sales from existing customers
• ▸Satisfaction band split: % completely/extremely satisfied vs. merely adequate
• ▸Valued attribute (driver): the preference customers rate most critical (e.g., on-time delivery)
• ▸Internal process required: process that must excel to deliver the attribute (cycle time, internal quality)
• ▸Capability gap: strategic job coverage ratio — employees qualified vs. needed for this value proposition
• ▸Financial linkage: how loyalty feeds ROCE via repeat and expanded sales
• ▸Short-term risk check: is any recent profit gain from higher price or lower service? (yes/no + note)

1. 1Start with the senior executive team translating the business unit's strategy into explicit financial goals: decide whether to emphasize revenue and market growth, profitability, or cash flow generation. For a growth strategy, name revenue and market growth as the primary theme.
2. 2Refuse the corporate uniform-metric trap. Do not accept the same 16% return-on-capital-employed or maximize-EVA target imposed on every unit; determine financial metrics specific to your unit's growth strategy.
3. 3Define the target market and customer segments explicitly before setting growth measures. Force the executive team to reach consensus on which customer segments to serve and which products/services to offer them — as one financial institution discovered, 'superior service to targeted customers' meant something different to each of 25 executives until operational measures forced agreement.
4. 4Select revenue-growth measures tied to the two drivers named in the definition: new customer acquisition (new segments, new market areas) and expanding business with retained, loyal customers.
5. 5Build the cause-and-effect chain: every growth measure must link backward to internal-process, customer, and learning-and-growth objectives that will deliver that revenue, and forward to long-run economic performance. The scorecard should tell the story of the growth strategy.
6. 6Guard revenue-growth measures against short-term gaming: flag any 'growth' produced by high prices or reduced service (which erodes loyalty) and any reported income increase caused by cutting spending on customer/market development or R&D.
7. 7Distinguish sustainable growth from cannibalizing growth: verify that reported sales and profit gains are not masking disgruntled customers who are vulnerable to competitive inroads.
8. 8Roll the market-and-revenue-growth theme down to every business and service unit, as Pioneer Petroleum did — divisionwide scorecard with targeted segments and broad themes first, then unit-level scorecards.

Xerox up through the mid-1970s held a virtual monopoly on plain paper copiers, leasing machines and earning revenue on every copy plus paper and toner — sales and profits were large and growing. When customers complained about high breakdown rates, executives chose to grow revenue further rather than fix the product: they allowed direct machine purchase and built a separate field-service profit center to repair the frequent malfunctions. Because a broken machine produced no output, customers bought backup machines, so sales and profits climbed even higher. Every financial indicator — sales growth, profit growth, return on investment — signaled a highly successful strategy. But customers remained unhappy and surly, and the growth rested on excellence at handling breakdowns rather than customer loyalty. This is the trap the construct warns against: revenue growth that is real on the statements yet unsustainable because it is not driven by satisfied, loyal customers.

• If the corporate parent imposes one financial target (e.g., 16% ROCE) across all units, then reject it for your growth-stage unit and choose metrics matched to your strategy.
• If a revenue increase comes from raising prices or cutting service, then treat it as a warning of future vulnerability, not as strategic growth.
• If reported income rose because spending on databases, systems, R&D, or customer/market development was cut, then read it as cannibalized future value, not growth.
• If executives cannot name the specific target customer segments, then stop and reach consensus before selecting any market-share or revenue-growth measure.
• If a growth measure has no traceable link back to a customer, internal-process, or learning objective, then it does not belong on the scorecard.

• Applying one identical financial metric to every business unit — the tell is that a fast-growth unit and a mature unit carry the same return-on-capital target.
• Confusing revenue growth with strategy success while customers are disgruntled — the tell is rising sales and profit alongside high complaint or breakdown rates, as at Xerox.
• Growing reported income by cutting investment in customer relationships and capabilities — the tell is that margins improve while the stock of intangible assets shrinks.
• Setting growth measures before defining target segments — the tell is that each executive privately holds a different definition of the target customer.
• Treating the scorecard as only a measurement system rather than tying growth measures to strategy — the tell, seen in most companies, is improving existing processes generically instead of identifying the processes that are truly strategic for growth.

• ▸Financial emphasis: state whether this unit prioritizes revenue/market growth, profitability, or cash flow.
• ▸Target market segments: name the specific customer and market segments where you compete.
• ▸Market-share measure: state current share and target (e.g., Metro Bank's 30% of core deposit accounts).
• ▸Revenue-growth measure: define the sales-growth rate target and its baseline.
• ▸New-customer acquisition driver: state the measure for reaching new segments/market areas.
• ▸Existing-customer expansion driver: state the measure for growing business with loyal customers.
• ▸Cause-effect link: name the internal-process and learning objectives that produce this growth.
• ▸Sustainability check: state how you will confirm growth is not price/service gaming or cannibalized investment.
• ▸Unit rollout: name each business/service unit that must carry a version of this growth objective.