Key Takeaways
Separate outcomes, operating signals, and the few measures that change results
Three measures do different jobs. A key result indicator (KRI) summarizes what happened across a broad area, such as customer satisfaction or profit. A performance indicator (PI) helps show what people should do. A key performance indicator (KPI) identifies an action that can materially improve results. Parmenter compares the measures to layers around an onion: broad outcomes sit outside, while the actionable drivers are deeper in the organization.
Do not confuse visibility with usefulness. Profit tells leaders whether the organization is succeeding, but it does not tell a team what to change tomorrow. A useful measurement system keeps outcomes, operational signals, and high-impact action measures distinct, so each audience can see the information it needs.
This distinction is valuable because organizations often treat every number on a dashboard as if it answers the same question. Separating outcomes from actions resembles the distinction in control theory between observing a system's state and choosing an input that changes it. The framework also discourages executives from asking a single metric to serve governance, diagnosis, and motivation at once. Its categories are practical rather than universal laws, however. A measure's role can depend on the decision, time horizon, and organizational level, so classification should guide interpretation rather than become a labeling contest.
Call a measure a KPI only when people can act on it in time
A KPI is a live lever. In this book, a strong KPI is nonfinancial, measured frequently, understood by staff, tied to an individual or team, and followed by action from senior leaders. It should affect important success factors across more than one balanced-scorecard perspective, and improvement should benefit other measures rather than simply shifting the problem elsewhere.
Frequency matters. A monthly or annual result usually arrives too late to guide a rapid correction, while a daily or continuously updated measure can direct attention while action is still possible. The measure must also be intelligible to the people responsible for it: staff need to know both what the number means and what response is within their authority.
The emphasis on actionability makes measurement a management routine, not a hunt for impressive metrics. It connects with the idea of feedback latency: the longer the delay between an event, its detection, and a response, the less useful the signal becomes for correction. Yet frequent measurement is not automatically better. High-frequency tracking can produce noise, surveillance concerns, and overreaction to ordinary variation. A sound design therefore matches update speed to the process, and pairs the indicator with clear authority and a sensible threshold for intervention.
Measure the intervention, not just the aftermath
Track what can still be changed. British Airways' late-plane example shows the difference. A senior executive was alerted whenever a plane crossed a delay threshold, prompting airport managers to coordinate ground crews and other staff to recover time. Delays were not merely an inconvenience: they could raise costs, frustrate passengers, disrupt suppliers, and add fuel use when crews tried to catch up in flight.
Follow the cause into the work. A distribution-company CEO focused on trucks leaving with unused capacity. Dispatch managers were prioritizing delivery timing, but customers could sometimes accept a shipment on another date that allowed a fuller load. A daily report made that choice visible. Both examples point toward measuring a correctable operating decision, not only the later financial result.
These cases make the metric's value concrete: it changes coordination across functions, rather than merely documenting failure. In organizational design, this resembles managing a process at its points of leverage, where small operational choices influence several downstream outcomes. The examples also show why cross-functional measures can outperform departmental scorekeeping. Still, a single executive escalation can create fear-driven compliance. Sustainable improvement depends on giving teams the information and discretion to solve the problem, not just making the cost of a missed target personally uncomfortable.
Keep the executive signal set small enough to guide attention
Use a portfolio, not a metric warehouse. The book's 10/80/10 rule proposes roughly 10 KRIs, up to 80 PIs, and about 10 KPIs for an organization. The board's dashboard should emphasize a small set of high-level results. Managers and teams need a broader working scorecard, mixing operational indicators with the few measures that demand rapid action.
Standardize before multiplying. What appears to be many different measures may be the same indicator defined differently by separate teams. A shared definition and reporting format can reduce duplication. The suggested numbers are a guide, not a quota: a diverse conglomerate may need separate sets for distinct businesses, while another organization may need fewer measures. More indicators do not necessarily mean more control; they can dilute attention.
The underlying insight is about scarce attention, a resource as real as budget or staff time. A deliberately limited dashboard helps leaders distinguish signals from administrative noise and makes it easier to remember what deserves follow-up. This also resembles good information design: the point is not to display everything available, but to make the consequential patterns legible. The proposed counts should not be treated as a scientifically fixed optimum. Complexity varies, and an overly strict cap can hide important risks. The better test is whether each measure supports a distinct decision.
Trace every measure from strategy through a handful of success factors
Build the chain before choosing metrics. The book connects an organization's mission, vision, and strategy to its critical success factors (CSFs), then to measures. A mission expresses the enduring purpose; a vision describes a destination; strategy explains how to move toward it. CSFs identify the few conditions essential to organizational health. Parmenter recommends narrowing a long list to about five to eight core factors.
Look across the whole organization. The balanced scorecard used here covers financial results, customer focus, internal processes, learning and growth, employee satisfaction, and environment or community. For an airline, timely arrivals can influence cost, customer trust, staff workload, suppliers, and fuel use. A factor that touches several perspectives is more likely to be central than one that matters to only a narrow function.
This strategy-to-measure chain counters a common failure of dashboards: indicators accumulate because data exists, not because leaders know what success requires. It also offers a useful test for strategic coherence. If no measure connects a stated priority to observable work, the strategy may remain rhetorical. The six perspectives widen attention beyond financial results and customer satisfaction, particularly toward employees and communities. But a neat map can imply causal certainty that organizations rarely possess. Links should be treated as hypotheses to test, not proof that one metric directly causes another.
Give frontline teams authority, or your measures will teach them to cheat
Measurement changes behavior. The book describes a train service where drivers were judged on punctuality. To appear on time, some stopped in a way that triggered the signal at the far end of a platform, then departed without opening the doors. The punctuality figure improved while passengers suffered. The measure rewarded the appearance of performance instead of the service's purpose.
Design with the people doing the work. Parmenter's four foundation stones call for partnership with staff, unions, key suppliers, and customers; transferring power to frontline teams; integrating measurement with reporting and improvement; and linking measures to strategy. Consultation helps reveal what a metric will actually encourage. Empowerment lets employees fix problems promptly, while training clarifies the response expected and the authority available.
The train story captures a central problem in incentive design: people optimize what is rewarded, sometimes at the expense of the real goal. It is closely related to Goodhart's law, the observation that a measure can become less informative once it becomes a target. Partnership and frontline authority help because workers understand operational edge cases that executives may not see. Consultation alone is not a cure, however. Measures still need safeguards, customer outcomes, and periodic review, since even a well-intentioned target can create unintended trade-offs.
Report each measure at the speed its decision requires
Different audiences need different clocks. The board needs a concise governance dashboard of KRIs, generally reviewed monthly. Managers need a working scorecard that includes PIs and KPIs. A small number of urgent measures may need daily or continuous reporting; other critical measures can be reviewed weekly, and routine indicators monthly. The book suggests that an organization might track one or two KPIs daily and a further group of key measures weekly.
A report should prompt a choice. An old number can describe a problem without helping anyone prevent its consequences. Timely reporting should be brief, accessible, and connected to a person or team who can respond. The board's role is different from day-to-day management, so flooding directors with operational detail can distract them from governance rather than improve oversight.
Cadence is not a formatting detail. It determines whether a report functions as feedback or as an autopsy. Separating board-level results from operational signals also clarifies accountability: directors can ask whether the organization is healthy, while managers decide what action to take. This resembles layered monitoring in complex systems, where each level receives information at a scale suited to its decisions. The risk is mistaking speed for insight. Real-time dashboards are useful only when the underlying data is reliable and someone has both the competence and authority to act.
Build the measurement system with staff, then improve it in short cycles
Treat implementation as organizational work. The book offers a 12-step model, aiming for a working system in about 16 weeks. It begins with senior-management commitment, a small project team reporting to the CEO, staff communication, and agreement on CSFs. Teams then select relevant measures, record them in a shared database, and develop reporting and review routines. A trained external facilitator can mentor the group, but should not replace internal ownership.
Start with tools already available. Parmenter advises using existing spreadsheets, presentation software, and databases during the first year rather than letting a software purchase delay the work. Team-level measures matter especially because those employees can often correct problems directly. Measures and reports should be reviewed and refined as priorities or operating conditions change.
The practical strength here is its sequencing: secure sponsorship, explain the purpose, establish shared definitions, and only then invest in infrastructure. That approach aligns with implementation research, which repeatedly finds that adoption depends on routines, skills, and local legitimacy, not software alone. A small team can also keep the project moving without turning measurement into a sprawling committee exercise. The 16-week timetable is best understood as a disciplined target, not a universal promise. Organizations with weak trust, fragmented data, or unclear strategy may need more preparation.
Treat targets as moving guides, not annual promises
Expect conditions to change. Parmenter warns that fixed annual targets can become detached from the world in which teams must perform. The book favors relative comparisons where useful, such as comparing results with other organizations, and ranges rather than a single future number. A range can acknowledge uncertainty while still showing the direction and level of improvement expected.
Plan on a rolling horizon. Its beyond-budgeting discussion proposes updating an 18-month forecast quarterly, with nearer-term spending decisions considered in shorter cycles. This avoids treating an annual budget as an unchanging contract. Performance measures should also evolve: teams can adjust indicators as they master one problem and shift attention to another, while organization-wide CSFs and enduring measures are reviewed as strategy and circumstances change.
The argument recognizes that a target is a forecast about a future context, not a fact. Ranges and relative comparisons can reduce the false precision that encourages gaming when demand, capacity, or external conditions shift. Rolling planning also moves attention from defending last year's assumptions to making current choices. Yet relative performance can mislead when peer organizations face different constraints, and flexible targets can weaken accountability if leaders revise them after every setback. Adaptability works best when changes are transparent, documented, and tied to evidence rather than convenience.
Analysis
Parmenter's central contribution is a change in the unit of attention. Performance management is not primarily a matter of adding more indicators; it is a matter of distinguishing retrospective results from operational signals and from the small number of actions capable of shifting several outcomes. That distinction then reshapes governance: boards receive concise evidence of organizational health, while managers and teams receive more frequent information connected to decisions.
The book is unusually alert to behavioral consequences. The train service example makes clear that a metric is not a neutral description once workers are judged by it. Measurement creates incentives, and incentives can redirect effort toward the measured proxy rather than the intended service. Partnership, frontline authority, and consultation are therefore not soft additions to a technical system. They are safeguards against designing measures that look coherent on paper but produce perverse workarounds.
Its implementation guidance is also a substantive claim: the hard part is adoption, not calculation. A small internal team, senior sponsorship, clear strategy, shared definitions, and use of existing tools can matter more than buying sophisticated software. The proposed 16-week timeline creates urgency, though it should not be mistaken for a guaranteed duration across organizations with different levels of trust, data quality, or strategic clarity.
The framework's limitation is its confidence that a limited set of high-leverage measures can be identified cleanly. In real organizations, causal chains are uncertain, outcomes can conflict, and indicators can become targets. The book's own insistence on balance, consultation, and regular refinement helps address this, but cannot eliminate the problem. Its most durable lesson is therefore not to worship the right metric. It is to treat measures as instruments for shared learning, test whether they improve decisions, and watch closely for the behavior they reward.
Review Summary
Key Performance Indicators receives mixed reviews, with an average rating of 3.81 out of 5. Many readers find it valuable for understanding KPIs and implementing them in organizations. The book is praised for its step-by-step guidance, clear explanations, and practical examples. However, some criticize its focus on large organizations and lack of technical depth. Readers appreciate the distinction between different types of indicators and the visual aids provided. Some find the content repetitive or overly focused on consulting practices. Overall, it's considered a useful resource for those involved in performance management and strategy implementation.
People Also Read
Glossary
Key Result Indicator
Summarizes accumulated outcomesA measure showing what the organization has achieved in a broad area or perspective. It reflects the combined effects of many activities, such as customer satisfaction or net profit, but does not by itself identify the action needed to improve the result. The book positions KRIs primarily as high-level information for boards and governance.
Performance Indicator
Guides operating actionA measure that helps indicate what teams or managers should do in their work. PIs sit between broad outcome measures and the few organization-wide KPIs. They can support management and team scorecards, and should connect to the organization's critical success factors rather than exist merely because data is available.
Key Performance Indicator
Signals high-impact actionA measure focused on an activity critical to current or future organizational success. In the book's specialized definition, KPIs are nonfinancial, measured frequently, understood by staff, tied to a responsible individual or team, and acted on by senior leaders. A strong KPI affects multiple critical success factors or scorecard perspectives and signals action while intervention is still possible.
Critical Success Factors
Conditions essential to successThe relatively small number of issues that determine an organization's health and continued success. The book recommends identifying roughly five to eight organization-wide CSFs before selecting performance measures. They should connect strategy to daily work and be considered across financial, customer, internal-process, learning and growth, employee-satisfaction, and environment or community perspectives.
10/80/10 rule
Suggested measure portfolioA guide to limiting organizational measures to about 10 key result indicators, up to 80 performance indicators, and about 10 key performance indicators. The figures are not a fixed quota. They encourage organizations to distinguish results, operating measures, and high-impact KPIs, and to resist the assumption that adding more metrics creates better management.
Balanced scorecard
Views performance across perspectivesA framework for measuring organizational performance beyond financial results alone. The book uses six perspectives: financial performance, customer focus, internal processes, learning and growth, employee satisfaction, and environment or community. Measures should connect to strategy and critical success factors, with reporting adapted for boards, managers, and teams.
Four foundation stones
Principles for KPI adoptionFour principles intended to make measurement useful and acceptable: partnership with staff, unions, key suppliers, and key customers; transfer of power to frontline employees; integration of measurement, reporting, and performance improvement; and linkage of measures to strategy. Together they frame KPI implementation as a participative organizational change effort.
12-step model
KPI implementation sequenceThe book's staged process for developing and using performance measures. It begins with senior-management commitment and a project team, then builds a consultative culture, establishes strategy and critical success factors, records measures, supports team-level selection, chooses organizational KPIs, creates reporting routines, and periodically refines the system.
FAQ
What's "Key Performance Indicators: Developing, Implementing, and Using Winning KPIs" by David Parmenter about?
- Comprehensive Guide: The book provides a detailed guide on developing, implementing, and using key performance indicators (KPIs) effectively within organizations.
- Focus on KPIs: It distinguishes between key result indicators (KRIs), performance indicators (PIs), and KPIs, emphasizing the importance of understanding these differences for successful performance measurement.
- Implementation Strategy: The book outlines a 12-step model for implementing KPIs, ensuring that organizations can achieve significant performance improvements.
- Foundation Stones: It introduces four foundation stones crucial for KPI development: partnership, empowerment, integration, and strategic linkage.
Why should I read "Key Performance Indicators" by David Parmenter?
- Practical Insights: The book offers practical insights and strategies for organizations looking to improve their performance measurement systems.
- Proven Methodology: It provides a proven methodology for developing and implementing KPIs, backed by case studies and real-world examples.
- Comprehensive Approach: Readers gain a comprehensive understanding of how to align KPIs with organizational strategy and critical success factors.
- Avoid Common Pitfalls: The book helps readers avoid common pitfalls in KPI implementation, ensuring a more effective and efficient process.
What are the key takeaways of "Key Performance Indicators" by David Parmenter?
- Differentiate KPIs: Understanding the difference between KRIs, PIs, and KPIs is crucial for effective performance measurement.
- 12-Step Model: The book outlines a 12-step model for implementing KPIs, emphasizing preparation, execution, and continuous improvement.
- Foundation Stones: Successful KPI implementation relies on four foundation stones: partnership, empowerment, integration, and strategic linkage.
- Focus on Critical Success Factors: Identifying and focusing on critical success factors (CSFs) is essential for developing meaningful KPIs.
What are the best quotes from "Key Performance Indicators" and what do they mean?
- "KPIs tell you what to do to increase performance dramatically." This quote highlights the transformative power of KPIs when correctly identified and implemented.
- "The ultimate success of a change strategy depends greatly on how the change is introduced and implemented." It emphasizes the importance of the implementation process in achieving successful organizational change.
- "A KPI should tell you what action needs to take place." This underscores the actionable nature of KPIs, which should guide decision-making and prompt immediate corrective actions.
- "Measurement initiatives are often viewed as managerial control devices and solely for the benefit of management." This quote reflects the common skepticism towards performance measurement and the need for a more inclusive approach.
How does David Parmenter define KPIs in "Key Performance Indicators"?
- Nonfinancial Measures: KPIs are nonfinancial measures that are not expressed in monetary terms.
- Frequent Measurement: They are measured frequently, often daily or 24/7, to provide timely insights.
- Actionable: KPIs should prompt immediate action by the CEO and senior management team.
- Significant Impact: They have a significant impact on the organization, affecting multiple critical success factors and perspectives.
What is the 12-step model for implementing KPIs in "Key Performance Indicators"?
- Senior Management Commitment: The first step involves securing commitment from the senior management team.
- Establishing a KPI Team: Form a dedicated team to lead the KPI development and implementation process.
- Just Do It Culture: Foster a culture that encourages action and avoids over-analysis.
- Holistic Strategy: Develop a comprehensive strategy that integrates KPIs with the organization's overall goals and initiatives.
What are the four foundation stones for KPI development in "Key Performance Indicators"?
- Partnership: Establish effective partnerships with staff, unions, key suppliers, and customers.
- Empowerment: Empower employees, especially those on the front line, to take immediate action.
- Integration: Integrate measurement, reporting, and performance improvement into a cohesive framework.
- Strategic Linkage: Ensure that performance measures are linked to the organization's strategy and critical success factors.
How does "Key Performance Indicators" by David Parmenter address common pitfalls in KPI implementation?
- Avoid Overcomplication: The book advises against overcomplicating the KPI development process and encourages a "just do it" approach.
- Focus on CSFs: Emphasizes the importance of identifying and focusing on critical success factors to ensure relevant KPIs.
- Continuous Improvement: Encourages regular review and refinement of KPIs to maintain their relevance and effectiveness.
- Stakeholder Engagement: Stresses the need for stakeholder engagement and communication throughout the KPI implementation process.
What role does strategic planning play in KPI development according to "Key Performance Indicators"?
- Alignment with Strategy: KPIs should be aligned with the organization's strategic objectives to ensure they drive desired outcomes.
- CSF Identification: Strategic planning helps identify critical success factors that are essential for KPI development.
- Holistic Approach: A well-constructed strategy provides a holistic framework for integrating KPIs with other organizational initiatives.
- Continuous Review: Regular strategic planning cycles allow for the review and adjustment of KPIs to reflect changing priorities.
How does "Key Performance Indicators" suggest organizations handle resistance to performance measurement?
- Address Concerns: Acknowledge and address employee concerns about performance measurement being used for control or discipline.
- Inclusive Process: Involve employees in the KPI development process to foster ownership and acceptance.
- Clear Communication: Clearly communicate the purpose and benefits of KPIs to all stakeholders.
- Training and Support: Provide training and support to help employees understand and effectively use KPIs.
What is the significance of the 10/80/10 rule in "Key Performance Indicators"?
- Balanced Approach: The rule suggests having about 10 KRIs, up to 80 PIs, and 10 KPIs for a balanced performance measurement system.
- Focus on Key Measures: Encourages organizations to focus on a limited number of truly impactful KPIs.
- Avoid Overload: Helps prevent information overload by limiting the number of performance measures.
- Prioritization: Ensures that the most critical measures receive the necessary attention and resources.
How does "Key Performance Indicators" recommend organizations report performance measures?
- Timely Reporting: Emphasizes the importance of timely reporting, with KPIs being reported daily or even 24/7.
- Dashboard for the Board: Suggests using a concise dashboard to report key result indicators to the board.
- Decision-Based Reporting: Encourages decision-based reporting that supports timely action and improvement.
- Use of Technology: Recommends leveraging technology, such as intranet-based reporting, for efficient and accessible performance measurement.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.