Corporate Performance: The Complete Guide to Measuring, Managing and Improving Organisational Performance...

Hope all are good and well...

Corporate Performance: The Complete Guide to Measuring, Managing and Improving Organisational Performance

Need a consultant/analyst/expert/manager to take care of your planning and reporting the way it should be? Drop a message and let's talk about your role/project.

Listen @ www.paper2audio.com/d/Pw54gmLl
FAQ on me & my cv/resumé on a page: click here

Musab Qureshi

Emails: musabquk@hotmail.com / mail@musab.co.uk
WhatsApp: +44 7857 709 573

About me: click here

#Musab #Analyst #Consultant #Expert #YouNeedMusab #Reports #AReportIsWorthAThousandWords #CorporatePerformance #PerformanceManagement #BusinessPerformance #KPI #KPIs #OKRs #Report #Dashboard #PerformanceMeasurement #BusinessIntelligence #BI #AI

1. Foundations of Corporate Performance

1.1 What is Corporate Performance?

Corporate performance is the overall assessment of how effectively an organisation is achieving its objectives and producing the results it is intended to achieve.

It provides a structured way of understanding whether an organisation is performing as expected, where performance is strong, where weaknesses exist and what needs to change.

Corporate performance is broader than any individual measure. An organisation can perform well in one area while experiencing significant problems in another. Customer satisfaction may be strong while service response times are deteriorating. Employee engagement may be improving while process quality is declining. Technology availability may be high while unresolved operational issues continue to increase.

Corporate performance therefore needs to be viewed as a multidimensional concept.

It can include customer performance, workforce performance, operational performance, process performance, service performance, quality, risk, compliance, technology, projects, programmes, suppliers and organisational capability.

The exact dimensions depend on the organisation's strategy, operating model, objectives and operating environment.

Understanding Performance

A performance measure is a defined way of assessing an aspect of performance.

A metric is a quantified measurement used to describe or monitor something.

An indicator is information that provides evidence about a condition, trend or result.

A Key Performance Indicator (KPI) is an important measure used to assess progress towards a significant objective or desired result.

These terms are related but are not identical.

An organisation may collect hundreds or thousands of measurements. Only some of them should normally be treated as KPIs.

The purpose of a KPI is to draw attention to something that matters.

A useful KPI should therefore have a clear relationship with an organisational objective, provide meaningful evidence and support management action.

Corporate Performance Begins With Purpose

Performance measurement should not begin with the question:

What data do we have?

It should begin with:

What are we trying to achieve?

This distinction is fundamental.

If an organisation starts with its available data, it can easily end up measuring what is convenient rather than what is important.

A stronger approach begins by understanding:

What the organisation is trying to achieve
Which results matter most
Which objectives support those results
Which factors influence performance
What evidence is required
Who is responsible for performance
What decisions the information should support
What action should occur when performance is below expectation

This creates the foundation for an effective corporate performance system.

The Corporate Performance Chain

Corporate performance can be understood as a connected management chain:

Strategy → Objectives → Measures → KPIs → Targets → Data → Analysis → Decisions → Actions → Outcomes

Each element has a different purpose.

Strategy establishes the direction.

Objectives define what the organisation intends to achieve.

Measures establish how performance will be assessed.

KPIs identify the measures that matter most.

Targets establish the expected level of performance.

Data provides the evidence.

Analysis explains what the evidence means.

Decisions determine what should happen.

Actions implement those decisions.

Outcomes demonstrate whether the organisation ultimately achieved the intended result.

A weakness at any stage can undermine the entire system.

Excellent analysis cannot compensate for unreliable data. Reliable data cannot compensate for poorly designed KPIs. Good KPIs cannot compensate for unclear objectives. Clear objectives cannot produce results if management takes no action when performance deteriorates.

Corporate performance is therefore a system rather than a collection of individual measurements.

Corporate Performance Is More Than Measurement

Performance measurement and performance management are closely related but different.

Performance measurement is concerned with collecting and assessing evidence.

Performance management is concerned with using that evidence to understand performance, make decisions and improve results.

An organisation can have an impressive measurement system without having effective performance management.

It may have hundreds of KPIs, sophisticated dashboards, automated reports, large quantities of data and regular performance meetings.

Yet performance may remain poor if nobody understands the information or takes appropriate action.

This leads to an important principle:

Measurement provides evidence. Management turns evidence into decisions and action.

The objective is therefore not to maximise the amount of measurement.

The objective is to obtain the right information at the right time so that the right people can make better decisions.

The Multiple Dimensions of Performance

Corporate performance normally consists of several interconnected dimensions.

These may include:

Customer performance: How customers and service users experience the organisation
People performance: Workforce capability, engagement, capacity and effectiveness
Process performance: How effectively organisational processes operate
Service performance: Whether services meet defined expectations
Quality performance: Whether outputs meet required standards
Risk performance: Whether significant risks are identified and managed
Compliance performance: Whether applicable requirements are being met
Technology performance: Whether technology supports reliable operations
Project performance: Whether projects deliver their intended outputs and outcomes
Programme performance: Whether coordinated initiatives achieve broader organisational results
Supplier performance: Whether suppliers and vendors meet agreed requirements
Capability performance: Whether the organisation has the capabilities required to achieve its objectives

These dimensions should not be treated as completely independent.

They interact continuously.

Poor technology performance can disrupt processes.

Poor processes can reduce service quality.

Poor service quality can damage customer experience.

Insufficient workforce capability can affect quality, productivity and operational resilience.

Weak governance can allow problems across several dimensions to remain unresolved.

Corporate performance measurement therefore needs both individual visibility and an integrated organisational view.

Strategic, Tactical and Operational Performance

Performance exists at different organisational levels.

Strategic performance concerns progress towards major organisational objectives and strategic priorities.

Tactical performance concerns the performance of departments, functions, programmes, business areas and other organisational units responsible for translating strategy into practical activity.

Operational performance concerns the day-to-day delivery of processes, services and activities.

These levels should connect.

For example:

Strategic objective: Improve customer experience

Tactical objective: Improve service responsiveness

Operational measures: Response time, resolution time, backlog and service availability

The operational measures provide evidence that can support tactical management.

Tactical performance then contributes to understanding whether the strategic objective is being achieved.

This creates a performance hierarchy:

Corporate → Functional → Process → Operational

The hierarchy should not mean that every measure is automatically cascaded downwards. Each level should contain measures that are relevant to the decisions and responsibilities of that level.

Performance in Greenfield and Mature Organisations

Corporate performance measurement looks different in a greenfield environment compared with a mature environment.

A greenfield environment is one where a performance framework is being established from the beginning or undergoing fundamental redesign.

There may be no agreed KPI catalogue, performance dictionary, dashboard structure, governance model or established review cycle.

A mature environment may already have extensive reporting, dashboards, KPIs, data platforms, governance arrangements and performance review processes.

However, maturity does not automatically mean effectiveness.

A mature organisation may still have:

Too many KPIs
Poorly defined measures
Conflicting indicators
Unreliable data
Duplicate reports
Outdated dashboards
Weak ownership
Limited analysis
Excessive manual reporting
Poor connections between measurement and decision-making

The performance professional therefore needs to assess not merely whether a performance system exists but whether it actually works.

The Five Fundamental Performance Questions

A good corporate performance framework should help management answer five fundamental questions:

1. Where are we now?

This requires reliable information about current performance.

2. Where do we need to be?

This requires clear objectives, targets and expected outcomes.

3. What is the gap?

This requires comparison between actual performance and the desired position.

4. Why does the gap exist?

This requires analysis, investigation and root-cause assessment.

5. What should we do about it?

This requires management judgement, decisions, ownership and action.

The first three questions are primarily measurement questions.

The fourth is an analytical question.

The fifth is a management question.

A mature corporate performance system connects all five.

The Ultimate Purpose of Corporate Performance

The purpose of corporate performance measurement is not measurement itself.

It is better organisational understanding, better decisions and sustained improvement.

A useful performance system helps an organisation understand what is happening, why it is happening, what is likely to happen next and what action should be taken.

This creates a continuous cycle:

Measure → Understand → Decide → Act → Monitor → Improve

When this cycle operates effectively, performance information becomes an active management capability rather than a reporting exercise.

The central principle of corporate performance is therefore simple:

Measure what matters, understand what the evidence means, take appropriate action and continually assess whether that action produces the intended improvement.

1.2 Performance, Productivity, Efficiency and Effectiveness

The words performance, productivity, efficiency and effectiveness are often used interchangeably. They are related concepts but they describe different aspects of organisational performance.

Understanding the distinction is essential because an organisation can be efficient without being effective, productive without achieving the intended outcome or highly active without actually performing well.

A strong corporate performance framework therefore needs to define these terms clearly before deciding what to measure.

Performance

Performance is the extent to which an organisation, team, process, service, project or individual achieves its intended objectives and results.

Performance is therefore a broad concept.

It can include:

What was achieved
How well it was achieved
How consistently it was achieved
How efficiently resources were used
Whether requirements were met
Whether customers received the intended service
Whether risks were controlled
Whether the intended outcomes were produced

Performance should therefore not be reduced to a single dimension.

Productivity

Productivity concerns the relationship between outputs and the resources used to produce those outputs.

In simple terms:

Productivity = Useful Output ÷ Resources Used

Resources can include employee time, processing capacity, technology capacity, physical resources and organisational effort.

Productivity is useful when an organisation wants to understand how effectively available capacity is being converted into useful output.

However, productivity measures need to be designed carefully.

Consider a service team that processes 1,000 requests during a reporting period.

That figure tells us something about activity.

It does not necessarily tell us whether the requests were processed correctly, whether customers received the intended outcome or whether significant rework was required.

Productivity should therefore be considered alongside quality and outcomes.

Efficiency

Efficiency concerns how well resources are used to produce a required output.

An efficient process minimises unnecessary time, effort, resources, duplication, delay and waste while still meeting the required standard.

Efficiency questions include:

How much effort is required?
How long does the process take?
How many steps are involved?
How much rework occurs?
How much waiting time exists?
Are resources being used appropriately?
Are unnecessary activities being performed?

Efficiency is therefore primarily concerned with how the work is performed.

Effectiveness

Effectiveness concerns whether the intended result is actually achieved.

An organisation can complete activities efficiently while failing to achieve the desired outcome.

For example, a service team might process requests very quickly but fail to resolve the underlying customer problems.

The process could therefore be efficient but ineffective.

Effectiveness asks:

Did we achieve the objective?
Did we produce the intended outcome?
Did the service solve the customer's problem?
Did the process achieve its purpose?
Did the initiative produce the intended improvement?

This makes effectiveness particularly important at strategic and outcome levels.

Efficiency and Effectiveness Together

Efficiency and effectiveness should normally be considered together.

A useful way to express the distinction is:

Efficiency asks: "Are we doing things right?"

Effectiveness asks: "Are we doing the right things?"

An organisation needs both.

Excessive focus on efficiency can lead to local optimisation where individual activities become faster but the overall outcome deteriorates.

Excessive focus on effectiveness without considering efficiency can create unnecessary complexity, excessive effort or unsustainable processes.

The objective is therefore to achieve effective outcomes through efficient and controlled processes.

Outputs and Outcomes

An output is something directly produced by an activity or process.

An outcome is the result or change produced by those outputs.

For example:

Activity: Process service requests

Output: Requests completed

Outcome: Customers receive the required service successfully

The distinction matters because organisations often measure outputs more easily than outcomes.

Counting completed requests is straightforward.

Determining whether those requests produced the intended result may require additional analysis.

This can create a common performance problem:

High activity is mistaken for high performance.

An organisation should therefore ask whether its measures demonstrate meaningful outcomes rather than simply showing that work took place.

The Performance Chain

The relationship can be represented as:

Inputs → Activities → Outputs → Outcomes → Impact

Inputs are the resources required to perform the work.

Activities are the actions performed.

Outputs are the immediate products or services produced.

Outcomes are the results experienced by customers, employees or the organisation.

Impact represents the broader effect produced over time.

Not every performance framework needs to measure all five levels separately. However, understanding the chain helps identify where measures sit and prevents activity measures from being confused with outcome measures.

Value and Performance

Value refers to the benefit or usefulness created by an activity, process, service or outcome relative to the needs of those who receive or depend upon it.

Value is therefore closely connected to effectiveness.

A process may be highly efficient but produce little useful value if it is performing work that does not contribute meaningfully to the intended objective.

Performance professionals should therefore consider whether activities are contributing to meaningful organisational outcomes.

Why the Distinctions Matter

These concepts provide different lenses through which performance can be understood.

Performance provides the broad organisational view.

Productivity examines the relationship between useful output and resources.

Efficiency examines how effectively resources and processes are used.

Effectiveness examines whether intended results are achieved.

A comprehensive performance framework should use these concepts together rather than treating one as a substitute for the others.

The central principle is:

Do not confuse doing more work with performing better. Measure the efficiency of the process, the quality of the output and the effectiveness of the resulting outcome.

1.3 Strategy and Performance

Corporate performance begins with strategy because an organisation cannot meaningfully determine whether it is performing well without understanding what it is trying to achieve.

Strategy is the organisation's chosen direction and approach for achieving its long-term objectives.

Strategy provides context for performance measurement.

Without strategy, organisations can easily create large numbers of measures without knowing which ones matter most.

Vision

A vision describes the future state an organisation wants to achieve.

It provides a long-term direction and helps establish what the organisation ultimately wants to become or accomplish.

Performance measures should support progress towards that desired future state.

Mission

A mission describes the fundamental purpose of an organisation and why it exists.

The mission helps define the organisation's core role.

Performance measurement should therefore consider whether the organisation is effectively fulfilling that purpose.

Values

Values are the principles that guide how an organisation behaves and makes decisions.

Values can influence performance expectations because an organisation may care not only about what is achieved but also about how it is achieved.

Performance frameworks should therefore avoid creating measures that encourage behaviour inconsistent with organisational values.

Strategic Priorities

Strategic priorities are the areas that receive particular organisational attention because they are considered important to achieving strategic objectives.

Priorities help focus resources, management attention and organisational effort.

A priority should normally have a clear relationship with one or more objectives.

Strategic Objectives

A strategic objective is a defined result that the organisation intends to achieve in support of its strategy.

Objectives convert broad strategic direction into something that can be managed and assessed.

For example:

Strategic priority: Improve customer experience

Strategic objective: Reduce unnecessary customer effort across key service journeys

The objective is more specific than the priority and provides a stronger basis for defining measures.

Strategic Initiatives

A strategic initiative is a significant programme of activity established to help achieve one or more strategic objectives.

Examples may include:

Service transformation
Process redesign
Technology transformation
Workforce capability development
Customer journey improvement
Organisational redesign

The important point is that an initiative should exist because it contributes to an objective.

Performance measurement should therefore assess both initiative delivery and whether the initiative is contributing to the intended organisational outcome.

Strategy Cascading

Strategy cascading is the process of translating high-level organisational strategy into objectives and priorities for departments, functions, teams and operational areas.

The principle can be represented as:

Corporate strategy → Strategic objectives → Functional objectives → Team objectives → Operational activities

Effective cascading creates alignment.

However, cascading does not mean simply copying the same objectives at every level.

Different organisational units may contribute to the same strategic objective in different ways.

For example, a customer experience objective may involve:

Customer service improving response and resolution
Technology improving service availability
Process teams removing unnecessary steps
People teams developing required capabilities
Quality teams reducing recurring service failures

The objectives are connected but not identical.

Business Plans and Operating Plans

A business plan describes how an organisation or organisational unit intends to achieve defined objectives over a particular period.

An operating plan translates objectives into practical activities, responsibilities, resources, milestones and operational commitments.

These plans provide an important bridge between strategy and execution.

Performance measurement should therefore connect to the commitments contained within these plans.

Strategy Execution

Strategy execution is the process of turning strategic intentions into practical organisational action and measurable results.

This is where many performance frameworks face difficulty.

An organisation may have a clear strategy but fail to execute it effectively because of:

Unclear ownership
Conflicting priorities
Poor communication
Insufficient capability
Weak governance
Inadequate measurement
Poor coordination
Weak follow-through
Lack of management action

Performance measurement provides evidence about whether strategy is being translated into results.

Strategy and Measurement

The relationship can be represented as:

Vision → Mission → Strategy → Strategic Priorities → Strategic Objectives → Measures → KPIs → Targets → Initiatives → Activities → Outcomes

This relationship is fundamental.

A KPI should not exist simply because data is available.

It should exist because it provides meaningful evidence about something the organisation is trying to achieve or control.

This is why strategy should normally be understood before KPI design begins.

Strategic Alignment

Strategic alignment exists when organisational activities, objectives, measures and resources are connected to the organisation's strategic direction.

Alignment can be considered vertically and horizontally.

Vertical alignment connects corporate objectives with functions, teams and operational activities.

Horizontal alignment ensures that different organisational areas work together rather than pursuing conflicting objectives.

For example, one department should not be rewarded for improving its own performance if doing so creates significant problems for another department or damages the end-to-end customer journey.

Strategy as the Starting Point

A performance professional should therefore begin by asking:

What is the organisation's purpose?
What is its strategy?
What are its strategic priorities?
What objectives support those priorities?
What outcomes are expected?
What initiatives are intended to achieve them?
How will progress be measured?

These questions provide the foundation for the performance architecture that follows.

The central principle is:

Performance measurement should explain whether the organisation is successfully executing its strategy, not simply report what the organisation happens to be doing.

1.4 The Performance Chain

The performance chain describes the relationship between the resources an organisation uses, the activities it performs, the outputs it produces and the outcomes it achieves.

Understanding this chain is essential because performance problems often arise when organisations measure activity without understanding results.

The basic model is:

Inputs → Activities → Outputs → Outcomes → Impact

Each stage provides a different perspective.

Inputs

Inputs are the resources required to perform work.

Inputs may include:

People
Skills
Technology
Information
Facilities
Equipment
Capacity
Time
Organisational capability

Inputs are necessary but do not demonstrate performance by themselves.

Having highly capable people or sophisticated technology does not guarantee that the organisation will achieve its objectives.

Activities

Activities are the actions performed using available inputs.

Examples include:

Processing requests
Conducting inspections
Resolving incidents
Delivering training
Performing analysis
Completing project tasks
Reviewing information
Providing services

Activity measures can be useful for understanding workload and operational demand.

However, activity alone does not demonstrate successful performance.

Outputs

Outputs are the immediate products or services produced by activities.

Examples include:

Completed requests
Completed cases
Published reports
Delivered services
Completed projects
Processed applications
Completed assessments

Outputs are generally easier to measure than outcomes.

This is one reason organisations often overuse output measures.

Outcomes

Outcomes are the results produced by outputs.

They describe what changed as a consequence of the organisation's activities.

Examples include:

Improved customer experience
Reduced processing delays
Improved service quality
Increased workforce capability
Reduced recurring errors
Improved operational resilience
Greater process effectiveness

Outcomes are usually more meaningful than activity measures because they show whether the work achieved its intended purpose.

Impact

Impact describes the broader or longer-term effect resulting from organisational activity.

Impact may extend beyond the immediate outcome and may be influenced by several factors outside the organisation's direct control.

Impact measurement is therefore often more difficult than output measurement.

The important point is that not every organisation needs to measure impact for every activity. The appropriate level depends on the nature of the objective.

Performance Drivers

A performance driver is a factor that influences an important performance result.

For example, response time may be influenced by:

Workforce capacity
Demand volume
Process complexity
Technology performance
Number of handoffs
Approval requirements

These factors may not be the final outcome but can help explain why performance changes.

Understanding drivers is particularly important when analysing leading indicators.

Leading Indicators

A leading indicator provides information about factors that may influence future performance.

For example, a growing backlog may indicate that future response times are likely to deteriorate.

A decline in workforce capacity may indicate future operational pressure.

An increase in unresolved technology incidents may indicate potential future service disruption.

Leading indicators therefore provide an opportunity to intervene before a significant outcome deteriorates.

Lagging Indicators

A lagging indicator measures a result that has already occurred.

Examples include:

Customer satisfaction
Completed service outcomes
Defect rates
Final project outcomes
Resolution performance

Lagging indicators are valuable because they demonstrate actual results.

However, they often provide information after the opportunity for early intervention has passed.

This is why strong performance frameworks normally combine leading and lagging indicators.

Driver and Result Measures

The relationship can also be expressed as:

Drivers → Activities → Results

Driver measures help explain what influences performance.

Result measures show what actually happened.

A strong performance system should connect the two.

For example:

Driver: Backlog growth

Process: Request processing

Result: Increased resolution time

The driver may provide an early signal that the result will deteriorate.

Avoiding Activity-Based Performance

One of the most common performance measurement problems is treating activity as performance.

Consider a team that completes 10,000 transactions.

That is a significant volume of activity.

But questions remain:

Were the transactions correct?
Were they completed on time?
Did they meet requirements?
Did customers receive the intended outcome?
Was excessive rework required?
Did the activity address the actual demand?

Without these questions, the organisation may reward activity while overlooking effectiveness.

Building a Complete Performance Chain

A useful performance chain should connect:

Inputs → Activities → Outputs → Outcomes

And where appropriate:

Outcomes → Longer-Term Impact

The organisation should then identify the important measures at each stage.

This allows performance professionals to determine whether a problem originates from:

Insufficient inputs
Ineffective activities
Poor process design
Low-quality outputs
Weak outcomes
External factors

This is much more useful than looking at a single KPI in isolation.

The Importance of Causality

A performance chain suggests relationships but does not automatically prove causality.

Causality means that one factor contributes to producing a particular result.

For example, a reduction in processing time may occur at the same time as an increase in customer satisfaction.

That does not automatically prove that the reduction in processing time caused the improvement.

Other factors may have changed at the same time.

Performance professionals must therefore distinguish between:

What happened

and

Why it happened

The second question requires analysis.

The central principle is:

Do not measure only what the organisation does. Measure what it produces, what results from it and which factors drive those results.

1.5 Strategic, Tactical and Operational Performance

Corporate performance exists at multiple organisational levels. A complete performance system needs to distinguish between strategic, tactical and operational performance while ensuring that these levels remain connected.

The three levels have different purposes, different time horizons and different information requirements.

Strategic Performance

Strategic performance concerns whether the organisation is progressing towards its major strategic objectives.

Strategic performance normally has a longer time horizon and focuses on significant organisational outcomes.

Typical strategic questions include:

Are strategic objectives being achieved?
Are strategic priorities progressing?
Are major organisational outcomes improving?
Are strategic initiatives producing the intended results?
Are significant risks affecting strategy execution?
Is organisational capability developing as required?

Strategic performance information should therefore be concise, meaningful and focused on matters requiring senior management attention.

Tactical Performance

Tactical performance concerns the performance of functions, departments, business areas, programmes and other organisational units responsible for translating strategy into execution.

Tactical management sits between strategy and day-to-day operations.

Typical questions include:

Is the function contributing to strategic objectives?
Are departmental objectives being achieved?
Are processes performing as expected?
Are resources and capabilities sufficient?
Are operational problems affecting strategic objectives?
What interventions are required?

Tactical reporting normally contains more detail than strategic reporting.

Operational Performance

Operational performance concerns the day-to-day execution of processes and services.

Operational measures may include:

Response time
Resolution time
Backlog
Throughput
Availability
Quality
Error rates
Work volumes
Process cycle time
Service levels

Operational teams generally need more detailed and more frequent information than senior executives.

The Performance Hierarchy

The relationship can be represented as:

Strategic → Tactical → Operational

Strategic objectives provide direction.

Tactical objectives translate that direction into functional responsibilities.

Operational measures monitor day-to-day execution.

The three levels should connect without becoming identical.

Cascading Performance

Performance cascading is the process of translating higher-level objectives into relevant objectives and measures at lower organisational levels.

For example:

Corporate objective: Improve customer experience

Functional objective: Improve service responsiveness

Operational measures: Response time, resolution time, backlog and first-time-right performance

The operational measures help explain whether the functional objective is being achieved.

The functional objective contributes to the corporate objective.

This creates a logical connection between organisational levels.

Avoiding Mechanical Cascading

Cascading should not mean giving every team exactly the same KPIs.

Different teams may contribute to the same strategic objective in different ways.

A technology team may influence service availability.

A process team may influence process complexity.

A customer service team may influence response and resolution.

A people team may influence workforce capability.

All may contribute to the same strategic outcome without sharing identical measures.

Time Horizons

The three levels also tend to have different time horizons.

Strategic performance often considers longer-term progression.

Tactical performance may focus on medium-term delivery and capability.

Operational performance may focus on immediate or short-cycle performance.

However, these boundaries are not absolute.

A strategic problem can require immediate action.

An operational issue can become a strategic concern if it persists or affects critical objectives.

Different Audiences Need Different Information

Performance information should be designed for its intended audience.

Senior executives generally need:

Strategic objectives
Key results
Major trends
Significant exceptions
Major risks
Decisions required

Managers may need:

Functional objectives
KPI performance
Variances
Root causes
Actions
Dependencies
Forecasts

Operational teams may need:

Current workload
Process performance
Backlogs
Exceptions
Service levels
Individual process stages
Immediate actions

A single dashboard rarely serves all three audiences equally well.

Connecting the Levels

An effective performance architecture should allow management to move from one level to another.

For example:

Strategic view: Customer experience is deteriorating

↓

Tactical view: Service responsiveness is below expectation

↓

Operational view: Resolution backlog has increased

↓

Diagnostic view: A particular process stage has become a bottleneck

This drill-down allows management to move from symptom to potential cause.

Avoiding Information Overload

Strategic users do not normally need every operational measure.

Equally, operational teams may need detailed information that would be unnecessary at executive level.

This creates a principle of information relevance.

Each level should receive the information necessary to make the decisions for which it is responsible.

Accountability Across Levels

Performance should also have clear ownership at each level.

Strategic objectives need strategic owners.

Functional objectives need functional owners.

Operational measures need operational owners.

This does not mean one person controls every factor affecting performance.

It means responsibility for monitoring, investigating and taking appropriate action is clearly established.

The central principle is:

Strategic, tactical and operational performance should be measured at the level where decisions are made while remaining connected through a clear organisational performance hierarchy.

1.6 Performance Management and Performance Measurement

Performance measurement and performance management are fundamental concepts within corporate performance, but they are not the same thing.

Performance measurement provides evidence.

Performance management uses that evidence to understand performance, make decisions, take action and improve organisational results.

Confusing these concepts can result in organisations producing large quantities of performance information without actually improving performance.

What is Performance Measurement?

Performance measurement is the systematic process of defining measures, collecting data, calculating results and assessing performance against expectations.

It normally involves:

Defining what should be measured
Establishing measurement definitions
Identifying data sources
Collecting data
Validating data
Calculating measures
Comparing results
Reporting performance
Monitoring trends

Performance measurement therefore creates the evidence base for management.

What is Performance Management?

Performance management is the broader discipline of using performance information to manage organisational results.

It includes:

Setting objectives
Defining measures
Establishing targets
Monitoring performance
Analysing results
Reviewing performance
Making decisions
Taking corrective action
Tracking improvement
Learning from results

Performance management therefore includes measurement but goes beyond it.

The Performance Management Cycle

A useful performance management cycle is:

Plan → Define → Measure → Collect → Analyse → Review → Decide → Act → Monitor → Improve

Plan establishes what the organisation wants to achieve.

Define establishes objectives, measures and targets.

Measure determines actual performance.

Collect gathers the required evidence.

Analyse examines trends, gaps, relationships and causes.

Review brings relevant people together to assess performance.

Decide determines what action is required.

Act implements the agreed intervention.

Monitor determines whether the intervention is producing the intended effect.

Improve strengthens the organisation's performance and its performance-management system.

This cycle should operate continuously.

Performance Measurement Without Management

An organisation can measure extensively without managing performance effectively.

Common symptoms include:

Large numbers of reports
Extensive KPI libraries
Frequent dashboard production
Regular data collection
Limited analysis
Repeated discussion of the same problems
Few completed actions
Weak ownership
Little evidence of improvement

This is sometimes described as reporting for reporting's sake.

The existence of a report does not demonstrate effective performance management.

Performance Management Without Good Measurement

The opposite problem also exists.

Managers may recognise that performance is poor but lack reliable evidence to understand the situation.

Without good measurement, management may rely excessively on:

Anecdotes
Individual opinions
Incomplete information
Assumptions
Historical perceptions
Isolated incidents

Good performance management therefore requires a reliable evidence base.

Evidence-Based Management

Evidence-based management means making management decisions using reliable information and relevant evidence rather than relying solely on assumption or intuition.

This does not mean that judgement is unnecessary.

Management judgement remains essential because performance data rarely explains everything.

The objective is to combine:

Evidence + Analysis + Experience + Context + Judgement

This produces stronger decisions than any one component alone.

Performance Reviews

A performance review is a structured management discussion in which performance information is examined and decisions are made.

A useful review should consider:

What happened?
What changed?
Is performance within the expected range?
What explains the change?
What are the implications?
What risks are emerging?
What decisions are required?
What actions should be taken?
Who owns each action?
When will the result be reviewed?

This prevents meetings from becoming simple readings of dashboard figures.

Corrective Action

Corrective action is action taken to address an identified performance problem.

Corrective action should ideally address the underlying cause rather than merely treating the visible symptom.

For example, if a backlog has increased, simply asking employees to process more work may temporarily reduce the backlog.

A stronger approach may investigate:

Demand patterns
Process bottlenecks
Capacity
Technology
Rework
Approval delays
Skills
Workflow design

The intervention should be based on evidence.

Continuous Improvement

Performance management should create a continuous improvement cycle.

After action has been taken, the organisation should determine whether performance actually improved.

This creates:

Measure → Analyse → Act → Re-measure → Learn

If the intervention worked, the organisation should understand why.

If it did not work, the organisation should determine what needs to change.

This learning process is an essential part of mature performance management.

The Difference in One Sentence

The distinction can be summarised simply:

Performance measurement tells you what is happening. Performance management determines what to do about it.

Both are necessary.

A sophisticated measurement system without management action creates information without improvement.

Management action without reliable measurement creates decisions without sufficient evidence.

The central principle is:

Build measurement into a management cycle so that information leads to understanding, understanding leads to decisions and decisions lead to measurable improvement.

1.7 Accountability, Culture and the Principles of Effective Performance

Corporate performance is not purely a technical discipline.

An organisation can have excellent KPIs, dashboards, data platforms and reporting processes yet still struggle to improve if accountability is weak or the organisational culture discourages transparency.

Performance systems operate within human and organisational environments.

The way people respond to performance information can therefore be just as important as the measurement system itself.

Accountability

Accountability is the obligation to explain performance, decisions and results within an assigned area of responsibility.

Accountability does not necessarily mean that one person controls every factor affecting a result.

It means that responsibility for monitoring, understanding and responding to performance is clearly established.

For each important KPI, there should normally be clarity about:

Who owns the KPI
Who owns the data
Who produces the report
Who analyses the result
Who reviews the performance
Who can make decisions
Who is responsible for agreed actions

Without clear accountability, poor performance can remain unresolved because everyone assumes someone else is responsible.

Ownership

Performance ownership means that a person or organisational unit has clear responsibility for a defined aspect of performance.

The owner should understand:

What is being measured
Why it matters
How it is calculated
What influences it
What constitutes acceptable performance
What action is required when performance deteriorates

Ownership should be explicit rather than assumed.

Performance Culture

A performance culture is an organisational environment in which people understand objectives, take responsibility for results, use evidence, learn from performance information and act to improve.

A healthy performance culture encourages people to identify problems rather than conceal them.

It also recognises that poor performance information can be an opportunity for learning.

A mature organisation should be able to say:

"The measure is showing a problem. Let's understand why."

rather than:

"Who is to blame?"

Blame Culture

A blame culture exists when people are primarily concerned with avoiding responsibility or punishment rather than identifying and solving performance problems.

Blame can create several negative behaviours.

People may:

Hide problems
Delay escalation
Manipulate information
Avoid ownership
Focus on protecting themselves
Avoid experimentation
Report only positive information

This can seriously weaken the quality of management information.

A performance system should therefore create accountability without encouraging concealment.

KPI Gaming

KPI gaming occurs when people change their behaviour to improve a measured indicator without genuinely improving the underlying performance.

For example, if a team is measured only on response time, it may prioritise rapid acknowledgement while allowing resolution to deteriorate.

This is a classic example of why measures should be balanced.

The solution is not necessarily to abandon the KPI.

The solution may be to combine it with complementary measures such as:

Resolution time
Quality
Customer satisfaction
Rework
First-time-right performance

The objective is to reduce the possibility that improving one measure damages the wider outcome.

Transparency

Performance transparency means that relevant performance information is visible to the people who need it and can be understood in a consistent way.

Transparency supports:

Accountability
Early identification of problems
Better decision-making
Organisational learning
Consistent management action

However, transparency must be combined with appropriate governance.

Not every piece of information needs to be visible to every person.

The principle is to provide the right information to the right audience for the right purpose.

Evidence-Based Decision-Making

Effective performance cultures value evidence.

This does not mean ignoring professional judgement.

Instead, it means distinguishing between:

Fact: What the evidence demonstrates

Interpretation: What the evidence may mean

Assumption: What is believed but has not yet been demonstrated

Decision: What management chooses to do

Keeping these categories separate improves the quality of performance discussions.

Consistency

Performance information must be defined consistently.

If two departments calculate the same KPI differently, organisational comparisons become unreliable.

Consistency requires clear definitions covering:

KPI name
Purpose
Formula
Data source
Measurement unit
Reporting period
Inclusion rules
Exclusion rules
Ownership
Target
Threshold
Tolerance

This is why a KPI dictionary becomes an important component of a mature performance system.

Simplicity

A performance framework should be sufficiently comprehensive without becoming unnecessarily complicated.

Complexity can arise through:

Excessive KPIs
Multiple reporting layers
Unclear definitions
Duplicate measures
Complicated calculations
Excessive dashboards
Unnecessary reporting cycles

The objective is not to create the largest performance system.

It is to create a system that provides useful information and supports effective management.

Relevance

Every significant measure should have a reason for existing.

A useful test is:

If this measure changed significantly, would someone need to understand why and potentially take action?

If the answer is consistently no, the measure may not deserve to be a KPI.

This does not mean that every supporting metric must immediately be removed.

Operational measures can still be useful.

The important distinction is between supporting information and critical performance indicators.

Actionability

A measure is actionable when its results can lead to a meaningful management response.

Not every measure needs to be directly controllable by the organisation.

However, management should understand what can reasonably be done when the measure moves outside the expected range.

A KPI that changes regularly but produces no possible management response may have limited value.

Balance

A balanced performance system considers different perspectives rather than relying excessively on one type of measure.

This may include:

Leading and lagging measures
Input and outcome measures
Quantity and quality
Efficiency and effectiveness
Short-term and longer-term indicators
Internal and customer-facing measures
Current performance and future risk

Balance reduces the likelihood that management optimises one aspect of performance while damaging another.

The Principles of Effective Corporate Performance

The most important principles introduced in this chapter can be summarised as follows:

Start with organisational purpose and strategy
Measure what matters
Define every important measure clearly
Distinguish activity from performance
Measure both efficiency and effectiveness
Connect outputs with outcomes
Balance leading and lagging indicators
Establish clear ownership
Use reliable evidence
Analyse before acting
Connect performance information to decisions
Track actions to completion
Measure whether actions produced improvement
Encourage transparency
Avoid blame-driven performance management
Prevent KPI gaming
Keep the measurement system manageable
Review and improve the measurement system itself

The Foundation of the Entire Performance System

Corporate performance ultimately depends on the relationship between strategy, measurement, management and action.

The complete foundation can be represented as:

Purpose → Strategy → Objectives → Measures → KPIs → Targets → Data → Analysis → Review → Decision → Action → Outcome → Improvement

Each stage depends on the quality of the preceding stages.

If objectives are unclear, measures become confused.

If measures are poorly designed, KPIs become misleading.

If data is unreliable, analysis becomes questionable.

If analysis is weak, decisions become less informed.

If accountability is unclear, actions may not happen.

If actions are not evaluated, the organisation cannot determine whether performance actually improved.

Corporate performance is therefore not simply about measuring an organisation.

It is about creating a repeatable management system through which an organisation can understand its performance, respond to problems, learn from results and continually improve its ability to achieve its objectives.

2. Strategy, Objectives and Performance Frameworks

2.1 Goals, Objectives and Strategic Priorities

Corporate performance measurement becomes meaningful only when an organisation has clarity about what it is trying to achieve. Goals, objectives and strategic priorities provide the foundation for translating broad organisational direction into measurable performance expectations.

Without this foundation, organisations can easily create large collections of KPIs that measure activity without demonstrating whether important objectives are being achieved.

Goals

A goal is a broad statement describing something an organisation wants to achieve.

Goals provide direction but may not always contain enough detail to be measured directly.

For example:

Goal: Improve customer experience.

This establishes a clear direction but does not yet explain precisely what improvement means, how it will be measured or when the desired result should be achieved.

A goal therefore normally needs to be translated into more specific objectives.

Objectives

An objective is a defined result that an organisation intends to achieve.

Objectives are more specific than broad goals and provide a stronger basis for performance measurement.

For example:

Goal: Improve customer experience.

Objective: Reduce unnecessary customer effort across priority service journeys.

The objective provides a clearer basis for identifying appropriate measures.

A good objective should make it possible to determine:

What needs to change
What result is expected
Who is responsible
How progress will be assessed
When the result should be achieved

Strategic Objectives

A strategic objective is an important organisational objective that contributes directly to the execution of strategy.

Strategic objectives normally address significant organisational outcomes rather than routine activities.

Examples include:

Improve customer experience
Strengthen operational resilience
Improve service quality
Increase organisational capability
Reduce process complexity
Improve technology reliability
Strengthen compliance performance
Improve workforce engagement

The specific objectives will depend on the organisation's strategy.

Tactical Objectives

A tactical objective translates strategic direction into a more specific objective for a function, department, programme or business area.

For example:

Strategic objective: Improve customer experience.

Tactical objective: Improve service responsiveness across priority customer journeys.

The tactical objective provides a bridge between strategy and operational activity.

Operational Objectives

An operational objective describes a specific result expected from a process, service or operational team.

For example:

Tactical objective: Improve service responsiveness.

Operational objective: Reduce average resolution time for priority service requests.

Operational objectives are usually closer to day-to-day activities and therefore tend to have more frequent measurement cycles.

Strategic Priorities

A strategic priority is an area that receives particular organisational attention because it is important to achieving strategic objectives.

An organisation may have many objectives but only a smaller number of strategic priorities.

Priorities help management determine where attention and organisational effort should be concentrated.

For example:

Strategic Priority: Customer experience.

This priority could contain several objectives relating to:

Customer satisfaction
Customer effort
Service quality
Response time
Resolution effectiveness
Customer journey performance

The priority provides the organising theme while the objectives define the specific results to be achieved.

Outcomes and Outputs

Objectives should distinguish between outputs and outcomes.

An output is something directly produced by an activity.

An outcome is the result produced by those outputs.

For example:

Output: New customer-service process implemented.

Outcome: Customers experience fewer unnecessary steps when requesting the service.

The output demonstrates delivery.

The outcome demonstrates whether the delivery created the intended result.

Performance frameworks should therefore avoid defining objectives entirely around completed activities.

Objective Ownership

Every significant objective should have a clear owner.

An objective owner is the person or organisational unit accountable for monitoring progress and coordinating action towards the objective.

Ownership does not mean that one individual personally performs every activity required to achieve the objective.

It means that accountability for the overall result is clear.

An objective without clear ownership can easily become an objective that everyone supports in principle but nobody actively manages.

Objective Hierarchy

A useful organisational hierarchy is:

Vision → Mission → Strategy → Strategic Priorities → Strategic Objectives → Tactical Objectives → Operational Objectives → Activities

This hierarchy creates a logical relationship between organisational direction and day-to-day work.

However, the relationship should not become excessively bureaucratic.

Not every operational activity needs to be traced through a long chain of documentation.

The purpose of the hierarchy is to establish meaningful alignment.

Prioritisation

Objective prioritisation is the process of determining which objectives require the greatest organisational focus.

Prioritisation can consider:

Strategic importance
Customer impact
Organisational risk
Regulatory importance
Operational significance
Dependencies
Urgency
Organisational capability
Complexity
Expected improvement

Prioritisation prevents performance management from becoming an exercise in treating every objective as equally important.

Objectives and Performance Measurement

Once objectives have been defined, the organisation can determine how progress will be measured.

The relationship is:

Objective → Measure → KPI → Target → Data → Analysis

For example:

Objective: Improve service responsiveness.

Measure: Average resolution time.

KPI: Average resolution time for priority requests.

Target: Defined acceptable resolution level.

Data: Service management system.

Analysis: Actual performance, trend, variance and root causes.

This provides a clear line of sight from organisational intent to measurable evidence.

Common Problems With Objectives

Poorly designed objectives can create problems throughout the performance system.

Common problems include:

Objectives that are too vague
Objectives that describe activities rather than results
Too many objectives
Objectives with no clear owner
Objectives that conflict with each other
Objectives that cannot realistically be measured
Objectives disconnected from strategy
Objectives that lack a defined timeframe
Objectives that are never reviewed

The quality of the objective directly affects the quality of the measurement system.

The central principle is:

Goals provide direction. Priorities provide focus. Objectives define the results. Measures provide evidence.

2.2 Designing Effective Objectives

Once an organisation has established its goals, strategic priorities and intended outcomes, the next challenge is to translate them into well-designed objectives.

An objective should provide enough clarity for people to understand what needs to be achieved, enough precision for performance to be measured and enough context for management to determine whether progress is satisfactory.

Poor objectives create poor performance measurement.

If an objective is vague, the associated KPI is likely to be vague. If an objective describes activity rather than a result, the organisation may end up measuring activity instead of performance. If an objective is impossible to measure, management may struggle to determine whether it has been achieved.

What Makes an Objective Effective?

An effective objective should normally be:

Relevant to organisational strategy
Clearly worded
Outcome-focused where appropriate
Measurable
Assigned to an owner
Time-bound where appropriate
Realistic
Sufficiently challenging
Understandable to the people responsible for delivery

The objective should also describe a meaningful result rather than simply describing an activity.

Compare:

Weak objective: Implement a new customer service system.

Stronger objective: Improve customer service responsiveness through a redesigned service management capability.

The first describes an activity.

The second describes the intended organisational improvement.

SMART Objectives

One of the best-known approaches to objective design is the SMART framework.

SMART commonly stands for:

Specific: The objective clearly states what needs to be achieved.

Measurable: There is a way to determine progress or achievement.

Achievable: The objective can reasonably be pursued within the relevant circumstances.

Relevant: The objective contributes to organisational priorities.

Time-bound: There is a defined timeframe where appropriate.

SMART objectives can be useful because they encourage clarity.

However, SMART should not become a mechanical exercise.

An objective can satisfy the letters of SMART while still being strategically unimportant.

The first question should always remain:

Does this objective matter?

Specific Objectives

A specific objective provides sufficient detail to establish what is expected.

For example:

Vague: Improve service.

Specific: Improve the responsiveness and resolution of priority customer service requests.

The second objective provides a clearer direction for measurement.

Specificity reduces ambiguity between teams and makes performance discussions more consistent.

Measurable Objectives

A measurable objective has an identifiable way of determining whether progress is being made.

Measurement may involve:

Quantity
Quality
Time
Percentage
Rate
Frequency
Satisfaction
Capability
Compliance
Outcome achievement

Not every objective needs to be reduced to one numerical measure.

Some objectives require a combination of quantitative and qualitative evidence.

For example, organisational capability may require assessment against defined capability criteria rather than a single numerical value.

Outcome Objectives

An outcome objective focuses on the result the organisation wants to achieve.

For example:

Outcome objective: Improve customer satisfaction with priority support services.

This is generally stronger than an activity-based objective such as:

Activity objective: Conduct customer service training.

Training may contribute to the desired outcome but does not demonstrate that the outcome has been achieved.

This distinction is critical throughout corporate performance management.

Output Objectives

An output objective focuses on something the organisation intends to produce or deliver.

For example:

Output objective: Implement a standardised customer support process across all service teams.

Output objectives are useful where delivery itself is important.

However, they should be complemented by outcome measures where the ultimate purpose of the output is to create an organisational improvement.

Leading Objectives

A leading objective focuses on a condition or driver that is expected to influence future performance.

For example:

Objective: Increase adoption of standardised service processes across operational teams.

This may act as a leading factor for future improvements in service quality and consistency.

Leading objectives can be particularly useful where management needs to influence future performance rather than simply measure historical results.

Lagging Objectives

A lagging objective focuses on an achieved result.

For example:

Objective: Improve customer satisfaction across priority services.

The objective concerns a result that can be assessed after performance has occurred.

A balanced framework should normally include both leading and lagging objectives where appropriate.

Prioritising Objectives

An organisation can easily create too many objectives.

When everything becomes a priority, nothing receives sufficient attention.

Objective prioritisation should therefore consider:

Strategic importance
Expected organisational impact
Customer impact
Risk
Urgency
Dependencies
Complexity
Available capability
Management capacity

Prioritisation also helps determine which objectives should receive executive attention and which can be managed at functional or operational levels.

Objectives Should Be Challenging but Credible

An objective should create meaningful improvement without becoming so unrealistic that it loses credibility.

A target that is obviously unattainable can encourage disengagement.

An objective that requires no meaningful improvement can create complacency.

The appropriate level depends on:

Current baseline
Organisational capability
Available capacity
External conditions
Required improvement
Strategic importance
Time available

The objective should stretch the organisation appropriately while remaining grounded in evidence.

Objectives Should Be Controllable Where Possible

An organisation should distinguish between factors it can directly control, factors it can influence and factors largely outside its control.

An objective that depends entirely on external circumstances can be difficult to manage.

This does not mean that organisations should avoid objectives involving external factors.

It means that the performance framework should identify the controllable drivers alongside the broader outcome.

For example:

Outcome: Improve customer satisfaction.

Influencing factors: Service quality, response time, resolution effectiveness and customer effort.

The organisation can manage these influencing factors even though it cannot directly control every aspect of customer perception.

Objective Dependencies

Objectives can depend on one another.

For example:

Objective A: Improve workforce capability.

Objective B: Standardise operational processes.

Objective C: Improve service quality.

Objectives A and B may contribute to achieving Objective C.

Understanding these relationships is important because delays in one objective can affect another.

A strategy map or objective dependency map can help make these relationships visible.

Common Objective Design Errors

Common problems include:

Writing objectives as activities
Using vague language
Creating too many objectives
Failing to identify ownership
Creating objectives without measures
Creating measures before defining the objective
Setting arbitrary timeframes
Setting unrealistic expectations
Creating conflicting objectives
Focusing exclusively on outputs
Ignoring outcomes
Failing to review objectives when circumstances change

A strong objective provides a stable direction while allowing the organisation to refine the associated measures as understanding improves.

The central principle is:

Design objectives around meaningful results, make them clear enough to measure and ensure they remain connected to organisational priorities.

2.3 Strategy Maps and Strategic Alignment

Once goals and objectives have been established, organisations need to understand how those objectives relate to one another.

A strategy map is a visual representation of strategic objectives and the relationships between them.

It helps answer an important question:

How do the different things we are trying to achieve contribute to the overall strategy?

What is a Strategy Map?

A strategy map normally displays strategic objectives in a logical structure.

The objectives are connected through relationships that describe how one capability or result can contribute to another.

For example:

Workforce capability → Better process performance → Improved service quality → Better customer experience

The map therefore provides a visual representation of strategic logic.

Strategic Themes

A strategic theme is a major area of strategic focus used to organise related objectives.

Examples might include:

Customer experience
Operational excellence
Digital capability
Workforce capability
Service quality
Organisational resilience

Strategic themes help organise complex strategies into understandable areas.

Cause-and-Effect Relationships

Strategy maps often use cause-and-effect relationships to describe how objectives are expected to influence one another.

For example:

Improved workforce capability

↓

Improved process execution

↓

Improved service quality

↓

Improved customer experience

These relationships represent strategic hypotheses.

They should not automatically be treated as proven causal relationships.

Performance analysis should test whether the expected relationship actually exists.

Vertical Alignment

Vertical alignment connects objectives at different organisational levels.

For example:

Corporate objective: Improve customer experience.

↓

Department objective: Improve service responsiveness.

↓

Team objective: Reduce priority request resolution time.

↓

Operational measure: Average resolution time.

This creates a line of sight from strategy to execution.

Horizontal Alignment

Horizontal alignment concerns coordination between organisational areas operating at the same level.

For example, improving customer experience may require coordination between:

Customer service
Technology
Operations
Process management
Quality
Workforce management

If each function optimises only its own objectives, the overall customer journey may not improve.

Horizontal alignment therefore helps prevent organisational silos.

Cascading Strategy

Strategy cascading translates organisational strategy into relevant objectives for functions, departments, teams and operational areas.

Effective cascading should preserve strategic intent while allowing each organisational unit to define its own appropriate contribution.

Cascading should not mean simply copying corporate objectives into every departmental plan.

Instead, each level should answer:

What does this part of the organisation need to achieve to contribute to the higher-level objective?

Alignment and Conflicting Objectives

Objectives can sometimes conflict.

For example:

One team may seek to reduce processing time
Another may prioritise quality controls
Another may prioritise customer effort reduction

If these objectives are managed independently, one improvement may create deterioration elsewhere.

Performance frameworks should therefore identify important trade-offs and dependencies.

The objective is not to eliminate every trade-off.

It is to make them visible so management can make informed decisions.

Strategy Maps and KPIs

A strategy map should eventually connect objectives to measures.

For example:

Strategic objective: Improve service quality

Supporting objective: Reduce recurring service failures

KPI: Repeat incident rate

Supporting indicator: First-time-right performance

This creates a connection between strategic intent and measurable evidence.

Strategy Maps and Communication

Strategy maps are also communication tools.

A well-designed strategy map can help employees understand:

Where the organisation is going
Which objectives matter
How objectives relate
How their work contributes
Which outcomes are important

This can improve strategic alignment because people can see the relationship between their activities and broader organisational objectives.

Avoiding Overcomplicated Strategy Maps

A strategy map should provide clarity.

An excessively complicated map containing dozens or hundreds of objectives can become difficult to understand.

The most important objectives and relationships should be visible.

Supporting detail can be maintained elsewhere in the performance architecture.

The central principle is:

A strategy map should make strategic logic visible by showing how important objectives connect and how organisational capabilities and activities are expected to contribute to desired outcomes.

2.4 Balanced Scorecard

The Balanced Scorecard is a strategic performance management framework designed to translate strategy into objectives, measures, targets and initiatives.

It is widely associated with Robert Kaplan and David Norton and was developed to encourage organisations to consider multiple dimensions of performance rather than relying on a narrow set of measures.

The central idea is balance.

An organisation should not judge its performance using only one type of information.

The Four Traditional Perspectives

The traditional Balanced Scorecard contains four perspectives:

Financial
Customer
Internal Process
Learning and Growth

For this article, the focus is deliberately on the non-financial dimensions of performance.

The customer perspective considers how customers experience the organisation.

The internal process perspective examines whether important organisational processes are operating effectively.

The learning and growth perspective considers the capabilities, people, knowledge and organisational infrastructure needed for sustained performance.

Customer Perspective

The customer perspective examines whether the organisation is delivering the experience and outcomes expected by its customers or service users.

Measures can include:

Customer satisfaction
Customer effort
Customer experience
Service quality
Complaints
Response time
Resolution time
Customer retention
Journey performance

The exact measures depend on organisational objectives.

Internal Process Perspective

The internal process perspective examines whether critical organisational processes are operating effectively.

Measures may include:

Process cycle time
First-time-right performance
Error rates
Rework
Process compliance
Throughput
Service levels
Process quality
Process efficiency

This perspective connects internal operational capability with customer outcomes.

Learning and Growth Perspective

The learning and growth perspective concerns the organisational capabilities required to sustain performance.

It can include:

Employee capability
Workforce skills
Employee engagement
Leadership capability
Knowledge management
Technology capability
Organisational learning
Improvement capability

These measures can act as leading indicators for future organisational performance.

Strategy Maps and the Balanced Scorecard

Strategy maps and Balanced Scorecards are closely related.

A strategy map shows how strategic objectives connect.

The Balanced Scorecard then translates those objectives into measurable performance.

The relationship can be represented as:

Strategy → Objectives → Strategy Map → Measures → KPIs → Targets → Initiatives

Balanced Performance

The word balanced is important.

An organisation should avoid creating a performance system that focuses excessively on one dimension while ignoring others.

For example, improving process speed should not automatically be considered successful if quality deteriorates.

Similarly, improving an internal process should not automatically be considered successful if customer experience worsens.

Balance encourages management to consider relationships and trade-offs.

Common Balanced Scorecard Problems

Common implementation problems include:

Treating the framework as merely a reporting template
Creating too many measures
Failing to connect measures to strategy
Selecting measures because data is readily available
Using measures without clear definitions
Failing to establish ownership
Treating the four perspectives as isolated silos
Focusing on measurement rather than management action

The Balanced Scorecard is most useful when it becomes part of the wider performance management cycle.

Using the Balanced Scorecard Today

The Balanced Scorecard should not be treated as a rigid template that every organisation must reproduce exactly.

Organisations can adapt its principles to their circumstances.

The essential concepts are:

Translate strategy into objectives
Establish relationships between objectives
Select meaningful measures
Define targets
Assign ownership
Monitor performance
Review results
Take action

The central principle is:

The Balanced Scorecard is valuable when it creates a balanced view of strategic performance and connects strategic objectives with measurable evidence and management action.

2.5 OKRs: Objectives and Key Results

OKR stands for Objectives and Key Results.

OKRs are a goal-setting and performance management approach used to define important objectives and identify measurable results that demonstrate progress towards those objectives.

The basic structure is:

Objective → Key Results

Objectives in OKRs

An Objective describes what the organisation, team or individual wants to achieve.

A strong OKR objective is normally:

Clear
Meaningful
Outcome-focused
Understandable
Directional
Time-bound within an agreed OKR cycle

For example:

Objective: Make the priority customer service journey significantly easier.

The objective provides direction.

Key Results

A Key Result is a measurable result that demonstrates progress towards the objective.

For example:

Objective: Make the priority customer service journey significantly easier.

Key Results:

Reduce average customer effort score by the agreed amount
Reduce the number of unnecessary journey steps
Increase successful first-contact resolution
Reduce repeat customer contacts

The Key Results provide evidence about whether the objective is being achieved.

OKRs and KPIs

OKRs and KPIs are related but different.

A KPI is an important performance indicator that is monitored over time.

An OKR is a structured objective and set of measurable results intended to drive focused achievement during a defined cycle.

A KPI might continue to be monitored for years.

An OKR may be established for a particular strategic or operational cycle and then replaced, revised or renewed.

KPIs answer:

How is an important area of performance behaving?

OKRs answer:

What important result are we trying to achieve and how will we know that we are progressing?

OKR Cycles

An OKR cycle is the defined period during which objectives and Key Results are established, monitored and reviewed.

The cycle may include:

Objective setting
Key Result definition
Alignment
Progress monitoring
Review
Reflection
Renewal or revision

Regular review helps teams identify whether progress is occurring and whether obstacles require management attention.

OKR Alignment

OKRs can support alignment across organisational levels.

For example:

Corporate Objective: Improve customer experience

↓

Function Objective: Simplify priority customer journeys

↓

Team Objective: Reduce unnecessary customer effort in the service process

The objectives should remain connected without requiring every team to copy the same wording.

OKR Scoring

Some organisations use numerical scoring to assess progress against Key Results.

Scoring can help create consistency when reviewing progress.

However, the score should not become more important than the underlying discussion.

A Key Result with a lower score may provide valuable information about obstacles, assumptions or changing circumstances.

The purpose of OKR scoring should therefore be to support learning and management rather than simply classify teams as successful or unsuccessful.

Common OKR Mistakes

Common mistakes include:

Creating too many objectives
Writing activities instead of outcomes
Creating Key Results that are not measurable
Using existing KPIs as though they are automatically OKRs
Setting objectives without clear ownership
Creating disconnected team objectives
Using excessive scoring
Focusing on completion rather than outcomes
Failing to review progress during the cycle

The quality of the Key Results is particularly important.

If the Key Results do not provide meaningful evidence, the OKR provides little value.

OKRs and Performance Management

OKRs work best when integrated with broader performance management rather than treated as a separate reporting exercise.

The relationship can be:

Strategy → Objective → Key Results → Actions → Measurement → Review → Learning

This makes OKRs particularly useful for translating strategic priorities into focused execution.

The central principle is:

An OKR should make an important objective clear and provide measurable evidence that shows whether meaningful progress is actually being made.

2.6 Other Performance Frameworks

The Balanced Scorecard and OKRs are only two approaches available to organisations.

Different organisations use different performance frameworks depending on their strategy, operating model, maturity, regulatory environment and management needs.

The objective is not to select a framework because it is fashionable.

The objective is to select or design an approach that helps the organisation manage performance effectively.

Management by Objectives

Management by Objectives (MBO) is an approach in which managers and employees agree defined objectives and then assess performance against those objectives.

The basic principle is:

Agree objectives → Perform work → Measure results → Review performance

MBO emphasises clarity of objectives and accountability for results.

Its effectiveness depends heavily on the quality of the objectives.

EFQM

EFQM refers to the European Foundation for Quality Management and its organisational excellence framework.

The EFQM approach provides a structured way of examining organisational direction, execution and results.

It can help organisations assess areas such as:

Strategy
Leadership
People
Processes
Stakeholders
Organisational capability
Results
Improvement

EFQM is particularly useful where an organisation wants to examine performance as a broader organisational system rather than simply through individual KPIs.

Performance Prism

The Performance Prism is a performance framework that considers organisational performance through multiple perspectives associated with stakeholders and organisational capability.

It asks questions such as:

What do stakeholders want from the organisation?
What does the organisation want from its stakeholders?
What strategies are required?
What processes are required?
What capabilities are required?

This creates a broader perspective than simply asking what KPIs should be reported.

Logic Models

A logic model describes the relationship between resources, activities, outputs and outcomes.

A typical logic model may show:

Inputs → Activities → Outputs → Outcomes → Impact

Logic models are particularly useful for understanding how activities are expected to produce results.

They can therefore support objective design, KPI selection and evaluation.

Results Frameworks

A results framework establishes relationships between objectives, outputs, outcomes, indicators and assumptions.

It is often used where organisations need to demonstrate how activities contribute to intended results.

The emphasis is on the results chain rather than simply measuring activity.

Benchmarking Frameworks

A benchmarking framework provides a structured approach to comparing organisational performance with another reference point.

The reference point may be:

Historical performance
Another organisational unit
Another organisation
Industry performance
A recognised standard
A defined best-practice level

Benchmarking should always consider comparability.

A different organisation may operate under completely different conditions, making direct comparison misleading.

Maturity Models

A maturity model assesses the development of an organisational capability through defined levels.

For example:

Level 0 → Level 1 → Level 2 → Level 3 → Level 4 → Level 5

The levels may represent progression from non-existent or ad hoc practices through developing and defined practices to managed and optimised capability.

Maturity models become particularly useful when an organisation wants to understand not only current performance but also the development of its performance-management capability.

Selecting a Framework

An organisation should consider:

Strategic objectives
Organisational complexity
Performance maturity
Management needs
Existing governance
Data availability
Reporting requirements
Organisational culture
Required level of detail
Ability to sustain the framework

The organisation should also consider whether an existing framework can be adapted rather than introducing an entirely new model.

The central principle is:

Use a performance framework because it solves a genuine management need, not simply because the framework is recognised or widely used.

2.7 Linking Strategy to Performance

The ultimate purpose of strategy and performance frameworks is to create a clear connection between what an organisation intends to achieve and the evidence used to determine whether it is achieving it.

This connection can be represented as:

Strategy → Priorities → Objectives → Measures → KPIs → Targets → Initiatives → Activities → Outputs → Outcomes

Each stage has a distinct role.

Strategy to Priorities

Strategy establishes organisational direction.

Strategic priorities identify the areas requiring particular attention.

For example:

Strategy: Improve the quality and reliability of customer services.

Priority: Service quality.

The priority focuses management attention on a specific strategic area.

Priorities to Objectives

Objectives convert priorities into defined results.

Priority: Service quality.

Objective: Reduce recurring service failures across priority services.

The objective can now be measured.

Objectives to Measures

A measure provides a method for assessing progress towards an objective.

For the example above, possible measures could include:

Repeat failure rate
First-time-right performance
Service complaints
Rework
Resolution effectiveness

The measures should provide meaningful evidence about the objective.

Measures to KPIs

Not every measure needs to become a KPI.

The organisation should select the measures that are most important for management attention.

For example:

Measure: Repeat service failure rate.

KPI: Repeat service failure rate for critical services.

The KPI should have clear strategic relevance and ownership.

KPIs to Targets

A target defines the expected level of performance.

For example:

KPI: Repeat service failure rate.

Target: Defined acceptable level by the end of the performance period.

Targets allow actual performance to be compared with expected performance.

Targets to Initiatives

Where performance is below the desired level, the organisation may establish an initiative to improve the result.

For example:

Problem: High repeat service failures.

Initiative: Redesign the underlying service process.

The initiative should be connected explicitly to the objective it is intended to support.

Initiatives to Activities

An initiative consists of activities.

For example:

Map the existing process
Identify failure points
Analyse root causes
Redesign the process
Test the redesigned process
Implement the changes
Monitor results

Activities demonstrate execution.

They do not automatically demonstrate success.

Activities to Outputs

The activities produce outputs.

For example:

Redesigned process
Updated procedures
New controls
Updated technology configuration
Staff capability development

These outputs demonstrate what the initiative delivered.

Outputs to Outcomes

The final question is whether the outputs produced the intended outcome.

For example:

Output: Redesigned service process.

Outcome: Reduced repeat service failures.

This distinction is critical.

A project can deliver its outputs successfully without producing the expected organisational improvement.

Testing KPI Relevance

A useful KPI should pass several tests.

Strategic relevance: Does it relate to an important objective?

Meaningfulness: Does it tell management something important?

Reliability: Is the underlying data sufficiently trustworthy?

Actionability: Can management respond meaningfully to changes?

Ownership: Is someone responsible for monitoring and responding?

Clarity: Is the definition understood consistently?

Balance: Could improving this KPI create problems elsewhere?

If a KPI fails several of these tests, it should be reconsidered.

The Complete Strategy-to-Performance Chain

The complete architecture can therefore be expressed as:

Strategy

↓

Strategic Priorities

↓

Objectives

↓

Measures

↓

KPIs

↓

Targets

↓

Data

↓

Analysis

↓

Initiatives

↓

Activities

↓

Outputs

↓

Outcomes

↓

Organisational Improvement

This is one of the most important structures in corporate performance management.

It establishes a line of sight from organisational intent through to measurable results.

The "So What?" Test

Every important measure should ultimately answer the question:

So what?

If a KPI changes, what does that mean?

If performance deteriorates, who needs to know?

What could be causing the change?

What decision might be required?

What action could be taken?

What outcome should the action produce?

If there is no meaningful answer, the measure may not be sufficiently important.

Bringing the Framework Together

Strategy, objectives and performance frameworks should operate as an integrated system.

The organisation should be able to move from:

Where are we going?

to:

What are we trying to achieve?

to:

How will we know whether we are succeeding?

to:

What does the evidence tell us?

to:

What should we do next?

This creates the foundation for the chapters that follow, where performance measures, KPIs, targets, analysis, dashboards, data, governance, maturity and technology will be examined in greater detail.

The central principle of this chapter is:

Corporate performance measurement should create a clear line of sight from strategy to objectives, from objectives to measures and from measures to management action and organisational outcomes.

3. KPIs, Metrics, Measures and Targets

Performance measurement becomes meaningful when an organisation knows exactly what it is measuring, why it is measuring it and what the results are supposed to tell decision-makers.

This is where metrics, measures, indicators, Key Performance Indicators, targets, thresholds and benchmarks become important.

A well-designed performance measurement system does not simply produce numbers. It produces reliable information that helps people understand what is happening, whether performance is acceptable and where action may be required.

The quality of the measurement system therefore depends on much more than selecting a list of KPIs. Each measure needs a clear purpose, a precise definition, a reliable source, an appropriate owner and a sensible method of interpretation.

3.1 Metrics, Measures, Indicators and KPIs

The words metric, measure, indicator and KPI are often used interchangeably. They are related but they do not mean exactly the same thing.

A measure is a quantified representation of something that can be observed.

For example, the number of customer complaints received during a reporting period is a measure. The average time taken to resolve a service request is also a measure.

A metric is a quantified measurement used to understand or assess a particular aspect of performance.

In many organisations, the words metric and measure are effectively interchangeable. However, it is useful to think of a metric as a measure that has been selected because it provides meaningful information for analysis or management.

An indicator provides evidence about a condition, trend or situation.

An indicator does not necessarily tell the whole story. It provides a signal that helps an organisation understand what may be happening.

For example, an increase in unresolved service requests may indicate increasing operational pressure. A rise in employee absence may indicate a workforce issue that requires further investigation.

A Key Performance Indicator, usually abbreviated to KPI, is a particularly important measure selected to monitor performance against an important organisational objective or outcome.

The word "key" matters.

Not every measure should become a KPI.

An organisation may collect hundreds or thousands of measures through its operational systems. Only a smaller number should normally receive formal KPI status.

A KPI should therefore answer an important performance question.

For example:

Are customers receiving the required level of service?
Are critical processes operating within acceptable timescales?
Are important projects progressing according to agreed milestones?
Are quality standards being achieved?
Are significant risks remaining within agreed tolerances?
Is technology providing the required availability and reliability?
Is the workforce developing the capabilities required by the organisation?

A KPI should have a clear connection to something the organisation considers important.

KPI versus metric

A metric can be useful without being a KPI.

For example, an IT service team may record the number of incidents created each day. This may be useful operational information.

However, the organisation may designate the percentage of critical incidents resolved within the agreed service level as a KPI because that measure directly relates to an important service objective.

The distinction is therefore about importance, purpose and management attention.

KPI versus objective

An objective describes what the organisation wants to achieve.

A KPI helps measure whether it is achieving it.

For example:

Objective: Improve customer service responsiveness

KPI: Percentage of customer enquiries answered within the required response time

The objective describes the desired result. The KPI provides evidence of progress towards that result.

KPI versus target

A target is the desired level of performance for a measure.

For example:

KPI: Percentage of service requests resolved within the agreed timeframe

Target: 95%

The KPI identifies what is being measured. The target identifies the expected level.

Confusing KPIs with targets creates poorly structured performance systems.

The purpose of a KPI

A good KPI should help management answer a meaningful question.

It should make performance more visible.

It should support comparison.

It should help identify exceptions.

It should support discussion.

Most importantly, it should help people decide whether action is required.

A KPI that produces a number but does not influence understanding or action may not deserve KPI status.

The KPI hierarchy

A useful hierarchy is:

Objective → Measure → KPI → Target → Actual Result → Analysis → Action

This creates a logical connection between what the organisation wants to achieve and what it actually observes.

When this connection is missing, organisations often end up measuring what is easy rather than what is important.

3.2 Types and Categories of KPIs

KPIs can be classified in many different ways.

There is no single universal classification system. Different organisations use different categories depending on their operating model, strategy and measurement requirements.

The important principle is to understand what each KPI is intended to tell the organisation.

Strategic KPIs

Strategic KPIs measure progress towards important strategic objectives.

They normally operate at organisational level and provide senior leaders with a view of whether strategic priorities are progressing.

Strategic KPIs should not simply be a collection of operational statistics.

They should provide evidence about significant organisational outcomes and strategic performance.

Operational KPIs

Operational KPIs measure the performance of day-to-day activities, processes and services.

Examples include:

Average service response time
Percentage of requests completed within the required timeframe
Process cycle time
Service availability
Backlog volume
First-time-right percentage
Process error rate

Operational KPIs are often more frequent than strategic KPIs because operational performance can change rapidly.

Customer KPIs

Customer KPIs measure aspects of the customer or service user experience.

Examples include:

Customer satisfaction
Customer effort
Complaint volumes
Complaint resolution time
Customer experience scores
Service responsiveness
Percentage of interactions resolved at first contact

Customer measures should be interpreted carefully.

A high satisfaction score does not necessarily mean every aspect of service is performing well. Different measures may reveal different aspects of the customer experience.

Employee and workforce KPIs

Workforce KPIs provide information about people and organisational capability.

Examples include:

Employee engagement
Employee retention
Employee turnover
Absence levels
Time to hire
Training completion
Capability attainment
Internal mobility
Workforce utilisation

These measures should be interpreted in context rather than treated as isolated numbers.

Process KPIs

Process KPIs measure how effectively and efficiently processes operate.

Examples include:

Process cycle time
Process completion rate
Process backlog
Rework percentage
Process error rate
Throughput
First-time-right performance

Process measures are particularly useful when an organisation is trying to improve operational performance.

Technology KPIs

Technology KPIs measure the performance of applications, infrastructure, digital services and IT operations.

Examples include:

System availability
Application response time
Incident resolution time
Service request completion
Change success rate
Major incident frequency
Infrastructure reliability

Technology measures should ultimately connect to the services and organisational outcomes that technology supports.

Quality KPIs

Quality KPIs measure whether outputs and services meet defined standards.

Examples include:

Defect rate
Error rate
First-time-right percentage
Rework percentage
Non-conformities
Quality inspection results
Corrective action completion

Quality measurement is particularly important because high activity does not necessarily mean high quality.

Risk KPIs

Risk-related performance measures help organisations monitor significant risks.

A Key Risk Indicator, or KRI, is a measure that provides information about changes in risk exposure or risk conditions.

Examples include:

Number of unresolved high-risk issues
Percentage of critical controls tested
Number of overdue risk treatments
Number of significant control failures
Percentage of critical processes without adequate contingency arrangements

KPIs and KRIs can work together.

A KPI may show that a process is performing well today while a KRI may indicate that underlying risk is increasing.

Compliance KPIs

Compliance measures monitor whether required rules, policies, standards or obligations are being followed.

Examples include:

Compliance completion rate
Number of overdue mandatory actions
Number of audit findings
Corrective action closure rate
Percentage of required controls operating effectively

Project and programme KPIs

Project KPIs measure delivery performance.

Examples include:

Milestone achievement
Schedule adherence
Requirements completion
Defect resolution
Issue resolution
Risk treatment
Dependency completion
Benefits achievement

Project KPIs should provide a balanced view rather than focusing exclusively on one dimension.

Supplier and vendor KPIs

Supplier KPIs measure the performance of external providers.

Examples include:

Service level achievement
Delivery reliability
Response time
Defect levels
Issue resolution
Contractual service compliance
Corrective action completion

Supplier measures are particularly important where an organisation depends on external providers for critical services.

The danger of categorisation

Categories help organise KPIs but they should not become an excuse to create excessive measures.

An organisation does not need ten KPIs simply because ten KPI categories exist.

The objective is to create a coherent measurement system that provides sufficient information without overwhelming the people who must use it.

3.3 Leading, Lagging, Input, Process, Output and Outcome Measures

One of the most important concepts in performance measurement is understanding what type of measure is being used.

Different measures provide different types of information.

Leading measures

A leading measure provides an early indication of future performance.

It measures a factor that may influence a later result.

For example, the percentage of employees completing required training may provide an indication of future capability.

The percentage of preventative maintenance activities completed may provide an indication of future equipment reliability.

Leading measures are valuable because they can provide time to intervene before an undesirable result occurs.

However, leading does not automatically mean useful.

A leading measure must have a meaningful relationship with the result it is intended to influence.

Lagging measures

A lagging measure records an outcome that has already occurred.

Examples include:

Customer complaints received
Service failures
Defects identified
Project milestones missed
Employee turnover
Incidents recorded

Lagging measures are important because they tell the organisation what actually happened.

Their limitation is timing.

By the time a lagging indicator deteriorates, the underlying problem may already have existed for some time.

Input measures

Input measures describe resources or conditions required to perform an activity.

Examples include:

Number of available employees
Available system capacity
Number of trained personnel
Availability of required equipment

Input measures can provide useful context but they do not automatically demonstrate good performance.

Having sufficient resources does not guarantee that the resources are being used effectively.

Process measures

Process measures describe what happens during a process.

Examples include:

Processing time
Number of transactions processed
Queue time
Number of items waiting
Percentage of cases passing a particular process stage

Process measures are useful for identifying bottlenecks and operational constraints.

Output measures

Output measures describe what a process produces.

Examples include:

Number of completed cases
Number of completed service requests
Number of reports produced
Number of applications processed
Number of project deliverables completed

Output measures are useful but output volume alone does not demonstrate effectiveness.

Producing more outputs does not necessarily mean producing better outcomes.

Outcome measures

Outcome measures describe the result or effect produced by an activity, service or intervention.

Examples include:

Improvement in customer satisfaction
Reduction in recurring service failures
Improvement in process quality
Improvement in service reliability
Increased capability
Reduction in avoidable complaints

Outcome measures are often more closely connected to organisational purpose than activity measures.

A simple performance chain

A useful model is:

Inputs → Activities → Processes → Outputs → Outcomes

For example:

Input: Trained service staff

Activity: Customer enquiries are handled

Process: Enquiries are assessed and resolved

Output: Customer cases are completed

Outcome: Customers receive an effective and timely service

Each stage tells a different part of the story.

The importance of balance

A mature measurement system normally contains a mixture of leading and lagging measures.

It may also contain input, process, output and outcome measures.

The correct balance depends on the performance question.

If an organisation measures only outcomes, it may discover problems too late.

If it measures only activities, it may become obsessed with work volume without knowing whether the work produced meaningful results.

The strongest systems connect drivers to results.

3.4 KPI Design and Definition

Selecting a KPI is only the beginning.

A KPI must be defined precisely enough that different people can understand and calculate it consistently.

Poor KPI definitions create disagreement, unreliable reporting and misleading comparisons.

A well-defined KPI should normally contain several components.

KPI name

The KPI should have a clear and concise name.

For example:

Percentage of Critical Incidents Resolved Within SLA

The name should communicate what the measure represents.

Avoid vague names such as:

Service performance
Customer quality
Operational effectiveness

These labels may sound meaningful but do not define what is actually being measured.

KPI definition

The definition explains exactly what the KPI measures.

For example:

"The percentage of critical incidents resolved within the agreed service level during the reporting period."

The definition should remove ambiguity.

Formula

The formula explains how the KPI is calculated.

For example:

Percentage resolved within SLA = Number resolved within SLA ÷ Total number of applicable incidents × 100

The formula should be documented.

Two teams should not produce different results because they silently use different calculation methods.

Unit of measurement

The unit should be specified.

Examples include:

Percentage
Number
Hours
Days
Minutes
Rating
Score
Ratio

Data source

The organisation should identify where the data comes from.

Examples include:

Service management system
Customer relationship system
Human resources system
Project management system
Quality management system
Audit system
Operational database
Survey platform

The source should be sufficiently reliable for the intended purpose.

Reporting frequency

The KPI definition should specify how often it is measured or reported.

Possible frequencies include:

Real time
Daily
Weekly
Monthly
Quarterly
Annually

The correct frequency depends on how quickly the underlying performance changes and how quickly management needs to respond.

Reporting period

The organisation should define the period represented by the result.

For example:

Current day
Previous seven days
Calendar month
Reporting quarter
Financial year

Again, financial terminology is not necessary here. The important principle is that the period must be unambiguous.

Baseline

A baseline is the starting point against which future performance can be compared.

For example, an organisation may establish that average service resolution time was 42 hours before an improvement initiative.

Future performance can then be compared with that baseline.

A baseline is particularly useful when a target has not yet been established or when the organisation wants to understand the scale of improvement.

Target

The target identifies the desired level of performance.

Targets should be realistic, meaningful and connected to organisational objectives.

Owner

Every important KPI should have an accountable owner.

The owner is responsible for understanding the KPI, reviewing its performance and ensuring that appropriate action is taken when necessary.

Ownership does not necessarily mean that the person personally produces the data.

Data owner

A data owner is responsible for the quality, definition and appropriate management of the underlying data.

The KPI owner and data owner may be different people.

Reporting owner

The reporting owner may be responsible for producing, validating and distributing the KPI information.

Separating these roles can be useful in larger organisations.

KPI dictionary

A KPI dictionary is a controlled catalogue containing the definitions and supporting information for the organisation's KPIs.

A KPI dictionary can include:

KPI name
KPI definition
Purpose
Objective supported
Formula
Unit
Data source
Data owner
KPI owner
Reporting frequency
Reporting period
Baseline
Target
Threshold
Tolerance
Calculation rules
Inclusion rules
Exclusion rules
Data quality requirements
Reporting status

The KPI dictionary becomes a critical reference point.

It reduces ambiguity and helps maintain consistency across dashboards, reports and management reviews.

3.5 Targets, Thresholds, Tolerances and Benchmarks

A measurement system becomes more useful when actual performance can be interpreted against an expected or acceptable level.

This is where targets, thresholds, tolerances and benchmarks become important.

Targets

A target is the desired level of performance.

For example:

KPI: Customer enquiries answered within the required response time

Target: 95%

The target provides a reference point.

Without a target, a result of 90% may be difficult to interpret.

Is 90% good?

Is it poor?

Is it acceptable?

The target provides context.

Baselines

A baseline describes the starting or reference position.

Suppose the current performance level is 82%.

The organisation may then establish a target of 92%.

The baseline shows where the organisation started.

The target shows where it intends to go.

Thresholds

A threshold identifies a level at which attention may be required.

For example:

Above 95%: expected performance
90% to 94.9%: management attention
Below 90%: intervention required

The exact values depend on the organisation and the KPI.

Thresholds should not be selected simply because a traffic-light dashboard needs three colours.

They should represent meaningful performance conditions.

Tolerances

A tolerance defines the acceptable range around a target or expected level.

For example, an organisation may establish a target of 95% with an acceptable tolerance of two percentage points.

This helps distinguish normal variation from meaningful deterioration.

Minimum targets

A minimum target defines the lowest acceptable performance level.

It is particularly useful for service, quality, compliance and operational measures where falling below a particular level creates unacceptable consequences.

Stretch targets

A stretch target represents a more ambitious level of performance.

Stretch targets can encourage improvement but they should remain credible.

If targets are consistently impossible to achieve, people may eventually stop treating them as meaningful.

Benchmarks

A benchmark is a reference point used to compare performance.

Benchmarks can come from different sources.

Historical benchmark

Performance is compared with the organisation's previous performance.

Internal benchmark

One team, department or business unit is compared with another within the same organisation.

External benchmark

Performance is compared with another organisation or recognised external reference.

Industry benchmark

Performance is compared with a relevant industry reference.

Best-practice benchmark

Performance is compared with a recognised example of strong performance.

Benchmarks can provide useful context but they must be interpreted carefully.

Different organisations may operate under different conditions.

A process serving a small specialist population may not be directly comparable with a process serving a very large and diverse population.

Benchmarking is not copying

A benchmark should stimulate questions rather than automatic imitation.

If another organisation achieves a particular result, the correct question is not simply:

"How do we copy that number?"

A better question is:

"What conditions, processes, capabilities and practices contribute to that result?"

This encourages learning rather than superficial comparison.

Targets should support behaviour

Targets influence behaviour.

People naturally pay attention to the measures against which their performance is assessed.

Poorly designed targets can therefore produce unintended consequences.

For example, if a service team is measured only on speed, employees may prioritise closing cases quickly even when quality requires more time.

A better measurement system may combine speed, quality, customer experience and resolution effectiveness.

Targets should therefore be designed as part of a measurement system rather than as isolated numbers.

3.6 KPI Ownership, Governance and Lifecycle

KPIs need governance.

Without governance, organisations gradually accumulate obsolete measures, duplicate KPIs, inconsistent definitions and unreliable reporting.

KPI governance establishes who has authority over the measurement system and how changes are controlled.

KPI ownership

The KPI owner should understand why the KPI exists and what action may be required when performance changes.

The owner should be able to answer:

What does this KPI tell us?
Why does it matter?
What objective does it support?
What should happen when performance deteriorates?
What factors influence the result?
Who needs to be involved?
When should the KPI be reviewed?

Ownership should therefore be active rather than nominal.

Putting someone's name beside a KPI is not enough.

Data ownership

Data ownership concerns the quality and management of the underlying information.

The data owner should understand:

Where the data originates
How it is captured
How it is transformed
Who can change it
What quality controls exist
How long it is retained
What definitions apply

Reporting ownership

Reporting ownership ensures that performance information is produced consistently and reaches the appropriate audience.

Reporting should include appropriate validation before information is presented to decision-makers.

KPI governance forums

Larger organisations may establish a KPI governance forum or performance governance group.

Its responsibilities may include:

Approving new KPIs
Reviewing existing KPIs
Resolving definition disputes
Reviewing data quality
Removing duplicate measures
Retiring obsolete KPIs
Approving changes to calculation methods
Ensuring alignment with organisational objectives

KPI lifecycle

A KPI should have a lifecycle.

A useful model is:

Identify → Define → Approve → Implement → Monitor → Review → Refine → Retire

Identify

Determine whether a measure is required to answer an important performance question.

Define

Document the KPI precisely.

Approve

Confirm that the KPI is appropriate and aligned with organisational requirements.

Implement

Establish data collection, calculation and reporting.

Monitor

Track performance and data quality.

Review

Assess whether the KPI continues to provide useful information.

Refine

Modify the KPI where definitions, objectives or operational conditions have changed.

Retire

Remove the KPI when it no longer provides meaningful information.

KPI review

KPIs should not remain unchanged forever.

An organisation may change its strategy.

Processes may change.

Technology may change.

Customer expectations may change.

Regulatory requirements may change.

A KPI that was useful several years ago may no longer provide meaningful information.

Regular KPI reviews prevent the measurement system from becoming a historical record of priorities that no longer exist.

KPI governance principle

A useful rule is:

Every important KPI should have a purpose, owner, definition, data source, target and review mechanism.

If several of these are missing, the KPI may not be ready for formal management use.

3.7 Designing Effective KPIs and Avoiding KPI Problems

Good KPI design requires discipline.

Many organisations have large numbers of measures but still struggle to understand performance.

The problem is often not a lack of data.

It is a lack of meaningful measurement.

Relevant KPIs

A KPI should relate directly to an important organisational objective or performance question.

If a KPI cannot be connected to something that matters, its value should be questioned.

Measurable KPIs

A KPI should be capable of being measured consistently.

If the data cannot be collected reliably, the KPI may create more confusion than insight.

Controllable or influenceable KPIs

People should ideally be able to influence the performance being measured.

This does not mean that they must have complete control.

Many outcomes depend on multiple factors.

However, assigning accountability for a measure that an individual or team cannot meaningfully influence can create frustration and inappropriate behaviour.

Meaningful KPIs

A KPI should tell decision-makers something useful.

A technically precise measurement can still be strategically irrelevant.

The key question is:

What decision could this KPI help us make?

If there is no credible answer, the measure deserves further examination.

Avoid vanity metrics

A vanity metric is a measure that looks impressive but provides limited insight into actual performance.

For example, a website may report the total number of visits.

That number may be interesting.

However, if the organisation's real question concerns whether users successfully completed an important service, total visits may not provide enough information.

Vanity metrics are not necessarily useless.

The problem occurs when they receive disproportionate attention.

Avoid excessive KPIs

More KPIs do not automatically create better performance management.

An excessive number of KPIs creates:

Information overload
Increased reporting effort
Reduced management attention
Conflicting priorities
Greater data quality problems
Slower decision-making

A smaller set of carefully selected KPIs is often more useful than a large catalogue of loosely connected measures.

Avoid conflicting KPIs

KPIs can unintentionally encourage competing behaviours.

For example:

KPI A: Reduce average service handling time

KPI B: Improve first-time resolution

If staff are pressured to reduce handling time without considering resolution quality, the two measures may create tension.

The solution is not necessarily to remove one KPI.

The solution is to understand the relationship and design the measurement system accordingly.

Avoid poor definitions

A KPI can become unreliable when different teams interpret it differently.

For example, "resolution time" could mean:

Time from request creation to closure
Time from request assignment to closure
Time excluding periods waiting for the customer
Time excluding weekends
Total elapsed time

All five definitions could produce different results.

The definition must therefore be explicit.

Avoid unreliable data

A sophisticated KPI calculated from poor data remains a poor KPI.

Data quality should be assessed across dimensions such as:

Accuracy
Completeness
Consistency
Timeliness
Validity
Uniqueness

The organisation should understand the limitations of the data before making significant decisions based on it.

Avoid inappropriate targets

Targets should reflect context.

A target that is too low may allow poor performance to appear acceptable.

A target that is impossibly high may destroy credibility.

Targets should therefore be informed by:

Organisational objectives
Historical performance
Capability
Customer requirements
Service requirements
Risk considerations
Relevant benchmarks
Improvement expectations

Avoid KPI gaming

KPI gaming occurs when people alter behaviour primarily to improve the reported measure rather than improve the underlying performance.

For example, if a team is measured only on the number of cases closed, cases may be closed prematurely and reopened later.

The KPI may appear to improve while the actual service experience does not.

This is one reason why balanced measurement matters.

Avoid measuring activity instead of performance

Activity is not automatically achievement.

A team may conduct hundreds of meetings.

That does not prove that performance improved.

A project team may complete many tasks.

That does not automatically prove that the project delivered the intended outcome.

A service team may process a large number of requests.

That does not necessarily mean customers received an effective service.

The measurement system should therefore distinguish between:

What we did

and

What changed because we did it

Avoid measuring everything

Not everything needs to become a KPI.

Some information is useful as supporting analysis.

Some information is useful for operational monitoring.

Some information is useful only during particular investigations.

The objective is not to measure everything.

The objective is to measure what matters and provide sufficient supporting information to understand it.

Use the "So What?" test

One of the simplest tests for KPI quality is:

So what?

Ask:

"What does this number tell us?"

Then ask:

"Why does that matter?"

Then ask:

"What would we do differently if the number changed?"

If there is no meaningful answer, the KPI may not deserve prominence.

Use the "What action?" test

A strong KPI should connect naturally to management action.

For example:

KPI: Critical incidents resolved within required timeframe

Result: Performance falls significantly below target

Analysis: A particular technical dependency is creating repeated delays

Action: Address the dependency and strengthen the relevant support process

This is the purpose of performance measurement.

The number is not the final product.

The insight and resulting action are what create value.

The complete KPI design model

A practical KPI design model is:

Business Purpose → Objective → Performance Question → Measure → KPI → Definition → Formula → Data Source → Owner → Baseline → Target → Threshold → Reporting → Analysis → Action → Review

This model brings together the principles covered throughout this chapter.

It starts with purpose rather than data.

It connects measurement to objectives.

It defines the KPI precisely.

It establishes ownership.

It provides context through baselines and targets.

It creates a mechanism for analysis and action.

It also recognises that KPIs require continuous review.

The ultimate principle

A KPI should never exist simply because an organisation has the ability to collect the data.

It should exist because the information helps the organisation understand an important aspect of performance.

The strongest measurement systems therefore contain a relatively small number of meaningful KPIs supported by additional measures and detailed analysis where required.

The objective is clarity.

The objective is understanding.

The objective is better decisions.

And ultimately, the objective is improved organisational performance.

4. Performance Analysis, Benchmarking and Forecasting

Measurement produces information.

Analysis turns that information into understanding.

An organisation may have hundreds of KPIs and thousands of individual data points. Yet measurement alone does not explain what happened, why it happened, whether it matters or what should happen next.

Performance analysis provides the bridge between measurement and management action.

It examines actual performance, compares results with expectations, identifies patterns, investigates causes, assesses gaps and supports informed decisions.

This chapter explains the major techniques used to analyse organisational performance, including variance analysis, trend analysis, root-cause analysis, benchmarking, forecasting and scenario analysis.

The central principle is simple:

Do not stop at the number. Understand the performance behind the number.

4.1 Measuring Actual Performance

Actual performance is the result that has actually occurred during a defined period.

For example, an organisation may have a KPI requiring 95% of service requests to be resolved within the agreed timeframe.

If the actual result is 91%, the measurement tells us where performance currently stands.

The next question is whether 91% represents acceptable performance.

That requires comparison.

Actual versus target

The most basic performance comparison is:

Actual Performance versus Target Performance

For example:

Target: 95%

Actual: 91%

Gap: -4 percentage points

The gap shows that actual performance is below the target.

However, a gap alone does not explain why the gap exists.

This distinction is important.

Measurement identifies the position.

Analysis investigates the reason.

Actual versus baseline

Actual performance can also be compared with a baseline.

Suppose an organisation previously recorded 84% service performance and the current result is 91%.

The organisation has improved by seven percentage points compared with the baseline.

This may represent meaningful progress even though the current result remains below the target.

A performance system should therefore consider both:

Where are we now?
Where did we start?
Where do we want to be?

Status

Performance dashboards often classify results using status categories.

A common approach is:

Green: performance is within the expected range
Amber: performance requires attention
Red: performance requires intervention

The exact rules should be defined for each KPI.

Status should never be based purely on visual preference.

The thresholds should represent meaningful performance conditions.

Thresholds

A threshold identifies a point at which management attention becomes appropriate.

For example:

95% or above: expected
90% to 94.9%: attention required
Below 90%: intervention required

These ranges are illustrative.

The appropriate values depend on the KPI, operating environment and organisational requirements.

Tolerances

Performance naturally varies.

Not every movement represents a significant problem.

A tolerance helps distinguish normal variation from meaningful deterioration.

For example, if a process normally operates between 94% and 96%, a temporary movement to 93.8% may not require the same response as a sustained decline to 87%.

The organisation therefore needs to understand normal performance variation.

Exceptions

An exception is a performance condition that requires particular attention.

Exceptions may include:

Significant deviation from target
Rapid deterioration
Repeated failure
Critical threshold breach
Unexpected improvement
Significant change in underlying conditions

Exception-based management prevents managers from spending equal time on every KPI.

Attention can instead be concentrated where the evidence indicates that something important is happening.

Performance status should lead to questions

A red KPI does not automatically explain the problem.

The correct response is investigation.

Useful questions include:

What changed?
When did it change?
How large is the change?
Is the change isolated or widespread?
Is it temporary or persistent?
What factors may have contributed?
Does the same pattern appear elsewhere?
What action is required?

This moves performance management from reporting towards analysis.

4.2 Variance Analysis

Variance is the difference between two performance values.

The comparison may be between:

Actual and target
Actual and baseline
Actual and previous period
Actual and forecast
One team and another
One process and another

Variance analysis helps explain where performance has changed.

Basic variance

A simple calculation is:

Variance = Actual − Target

For a KPI measured as a percentage:

Target: 95%

Actual: 91%

Variance: -4 percentage points

The organisation now knows that performance is four percentage points below target.

Positive and negative variance

The meaning of a positive or negative variance depends on the KPI.

For some measures, a higher value represents better performance.

For example:

Percentage of requests resolved within the required timeframe

Higher may be better.

For other measures, a lower value may represent better performance.

For example:

Average resolution time

Lower may be better.

Therefore, the interpretation of variance must always consider the direction of desired performance.

Favourable and unfavourable variance

A favourable variance means performance has moved in a desirable direction.

An unfavourable variance means performance has moved in an undesirable direction.

The classification should be based on the objective rather than simply whether the number increased or decreased.

For example, reducing average incident resolution time may be favourable.

Increasing customer satisfaction may be favourable.

Reducing the number of defects may be favourable.

Increasing the number of unresolved critical issues would normally be unfavourable.

Magnitude matters

Not every variance deserves investigation.

A two-minute movement in an average response time may be insignificant.

A two-hour movement may be significant.

The significance of a variance depends on:

The size of the movement
The importance of the KPI
The normal range of variation
The impact of the change
The duration of the change
The risk associated with the result

Frequency matters

A single variance may be an isolated event.

Repeated variance may indicate a structural problem.

For example:

Period 1: 94%

Period 2: 93%

Period 3: 91%

Period 4: 89%

The individual movements may appear modest.

Together, however, they reveal a sustained deterioration.

Trend analysis should therefore complement variance analysis.

Forecast versus actual

Variance analysis can also compare actual performance with a forecast.

For example:

Forecast service availability: 99.5%

Actual service availability: 98.9%

This indicates that performance was below the expected forecast.

The next question is why.

Perhaps a major incident occurred.

Perhaps a system migration introduced unexpected disruption.

Perhaps the original forecast assumptions were incorrect.

Variance analysis identifies the difference.

Diagnostic analysis investigates the explanation.

Volume, process and performance factors

Performance variance may arise from different factors.

A change in workload volume may affect performance.

A process change may affect performance.

A capability issue may affect performance.

A technology problem may affect performance.

A supplier issue may affect performance.

An unexpected event may affect performance.

It is therefore important not to assume that a variance has a single cause.

Avoid simplistic variance explanations

A common analytical mistake is:

Performance decreased → one obvious cause must exist

Real organisational systems are usually more complicated.

Several factors may interact.

For example, an increase in service resolution time could be associated with:

Higher request complexity
Increased workload
Reduced availability of experienced staff
A technology issue
A process change
Additional approval requirements
External dependencies

The analysis should investigate the evidence before assigning a cause.

Variance analysis questions

A useful variance review asks:

What is the variance?
Is it significant?
Is it persistent?
Is it isolated?
What changed?
What factors may explain the change?
What evidence supports the explanation?
What action is required?

This creates a disciplined approach to performance analysis.

4.3 Trend and Comparative Analysis

A single performance result provides a snapshot.

A trend provides a story.

Trend analysis examines how performance changes over time.

Time series

A time series is a sequence of observations recorded over time.

For example:

Period	Service Performance
Period 1	96%
Period 2	95%
Period 3	94%
Period 4	92%
Period 5	91%

The individual numbers are useful.

The pattern is even more useful.

The organisation can see that performance has gradually declined.

Trend direction

Common trend patterns include:

Increasing
Decreasing
Stable
Volatile
Seasonal
Cyclical
Step change
Recovery

Understanding the pattern helps determine the appropriate response.

Increasing performance

An increasing trend may indicate improvement.

However, an increase is not automatically positive.

If the KPI represents complaints, defects or unresolved issues, an increase may indicate deterioration.

The meaning of a trend always depends on the KPI.

Decreasing performance

A declining trend may indicate deterioration.

However, it may also represent improvement where lower values are desirable.

For example, a declining incident resolution time may be positive.

Stable performance

A stable trend may indicate consistent performance.

It may also indicate stagnation.

If the organisation has an improvement objective, stable performance may still represent a problem.

Volatile performance

A volatile KPI moves significantly up and down.

Volatility can indicate:

Unstable processes
Variable demand
Inconsistent capacity
External dependencies
Poor data quality
Irregular operational events

A volatile result should not automatically be interpreted as deterioration.

The underlying pattern needs to be investigated.

Comparative analysis

Comparative analysis examines differences between groups, locations, services, processes or time periods.

Examples include:

Current period versus previous period
One service versus another
One team versus another
One region versus another
One process stage versus another
One customer group versus another

Comparisons can reveal differences that are hidden in overall organisational averages.

Averages can hide important information

Suppose an organisation reports an overall service response time of 30 minutes.

That number may appear acceptable.

However, the result may consist of:

Team A: 10 minutes
Team B: 15 minutes
Team C: 20 minutes
Team D: 75 minutes

The overall average hides the variation.

Segmentation can reveal where the problem actually exists.

Segmentation

Segmentation means dividing performance data into meaningful groups.

Possible segments include:

Customer type
Service type
Geography
Department
Process
Product or service
Priority
Severity
Employee group
Technology platform

Segmentation can reveal patterns that disappear when everything is combined.

Trend analysis should consider context

A trend should not be interpreted without understanding relevant events.

For example, a sudden increase in service requests may be explained by:

A new service launch
A major organisational change
A technology migration
A change in customer behaviour
A regulatory requirement
A temporary operational event

The trend is real.

The explanation requires context.

Correlation does not prove causation

Two measures may move together without one causing the other.

For example, customer complaints and service workload may both increase during a period.

This does not automatically prove that workload caused the complaints.

Other factors may be involved.

Correlation describes an association between variables.

Causation means that one factor contributes to producing a change in another.

Analysts should distinguish between the two.

Performance trajectory

A performance trajectory describes the direction in which performance is moving.

It is often more useful to ask:

"Where is performance heading?"

rather than simply:

"Where is performance now?"

This is particularly important for early intervention.

A KPI that is currently within target but deteriorating rapidly may require more attention than a KPI that is slightly below target but steadily improving.

4.4 Root-Cause and Diagnostic Analysis

Performance analysis should eventually move from identifying what happened to understanding why it happened.

This is the purpose of diagnostic analysis.

Symptoms versus causes

A symptom is an observable indication of a problem.

A cause is a factor that contributes to producing the problem.

For example:

Symptom: Service requests are taking longer to resolve

Possible causes may include:

Increased complexity
Insufficient capability
Poor process design
Technology problems
Incomplete information
Approval delays
External dependencies

Correcting the symptom without addressing the cause may produce only temporary improvement.

Root cause

A root cause is an underlying factor whose removal or treatment can prevent a problem from recurring.

There may be more than one root cause.

Some problems are caused by several interacting conditions.

Five Whys

The Five Whys technique involves repeatedly asking why a problem occurred.

For example:

Problem: A critical service request was resolved late

Why?

Because the request waited for specialist approval

Why?

Because the approval required manual intervention

Why?

Because the workflow did not automatically route the request

Why?

Because the process design had not been updated after an organisational change

Why?

Because process ownership had not been established for the new operating arrangement

The exact number of questions does not have to be five.

The purpose is to move beyond the immediate symptom.

Fishbone or Ishikawa analysis

A Fishbone Diagram, also known as an Ishikawa Diagram, is a structured technique for exploring potential causes.

Categories may include:

People
Process
Technology
Data
Environment
Suppliers
Management
Methods

The categories should be adapted to the problem.

The technique helps teams avoid jumping immediately to one explanation.

Pareto analysis

Pareto analysis helps identify the causes contributing most significantly to a problem.

The basic principle is to identify the relatively small number of causes responsible for a large proportion of the observed effect.

For example, an organisation may discover that a small number of recurring incident types account for most service disruption.

Addressing those areas may produce greater improvement than treating every issue equally.

Evidence before conclusions

Root-cause analysis should be evidence-based.

A plausible explanation is not necessarily a proven explanation.

The team should ask:

What evidence supports this cause?
Is the pattern repeatable?
Can the cause be observed?
Does removing the cause change the result?
Are there alternative explanations?

This reduces the risk of implementing solutions against incorrectly diagnosed problems.

Avoid blaming individuals too early

Many performance problems are influenced by systems and processes.

An individual error may be visible.

The underlying cause may involve:

Poor instructions
Inadequate training
Confusing process design
Weak controls
Poor system usability
Excessive workload
Unclear accountability

Root-cause analysis should therefore examine the system around the event.

This does not remove personal accountability where appropriate.

It simply prevents premature conclusions.

Root-cause analysis and improvement

A good diagnostic process should lead to action.

The sequence is:

Problem → Evidence → Analysis → Root Causes → Corrective Action → Monitoring → Verification

The final step is important.

An action is not successful simply because it was completed.

The organisation should verify whether the underlying performance improved.

4.5 Benchmarking and Performance Gaps

Benchmarking provides a structured way to compare performance against a reference point.

It can help organisations understand where they stand and identify opportunities for improvement.

Internal benchmarking

Internal benchmarking compares performance within the same organisation.

For example, one service centre may resolve requests significantly faster than another.

This can lead to useful questions:

What does the higher-performing team do differently?
Are the processes genuinely comparable?
Are workloads similar?
Are capabilities similar?
Are the systems the same?
Can useful practices be transferred?

Internal benchmarking can be particularly valuable because the organisational context may be more comparable.

External benchmarking

External benchmarking compares performance with another organisation.

It can provide an external reference point.

However, external comparisons require careful interpretation.

Different organisations may have different:

Customers
Processes
Technology
Workforce models
Regulatory requirements
Service definitions
Operating environments

A direct numerical comparison may therefore be misleading.

Industry benchmarking

Industry benchmarks provide reference points for organisations operating in similar sectors.

They can help establish a broad view of expected performance.

However, industry averages should not automatically become organisational targets.

An average does not necessarily represent good performance.

Best-practice benchmarking

Best-practice benchmarking focuses on recognised approaches or performance levels considered strong within a relevant context.

The objective should be to understand the practices that support performance rather than simply copy the reported result.

Benchmarking questions

A useful benchmarking exercise asks:

What are we comparing?
Why are we comparing it?
Are the definitions consistent?
Are the operating conditions comparable?
What does the difference tell us?
What explains the difference?
Is the difference meaningful?
What can we learn?

Performance gaps

A performance gap is the difference between current performance and a desired or reference state.

For example:

Current: 87%

Desired: 95%

Gap: 8 percentage points

The gap identifies the distance.

It does not explain how to close it.

Capability gaps

A performance gap may be caused by a capability gap.

For example:

Insufficient skills
Weak process design
Poor technology
Inadequate data
Weak governance
Unclear ownership

The organisation should therefore distinguish between the performance result and the capability required to produce that result.

Benchmarking limitations

Benchmarking can create problems when organisations compare incompatible measures.

Common errors include:

Comparing different definitions
Comparing different populations
Comparing different service models
Ignoring workload complexity
Ignoring operating conditions
Treating averages as targets
Copying practices without understanding context

Benchmarking is most useful when it stimulates learning and investigation.

4.6 Forecasting and Scenario Analysis

Performance management should not only examine the past.

It should also help organisations understand what may happen next.

Forecasting is the process of estimating future performance using available evidence, historical patterns, current conditions and relevant assumptions.

Forecasting versus prediction

The terms are sometimes used interchangeably.

A forecast is generally an estimate of future conditions based on available information.

A prediction may be broader and may involve models or assumptions about what is likely to occur.

Neither should be treated as certainty.

A forecast is an informed estimate.

Rolling forecasts

A rolling forecast is regularly updated as new information becomes available.

Instead of creating a forecast once and leaving it unchanged, the organisation continuously refreshes the forecast.

For example:

Actual results are added
New information is incorporated
Assumptions are reviewed
Future periods are recalculated

This can provide a more current view of likely performance.

Run rate

A run rate estimates future performance based on the current rate of activity.

For example, if a service currently processes approximately 1,000 cases per month, the current run rate can provide an initial estimate of future workload.

However, run rates can be misleading when conditions are changing.

They should therefore be treated as a starting point rather than a guaranteed outcome.

Forecast accuracy

Forecast accuracy measures how close a forecast was to the eventual actual result.

For example:

Forecast: 92%

Actual: 90%

The difference can be examined to understand why the forecast was inaccurate.

Possible reasons include:

Incorrect assumptions
Unexpected events
Poor data
Structural change
Insufficient historical information
Model limitations

Forecast accuracy should be monitored over time.

Scenario analysis

Scenario analysis examines different possible future conditions.

A common approach is:

Best-case scenario
Base-case scenario
Downside scenario

The labels should not be interpreted as precise probabilities.

They represent different sets of assumptions.

Best-case scenario

The best-case scenario assumes conditions develop favourably.

For example:

Demand remains manageable
Planned improvements are delivered
Technology performs as expected
Dependencies are resolved
Capability improves

Base-case scenario

The base case represents the organisation's central set of assumptions.

It should be realistic rather than deliberately optimistic.

Downside scenario

The downside scenario considers less favourable conditions.

For example:

Demand increases
A critical dependency fails
Implementation is delayed
Capability remains constrained
Technology problems continue

Scenario analysis helps organisations prepare rather than simply react.

Sensitivity analysis

Sensitivity analysis examines how changes in one assumption affect the resulting forecast.

For example:

"What happens to expected service performance if demand increases by 10%?"

Or:

"What happens if the planned process improvement is delayed?"

Sensitivity analysis identifies which assumptions have the greatest influence on expected performance.

Forecasting limitations

Forecasts are only as reliable as the information and assumptions behind them.

Important limitations include:

Poor historical data
Changing conditions
Structural breaks
Unexpected events
Incomplete information
Incorrect assumptions
Model limitations

A forecast should therefore always be accompanied by appropriate context.

Forecasts should support decisions

The purpose of forecasting is not to produce a number that looks precise.

The purpose is to help management prepare for plausible future conditions.

A useful forecast should therefore answer:

What may happen?
Why do we expect it?
What assumptions support the estimate?
What could change the result?
What early signals should we monitor?
What action should we prepare?

4.7 Early-Warning Indicators and Turning Analysis into Action

The ultimate purpose of performance analysis is action.

An organisation that repeatedly identifies problems without responding to them has a measurement system but not an effective performance management system.

Early-warning indicators

An early-warning indicator provides an indication that a future performance problem may be developing.

Examples include:

Increasing backlog
Rising repeat incidents
Increasing processing delays
Declining training completion
Increasing unresolved issues
Growing numbers of overdue actions
Increasing system errors
Deteriorating customer feedback

These indicators can provide management with time to intervene.

Early warning versus lagging results

A lagging measure may show:

Service failure occurred

An early-warning indicator may show:

Backlog has increased significantly for three consecutive periods

The second signal may provide an opportunity to act before service failure becomes widespread.

Emerging risks

Performance analysis can also identify emerging risks.

For example, a gradual deterioration in system availability may not yet have produced a major service failure.

However, the trend may indicate increasing operational risk.

This is why performance and risk measurement should often be considered together.

From insight to action

A practical performance management sequence is:

Measure → Compare → Analyse → Diagnose → Decide → Act → Monitor → Verify

Each stage has a distinct purpose.

Measure: Establish what happened

Compare: Determine how performance relates to expectations

Analyse: Identify patterns and relationships

Diagnose: Investigate likely causes

Decide: Determine the appropriate response

Act: Implement the response

Monitor: Track subsequent performance

Verify: Confirm whether the action produced the intended improvement

Corrective action

A corrective action addresses an existing problem.

For example, if a service process repeatedly fails to meet its required response time, corrective action may address the immediate operational cause.

Preventive action

A preventive action aims to reduce the likelihood of a future problem.

For example, an organisation may strengthen a control or process after identifying a vulnerability before a major failure occurs.

Improvement initiatives

Not every performance issue requires an emergency response.

Some require structured improvement.

An improvement initiative may involve:

Process redesign
Technology enhancement
Capability development
Data improvement
Governance changes
Service redesign
Workflow automation
Clarification of responsibilities

Prioritising action

Organisations rarely have unlimited capacity to address every issue simultaneously.

Actions should therefore be prioritised according to factors such as:

Performance impact
Risk
Customer impact
Urgency
Dependency
Feasibility
Root-cause significance

The most visible problem is not always the most important problem.

Measuring whether action worked

Completing an action is not the same as achieving an improvement.

For example:

Action: New service process implemented

This tells us that the action occurred.

It does not tell us whether the process improved performance.

The organisation should therefore compare performance before and after implementation.

Possible questions include:

Did the KPI improve?
Did the problem recur?
Did quality improve?
Did customer experience improve?
Did the improvement create an unintended consequence?
Has the improvement been sustained?

Closed-loop performance management

A mature performance system creates a closed loop:

Measurement → Analysis → Decision → Action → Result → Measurement

The organisation learns from its actions.

If performance improves, the organisation can identify what contributed to the improvement.

If performance does not improve, the organisation can reassess its assumptions and investigate further.

Performance analysis maturity

A basic organisation may simply report KPI results.

A developing organisation may compare actual performance with targets.

A more mature organisation may analyse trends and root causes.

A stronger organisation may use predictive indicators and scenario analysis.

A highly capable organisation integrates:

Measurement + Analysis + Risk + Forecasting + Decision-Making + Improvement

This creates a more complete performance management capability.

The final principle

Performance measurement tells an organisation what happened.

Performance analysis explains what may be happening and why.

Forecasting helps the organisation consider what may happen next.

Action converts understanding into improvement.

The complete performance analysis cycle can therefore be expressed as:

Measure → Compare → Analyse → Diagnose → Forecast → Decide → Act → Verify → Improve

This is where performance measurement becomes genuine performance management.

Numbers alone do not improve organisations.

Understanding what the numbers mean and acting on that understanding is what creates improvement.

5. Dashboards, Reporting and Business Intelligence

Performance measurement produces information.

Performance dashboards, management reporting and Business Intelligence turn that information into something people can see, understand and use.

A well-designed dashboard should help a person understand performance quickly.

A well-designed report should provide sufficient context for meaningful management discussion.

Business Intelligence should help people explore information, identify patterns and gain insight.

These capabilities are closely connected but they are not identical.

A dashboard provides a visual view of selected performance information.

A report communicates structured information to a defined audience.

Business Intelligence, commonly abbreviated to BI, provides technologies and analytical capabilities that help organisations access, analyse and understand data.

The objective is not to produce attractive screens or large reporting packs.

The objective is to support better understanding and better decisions.

5.1 Corporate Performance Dashboards

A performance dashboard is a visual presentation of selected performance information designed to help users understand the current position and identify matters requiring attention.

A dashboard normally combines KPIs, targets, actual results, trends, status indicators and supporting information.

The best dashboards answer important questions quickly.

For example:

How are we performing?
What has changed?
Where are the problems?
Which areas require attention?
Are we improving or deteriorating?
What should management investigate?

The purpose of a dashboard

A dashboard should reduce the time required to understand performance.

Instead of reading large volumes of raw information, the user should be able to identify important patterns and exceptions quickly.

A dashboard should therefore provide:

Clarity
Context
Comparability
Visibility
Exception identification
Trend information
Appropriate detail

Executive dashboards

An executive dashboard provides senior leaders with a high-level view of organisational performance.

It normally focuses on a relatively small number of strategically important measures.

The executive audience usually needs to know:

Overall performance
Major changes
Significant exceptions
Strategic risks
Important trends
Areas requiring decisions

An executive dashboard should not attempt to reproduce every operational measure.

Strategic dashboards

A strategic dashboard focuses on progress against strategic objectives and priorities.

It may include:

Strategic objectives
Strategic KPIs
Target achievement
Major initiatives
Outcome measures
Significant risks
Strategic milestones

The emphasis is on whether the organisation is moving towards its intended strategic position.

Operational dashboards

An operational dashboard provides more detailed information for managers responsible for day-to-day performance.

It may include:

Work volumes
Backlogs
Response times
Resolution times
Quality measures
Capacity
Service levels
Current exceptions

Operational dashboards may require more frequent refreshes than executive dashboards.

Departmental dashboards

A departmental dashboard focuses on the performance of a particular function.

For example:

IT
Customer service
Human resources
Operations
Quality
Risk
Projects
Procurement
Compliance

The dashboard should reflect the decisions made by that function.

Specialist dashboards

Specialist dashboards may focus on a specific performance area.

Examples include:

Service management dashboard
Project portfolio dashboard
Risk dashboard
Quality dashboard
Customer experience dashboard
Technology performance dashboard

These dashboards may contain more technical information than an executive dashboard.

One dashboard does not fit everyone

Different users need different levels of detail.

A senior executive may need a concise overview.

An operational manager may need detailed process information.

An analyst may need the ability to drill into individual records.

Trying to satisfy all audiences through one dashboard often produces an unnecessarily complicated design.

Dashboard hierarchy

A useful approach is to create levels.

Level 1: Executive overview

Level 2: Strategic or functional performance

Level 3: Operational detail

Level 4: Detailed analytical information

This allows users to move from summary to detail without overwhelming the initial view.

Dashboard as a decision tool

The most important question when designing a dashboard is:

What decisions will this dashboard support?

If the answer is unclear, the dashboard may simply become a collection of numbers.

A dashboard should be designed around the user's information needs rather than around the data that happens to be available.

5.2 What Goes Into a Performance Dashboard?

A dashboard should contain the information necessary to understand performance without unnecessary clutter.

KPI cards

A KPI card is a visual element showing a key performance measure.

It may display:

KPI name
Actual result
Target
Variance
Status
Trend

For example:

Service Requests Resolved Within Required Time

Actual: 92%

Target: 95%

Variance: -3 percentage points

Status: Attention required

The user can immediately see the basic performance position.

Actual performance

The actual result shows what has happened.

Actual results should always be interpreted in context.

A number without a reference point can be difficult to understand.

Target

The target establishes the expected level.

Showing actual and target together allows the user to assess performance quickly.

Variance

Variance shows the difference between actual and target or another reference point.

This helps identify gaps.

Trend

A trend shows movement over time.

A KPI may currently be within target but deteriorating.

Another KPI may currently be below target but improving.

The trend provides information that a single result cannot provide.

Thresholds and tolerances

Thresholds help identify when management attention may be required.

Tolerances help distinguish normal variation from meaningful change.

These should be clearly defined.

Forecasts

Where appropriate, dashboards can include forecasts.

A forecast can show the expected future direction of performance based on current information and assumptions.

Forecasts should be clearly distinguished from actual results.

Users should never confuse an estimate with an observed result.

Alerts

An alert identifies an important condition requiring attention.

Examples include:

KPI below threshold
Critical issue overdue
Major service disruption
Significant deterioration
Risk condition exceeded
Project milestone delayed

Alerts should be selective.

If everything produces an alert, users eventually stop paying attention.

Commentary

A short commentary can explain significant changes.

For example:

"Performance declined following the introduction of the new service workflow. The main increase occurred within the approval stage."

The commentary should explain the result rather than simply repeat it.

Status indicators

Common status indicators include:

Green
Amber
Red

Some organisations also use:

Blue for information
Grey for unavailable
White for not applicable

The exact colour scheme matters less than consistency.

Colour should never be the only method of communicating meaning.

Summary information

A dashboard may also include:

Key messages
Major exceptions
Priority actions
Significant risks
Recent changes
Upcoming milestones

These elements help connect measurement with management action.

5.3 Dashboard Visualisation and Interaction

Visualisation is the process of presenting data in a form that makes patterns and relationships easier to understand.

Good visualisation reduces cognitive effort.

Poor visualisation creates confusion.

Tables

Tables are useful when users need precise values.

They are particularly appropriate when:

Exact numbers matter
Many categories must be compared
Users need to identify individual records
The audience is familiar with the data

Tables become difficult to use when they contain excessive information.

Bar charts

Bar charts are useful for comparing categories.

For example:

Performance by department
Incidents by service
Quality results by process
Completion rates by team

They make differences between categories relatively easy to see.

Line charts

Line charts are useful for showing trends over time.

They can reveal:

Improvement
Deterioration
Stability
Volatility
Sudden changes

A line chart should normally have a meaningful time sequence.

Heat maps

A heat map uses visual intensity to highlight differences across a matrix.

It can be useful for:

Risk analysis
Performance comparisons
Process analysis
Resource allocation
Issue concentration

Heat maps should be designed carefully because excessive visual variation can make them difficult to interpret.

Gauges

Gauges can communicate the position of a measure against a defined range.

However, they often consume considerable dashboard space.

A simple KPI card or bar may communicate the same information more efficiently.

Traffic-light indicators

Traffic lights provide simple status communication.

For example:

Green: within expected range
Amber: attention required
Red: intervention required

They are effective for quick scanning but provide little information about the size or direction of a change.

They should therefore be combined with actual values and trends.

Sparklines

A sparkline is a small trend visual embedded alongside a measure.

It can show the general direction of performance without requiring a large chart.

Sparklines are useful when many KPIs need to be displayed in a compact space.

Scorecards

A scorecard provides a structured view of performance against defined objectives.

It may contain:

Objectives
KPIs
Actuals
Targets
Status
Trends
Commentary

A scorecard is particularly useful when the organisation wants to connect measurement directly to strategic objectives.

Filters

Filters allow users to select specific information.

Examples include:

Time period
Department
Service
Location
Customer group
Project
Priority

Filters can make dashboards powerful.

Too many filters can make them complicated.

Drill-down

Drill-down allows a user to move from summary information into greater detail.

For example:

Corporate service performance → IT performance → Application performance → Service → Individual incidents

Drill-down should support investigation.

It should not simply provide more data for its own sake.

Drill-through

Drill-through takes the user from one visual or summary to another detailed report or underlying record.

This is particularly useful when the user needs to investigate an exception.

Hierarchy

A good dashboard should have a clear visual hierarchy.

The most important information should receive the greatest visual prominence.

Users should be able to identify:

Overall status
Major exceptions
Important trends
Supporting detail

This reduces unnecessary searching.

Avoid dashboard decoration

A dashboard should not become a graphic design exercise where visual effects are prioritised over information.

Every visual element should have a purpose.

If a chart does not help users understand performance, it should be questioned.

Accessibility

Dashboards should also consider accessibility.

Important information should not depend solely on colour.

Text labels, clear headings and appropriate contrast can help users understand information more effectively.

5.4 Management Reporting

A management report is a structured communication of performance information prepared for a defined audience and purpose.

Reports are different from dashboards.

A dashboard is usually designed for rapid visual interpretation.

A report may provide more context, explanation and narrative.

Executive reporting

Executive reports provide senior management with a concise view of important organisational matters.

They may include:

Strategic performance
Significant KPI movements
Major exceptions
Important risks
Key initiatives
Decisions required
Priority actions

The emphasis should be on what management needs to know and decide.

Operational reporting

Operational reports provide more detailed information about current performance.

They may include:

Work volumes
Process performance
Service levels
Backlogs
Quality
Incidents
Issues
Capacity

The information should support operational management.

Monthly reporting

Monthly reporting can provide a regular management rhythm.

A monthly report may include:

Current performance
Previous period
Target
Variance
Trend
Significant events
Commentary
Actions

The exact frequency should depend on the operating environment.

Quarterly reporting

Quarterly reporting can provide a broader view of performance.

It may allow greater focus on:

Strategic progress
Longer-term trends
Major initiatives
Capability development
Risk changes
Improvement outcomes

Annual reporting

Annual performance reporting provides a longer-term perspective.

It can examine:

Strategic progress
Major outcomes
Organisational capability
Major improvement programmes
Quality
Customer experience
Workforce performance
Technology performance
Risk and compliance

Performance packs

A performance pack is a collection of reports, dashboards and supporting analysis prepared for a formal performance review.

A performance pack should be structured.

For example:

1. Executive summary

2. Strategic performance

3. Key exceptions

4. Functional performance

5. Risk and compliance

6. Major projects

7. Customer and workforce performance

8. Technology and operational performance

9. Actions and decisions

The structure should reflect the organisation's governance model.

Exception reporting

Exception reporting focuses attention on matters outside expected conditions.

This can significantly reduce reporting effort.

Instead of explaining every KPI in equal detail, the report can concentrate on:

Significant deterioration
Significant improvement
Threshold breaches
Persistent underperformance
Emerging risks
Important changes

Narrative reporting

Numbers rarely explain themselves.

A useful narrative should answer:

What happened?
Why did it happen?
Why does it matter?
What is likely to happen next?
What action is being taken?

This creates a bridge between measurement and management.

Avoid reporting overload

A large report is not necessarily a useful report.

Excessive information can make important issues harder to see.

Management reporting should therefore prioritise relevance.

A useful test is:

If this information disappeared, would the audience lose something important for understanding or decision-making?

If the answer is no, the information may not need to be included in the main report.

5.5 Performance Commentary and Performance Reviews

Performance commentary explains what the reported information means.

A dashboard may show that performance has fallen.

Commentary should explain what the organisation currently understands about that change.

What happened?

Start with the evidence.

For example:

"Service performance declined from 95% to 91% during the reporting period."

This establishes the fact.

Why did it happen?

Next, provide the evidence-based explanation.

For example:

"The decline was concentrated within two service categories following an increase in complex requests."

The explanation should distinguish confirmed causes from assumptions.

Why does it matter?

The commentary should explain significance.

For example:

"The decline has increased the number of customers waiting beyond the required response period."

What happens next?

The report should explain the expected direction.

For example:

"Additional process capacity is being introduced and performance will be reviewed during the next reporting cycle."

What action is required?

Where management action is needed, the report should make it explicit.

For example:

"Management approval is required to implement the proposed process change."

This makes the report actionable.

Performance review meetings

A performance review is a structured forum in which performance information is examined and management decisions are made.

A typical review may follow this sequence:

1. Review previous actions

2. Review overall performance

3. Examine significant exceptions

4. Analyse trends

5. Discuss root causes

6. Review risks

7. Consider forecasts

8. Agree decisions

9. Assign actions

10. Confirm follow-up

Executive reviews

Executive reviews should focus on matters requiring leadership attention.

The discussion should not become a line-by-line reading of the dashboard.

The dashboard should provide the evidence.

The meeting should provide the discussion.

Business reviews

Business or functional reviews can examine performance in greater depth.

They may consider:

Objectives
KPIs
Process performance
Customer experience
Workforce
Quality
Risk
Projects
Technology
Improvement actions

Operational reviews

Operational reviews focus on immediate performance.

They may examine:

Current workload
Backlogs
Incidents
Service levels
Process bottlenecks
Resource constraints
Quality issues

Asking the right questions

Good performance reviews ask questions such as:

What changed?
Why did it change?
Is the change temporary?
Is it affecting other measures?
What evidence supports the explanation?
What is the risk if nothing changes?
What action is already underway?
What decision is required?

Avoiding blame

A performance review should create accountability without automatically creating a blame culture.

The purpose is to understand performance and improve it.

Where accountability is required, it should be clear.

However, a culture in which people hide problems to avoid criticism can damage the measurement system itself.

Reliable performance management depends on people being willing to surface problems.

5.6 Business Intelligence and Performance Analytics

Business Intelligence provides technologies and methods for turning organisational data into useful information and insight.

BI can support reporting, analysis, visualisation and decision-making.

Reporting versus analytics

Reporting primarily communicates what happened.

Analytics investigates what the information means.

For example:

Reporting: Service performance was 91%

Analytics: Performance declined mainly within two service categories and the deterioration began after a process change

Both are valuable.

Analytics adds interpretation.

Descriptive analytics

Descriptive analytics examines what has happened.

Examples include:

Current KPI values
Historical trends
Performance summaries
Volume analysis
Status reporting

It provides visibility.

Diagnostic analytics

Diagnostic analytics investigates why something happened.

Examples include:

Root-cause analysis
Variance analysis
Segmentation
Correlation analysis
Process analysis

It provides explanation.

Predictive analytics

Predictive analytics uses historical and current information to estimate future conditions.

Examples include:

Forecasting service demand
Predicting workload
Identifying likely performance deterioration
Forecasting capacity requirements

Predictive analysis should always be understood in terms of its assumptions and limitations.

Prescriptive analytics

Prescriptive analytics goes further by considering possible actions and their potential consequences.

It may help answer:

"What could we do?"

or:

"Which intervention may produce the desired result under these assumptions?"

Prescriptive analysis can support decision-making but should not remove appropriate management judgement.

Self-service BI

Self-service Business Intelligence allows users to access and analyse approved organisational data without depending entirely on specialist reporting teams.

This can improve speed and flexibility.

However, self-service BI also creates governance risks.

Users may create:

Different definitions
Uncontrolled calculations
Duplicate reports
Inconsistent data sources
Conflicting KPIs

Self-service therefore needs appropriate governance.

Performance analytics

Performance analytics combines measurement with deeper investigation.

It may examine:

Trends
Variances
Segments
Relationships
Patterns
Exceptions
Root causes
Forecasts

The objective is to move from information to insight.

Data storytelling

Data storytelling is the practice of communicating important findings using evidence, context and a clear narrative.

A useful data story may follow:

What happened → Why it matters → Why it happened → What may happen next → What should be considered

The narrative should remain faithful to the evidence.

Avoid false precision

Advanced analytics can produce highly precise-looking numbers.

Precision does not necessarily mean accuracy.

A forecast of 92.37% may look more authoritative than 92%.

However, if the underlying data is uncertain, the additional decimal places do not make the forecast more reliable.

The presentation of analytical results should reflect the quality of the underlying evidence.

5.7 Dashboard, Reporting and BI Technology

Technology enables organisations to collect, transform, analyse and present performance information.

However, technology does not automatically create good performance management.

Spreadsheets

Spreadsheets can be useful for:

Prototyping
Small-scale analysis
Temporary reporting
Manual data preparation
Simple dashboards

They can become problematic when they are used as the primary enterprise measurement system without appropriate controls.

Common risks include:

Manual errors
Duplicate versions
Weak access control
Broken formulas
Poor traceability
Inconsistent definitions

Business Intelligence platforms

BI platforms can provide:

Data integration
Interactive dashboards
Automated calculations
Drill-down
Filtering
Trend analysis
Scheduled refreshes
Controlled reporting

They can significantly improve performance reporting when implemented properly.

Automated reporting

Automated reporting reduces repetitive manual activity.

For example, a report may automatically:

Retrieve approved data
Refresh calculations
Update dashboards
Apply defined thresholds
Generate reports
Distribute information to authorised users

Automation can improve consistency and speed.

However, automated reporting should still include appropriate controls.

Automation can reproduce an error just as efficiently as it reproduces a correct calculation.

Data refresh

A dashboard should make clear when its information was last refreshed.

Users need to know whether they are looking at:

Real-time information
Near-real-time information
Previous-day information
Weekly information
Monthly information

A dashboard that looks current but contains old data can create serious misunderstanding.

Performance management platforms

Some organisations use dedicated performance management platforms.

These may provide:

KPI management
Target management
Scorecards
Dashboards
Workflow
Performance reviews
Action tracking
Reporting
Governance

The appropriate technology depends on organisational requirements.

Technology architecture

A typical performance information architecture may include:

Source Systems → Data Integration → Data Storage → Data Transformation → Analytics → Dashboards and Reports → Users → Decisions → Actions

Each stage matters.

Poor source data can undermine the entire chain.

Poor integration can create inconsistent information.

Poor transformation can produce incorrect calculations.

Poor dashboard design can hide important findings.

Single source of truth

A single source of truth is a trusted and controlled source for a particular piece of information or defined data domain.

The phrase should be used carefully.

It does not necessarily mean that every organisation must have one physical database.

It means that users should know which approved source and definition should be used for a particular measure.

Common technology mistakes

Organisations often make mistakes such as:

Buying technology before defining requirements
Automating poor processes
Building dashboards before defining KPIs
Creating multiple versions of the same measure
Allowing uncontrolled calculations
Ignoring data quality
Failing to define ownership
Designing for appearance rather than decisions
Providing excessive information
Underestimating user adoption

Technology should support the performance management operating model.

It should not become the operating model.

Technology should follow purpose

A useful sequence is:

Business Purpose → Performance Questions → Objectives → Measures → Data Requirements → Reporting Requirements → Technology Requirements

This prevents technology from driving the measurement system.

The complete dashboard and reporting cycle

A mature reporting environment can be viewed as:

Strategy → Objectives → KPIs → Data → Analysis → Dashboard → Report → Review → Decision → Action → Outcome → Measurement

The dashboard is therefore only one part of the wider performance system.

The ultimate principle

A dashboard is not successful because it looks impressive.

A report is not successful because it is comprehensive.

A BI platform is not successful because it contains large quantities of data.

Success comes from helping people understand performance and take appropriate action.

The strongest performance environments combine:

Reliable Data + Clear Measures + Useful Analysis + Effective Visualisation + Meaningful Commentary + Structured Reviews + Decisive Action

When these elements work together, performance information becomes an organisational capability rather than simply a reporting activity.

6. Measuring Every Dimension of Corporate Performance

Corporate performance is multidimensional.

An organisation cannot understand its overall performance by examining one category of measurement.

Customer experience may be improving while operational quality is declining.

Employee capability may be strengthening while technology reliability is deteriorating.

Project delivery may be progressing while important risks are increasing.

Quality may be improving while process performance is becoming slower.

Performance measurement must therefore provide a sufficiently broad view of the organisation without becoming an uncontrolled collection of measures.

This chapter examines the major dimensions of organisational performance and explains how they can be measured as part of an integrated corporate performance framework.

The objective is not to measure everything.

The objective is to understand the dimensions that matter and connect them into a coherent view of organisational performance.

6.1 Customer and Service User Performance

Customers and service users experience the organisation through its products, services, processes, people and technology.

Customer performance measurement therefore provides an important external view of organisational performance.

Internal measures can show that a process is operating according to specification.

Customer measures can reveal whether the service is actually meeting people's needs.

Customer satisfaction

Customer Satisfaction, commonly abbreviated to CSAT, measures how satisfied customers are with a product, service or interaction.

It is often collected through surveys.

A simple question may ask customers to rate their satisfaction on a defined scale.

CSAT can be useful because it provides direct feedback from the people receiving the service.

However, satisfaction should not be interpreted in isolation.

A customer may report satisfaction even when an underlying process is inefficient.

Another customer may report dissatisfaction because of an issue outside the immediate control of the service team.

The measure should therefore be considered alongside operational and quality information.

Net Promoter Score

Net Promoter Score, commonly abbreviated to NPS, is a customer experience measure based on customers' willingness to recommend an organisation, product or service.

It can provide a broad indication of customer sentiment.

However, NPS is not a complete measure of customer experience.

It should be considered alongside other measures such as satisfaction, complaints, effort and service performance.

Customer Effort Score

Customer Effort Score, or CES, measures how easy or difficult customers perceive it to be to complete an interaction or achieve a desired outcome.

This can be particularly useful for identifying unnecessary complexity.

For example, a service may meet its response-time target while still requiring customers to complete multiple unnecessary steps.

Customer effort can reveal this problem.

Complaints

Complaints are an important source of performance information.

Measures may include:

Number of complaints
Complaint rate
Complaint categories
Complaint resolution time
Repeat complaints
Escalated complaints
Percentage resolved within required time
Complaints by service or process

A rise in complaints may indicate deteriorating performance.

However, complaint volume should be interpreted carefully.

An increase may also occur because customers have gained easier access to complaint channels.

First-contact resolution

First-contact resolution measures the percentage of customer issues resolved during the initial interaction without requiring further contact.

It can provide insight into service effectiveness.

Low first-contact resolution may indicate:

Inadequate information
Poor process design
Lack of employee authority
Training gaps
Technology limitations
Complex customer requirements

Customer retention and churn

Customer retention measures whether customers continue using a service.

Churn describes customers who stop using a service.

These measures can provide useful information about customer experience and service performance.

However, they should be interpreted carefully because customers may leave for many different reasons.

Customer journey performance

A customer journey represents the sequence of interactions a customer experiences while attempting to achieve an objective.

For example:

Discover → Enquire → Apply → Receive Service → Resolve Issue → Complete

Each stage can have its own performance measures.

This helps organisations identify where problems occur within the overall journey.

Customer journey measures

Possible measures include:

Time spent at each stage
Customer effort
Drop-off rates
Repeated contacts
Error rates
Waiting time
Satisfaction
Resolution rate

Journey-based measurement is particularly useful because customers experience the whole journey rather than individual organisational departments.

Service quality

Customer performance should be connected to service quality.

A service that is fast but inaccurate may create poor customer outcomes.

A service that is accurate but extremely difficult to access may also create poor customer experience.

A balanced customer measurement system therefore considers:

Speed + Quality + Accessibility + Ease + Resolution + Experience

Customer feedback as evidence

Customer feedback provides valuable qualitative information.

Not every important issue can be represented by a number.

Comments, survey responses, complaints and interviews can reveal themes that quantitative measures may not identify.

Qualitative information should therefore complement quantitative measurement.

6.2 People and Workforce Performance

People are central to organisational performance.

Workforce measurement should therefore examine capability, engagement, productivity, retention, wellbeing-related organisational indicators and the ability of the workforce to support organisational objectives.

The purpose is not to reduce people to numbers.

The purpose is to understand whether the organisation has the capability and capacity required to perform effectively.

Employee engagement

Employee engagement measures the degree to which employees are connected to their work and organisation.

Engagement surveys may examine:

Commitment
Motivation
Leadership
Communication
Recognition
Development
Organisational support

Engagement results should be analysed alongside other workforce information.

Employee experience

Employee experience refers to the overall experience employees have across their interactions with the organisation.

This may include:

Recruitment
Onboarding
Management
Technology
Workplace processes
Development
Internal services
Career progression
Exit

Measuring employee experience can reveal friction within organisational processes.

Employee turnover

Employee turnover measures the rate at which employees leave an organisation.

It can provide useful information about workforce stability.

However, turnover is not inherently negative.

Some movement may be expected.

The important questions include:

Which employees are leaving?
Why are they leaving?
Which roles are affected?
Is turnover increasing?
Is turnover concentrated in critical capabilities?
Is the organisation able to replace required capability?

Employee retention

Retention measures the ability of an organisation to retain employees over time.

Retention should be analysed by relevant segments rather than relying only on an organisational average.

Absence

Absence measures can provide information about workforce availability.

Possible measures include:

Absence rate
Frequency of absence
Average duration
Absence by team
Long-term versus short-term absence

Absence data should be interpreted responsibly.

It may be influenced by many factors and should not automatically be treated as evidence of poor individual performance.

Recruitment performance

Recruitment measures can include:

Time to hire
Time to fill
Candidate conversion rates
Offer acceptance
Recruitment process duration
Quality of hire
Vacancy duration

The purpose is to understand whether the organisation can obtain the capabilities it requires.

Training and capability

Training measures can include:

Training completion
Mandatory training completion
Skills attainment
Certification status
Capability assessment
Development plan completion

Completion alone is not enough.

An employee completing training does not necessarily mean that capability has improved.

Where possible, organisations should assess whether learning translated into improved capability or performance.

Workforce productivity

Workforce productivity examines the relationship between useful outputs and resources used.

The basic concept can be expressed as:

Productivity = Useful Output ÷ Resources Used

Productivity should not be reduced to simple activity counts.

A person processing more cases may not be more productive if the additional cases require rework or generate quality problems.

Productivity should therefore be considered alongside quality and outcomes.

Workforce utilisation

Utilisation measures the extent to which available capacity is being used.

It can help organisations understand workload and resource allocation.

However, maximum utilisation is not always desirable.

Teams may require capacity for:

Unexpected demand
Problem solving
Improvement
Training
Knowledge sharing
Resilience

A permanently overloaded workforce can become a performance risk.

Capability maturity

Organisations should also measure whether workforce capability is developing.

Possible measures include:

Capability coverage
Critical skills availability
Skills gaps
Succession coverage
Capability maturity
Cross-training

These measures provide a forward-looking view of workforce performance.

6.3 Process, Operational and Service Performance

Processes convert inputs into outputs and outcomes.

Process and operational performance measurement therefore provides a central view of how work actually flows through the organisation.

Process efficiency

Efficiency concerns the relationship between outputs and resources used.

A process may become more efficient when it achieves the required output using fewer unnecessary steps, delays or resources.

Process effectiveness

Effectiveness concerns whether the process achieves its intended outcome.

A process can be efficient but ineffective.

For example, a process may complete cases extremely quickly but produce incorrect results.

Good performance measurement therefore considers both efficiency and effectiveness.

Cycle time

Cycle time measures the time required to complete a process or activity.

It can reveal delays and bottlenecks.

Cycle time may be measured at different levels:

End-to-end process
Process stage
Transaction
Service request
Approval
Resolution

Definitions must be clear.

Throughput

Throughput measures the amount of work completed during a defined period.

Examples include:

Cases processed
Requests completed
Transactions handled
Items inspected
Service tickets resolved

Throughput should be considered alongside quality.

High throughput with high error rates is not necessarily strong performance.

Capacity

Capacity describes the amount of work an organisation, process, team or system can reasonably handle.

Capacity measurement helps answer:

How much work can we handle?
How much capacity is currently available?
Where are constraints developing?
What happens if demand increases?

Bottlenecks

A bottleneck is a point in a process that limits overall flow.

Bottlenecks may occur because of:

Limited specialist capability
Approval requirements
Technology constraints
Manual processing
Supplier dependency
Excessive workload

Identifying bottlenecks can reveal opportunities for improvement.

Backlogs

A backlog is accumulated work that has not yet been completed.

Measures may include:

Total backlog
Backlog age
New versus resolved items
Critical backlog
Average backlog duration

A growing backlog may be an early-warning indicator of declining operational performance.

Response time

Response time measures how quickly an organisation responds to a request or event.

It is particularly useful in customer service and IT service environments.

Resolution time

Resolution time measures how long it takes to resolve an issue or complete a defined activity.

The definition must specify when the clock starts and ends.

Service levels

A Service Level Agreement, or SLA, defines agreed service expectations between parties.

Service performance may therefore include:

SLA achievement
Response performance
Resolution performance
Availability
Service request completion
Incident management

Availability

Availability measures whether a service or system is available when required.

It is particularly important for technology-enabled services.

Availability should be measured using a clearly defined calculation and agreed service window.

Reliability

Reliability concerns the ability of a service, process or system to perform consistently over time.

A service may have high availability but still experience frequent interruptions.

Reliability measures can help reveal this distinction.

Operational resilience

Operational resilience is the ability of an organisation to continue delivering important services when disruption occurs.

Measures may include:

Recovery performance
Critical service continuity
Recovery testing
Dependency resilience
Incident response
Recovery time

Process quality

Operational measurement should include quality.

Useful measures include:

First-time-right
Rework
Defects
Errors
Failed transactions
Process exceptions

The strongest operational measurement systems therefore combine:

Speed + Volume + Capacity + Quality + Reliability + Outcomes

6.4 Quality, Risk and Compliance Performance

Quality, risk and compliance provide another essential dimension of corporate performance.

An organisation may achieve high levels of activity while producing poor-quality results or exposing itself to significant risk.

Quality performance

Quality measures whether outputs and services meet defined requirements.

Possible measures include:

Defect rate
Error rate
Rework
First-time-right
Non-conformities
Quality inspection results
Customer complaints
Corrective action completion

First-time-right

First-time-right measures the percentage of outputs completed correctly without requiring rework.

It is a powerful measure because it combines efficiency and quality.

High first-time-right performance generally indicates that the process is producing the intended result without unnecessary repetition.

Rework

Rework occurs when work must be performed again because the original output did not meet requirements.

High rework may indicate:

Poor process design
Insufficient training
Incomplete information
Weak controls
Technology problems
Unclear requirements

Non-conformity

A non-conformity occurs when a defined requirement is not met.

Non-conformities may be identified through:

Quality checks
Audits
Inspections
Customer feedback
Operational monitoring

The organisation should track both the occurrence and resolution of non-conformities.

Risk performance

Risk performance examines whether important organisational risks are being identified, managed and monitored.

Possible measures include:

Number of significant risks
Risk exposure
Risk treatment completion
Overdue risk actions
Control effectiveness
Control failures
Risk trend

Key Risk Indicators

A Key Risk Indicator, or KRI, provides information about conditions that may indicate changing risk.

Examples include:

Increasing unresolved critical issues
Increasing control failures
Growing numbers of overdue actions
Deteriorating system resilience
Increasing supplier dependency

KRIs can complement KPIs by providing an early view of potential threats to performance.

Risk appetite

Risk appetite describes the amount and type of risk an organisation is prepared to accept in pursuit of its objectives.

Performance measurement should be aligned with the organisation's risk appetite.

A KPI may show acceptable current performance while a related risk indicator may show that the current position is becoming increasingly fragile.

Risk tolerance

Risk tolerance defines the acceptable level of variation around a risk position.

Exceeding tolerance may trigger management action or escalation.

Residual risk

Residual risk is the risk remaining after controls and treatments have been applied.

Measuring residual risk helps management understand whether current controls are producing the intended reduction in exposure.

Risk treatment

Risk treatment refers to actions taken to address a risk.

Measures may include:

Treatment completion
Overdue treatments
Treatment effectiveness
Residual risk after treatment

Completing a risk action does not automatically mean that the risk has been reduced.

Effectiveness should be assessed.

Compliance performance

Compliance measurement examines whether required obligations are being met.

Possible measures include:

Compliance rate
Overdue compliance actions
Audit findings
Control testing
Mandatory activity completion
Corrective action closure

Audit findings

Audit findings can provide valuable evidence about weaknesses in processes and controls.

Measures may include:

Number of findings
Finding severity
Repeat findings
Overdue findings
Closure rate
Average closure time

Repeated findings can indicate that previous corrective actions did not address the underlying cause.

Integrated quality, risk and compliance

Quality, risk and compliance should not operate as completely separate measurement systems.

A recurring quality failure may create risk.

A control weakness may create quality problems.

A compliance failure may reveal a process weakness.

Integrated analysis helps organisations understand these relationships.

6.5 Project and Programme Performance

Projects and programmes temporarily bring together people, processes, technology and resources to achieve defined objectives.

Their performance therefore needs to be measured differently from routine operational activity while still remaining connected to organisational performance.

Project scope

Scope defines what the project is intended to deliver.

Scope performance examines whether the project is delivering the agreed requirements.

Possible measures include:

Requirements completed
Requirements accepted
Scope changes
Outstanding requirements
Deliverable completion

Schedule

Schedule performance examines whether planned milestones are being achieved when expected.

Measures may include:

Milestone achievement
Planned versus actual dates
Delayed activities
Critical path performance
Schedule variance

Milestones

A milestone is a significant point or achievement within a project.

Milestones help management understand whether important stages have been completed.

Project quality

Project quality measures whether deliverables meet defined requirements.

Possible measures include:

Defects
Acceptance rate
Rework
Testing completion
Requirements compliance

Project risks

Projects often contain significant risks.

Measures may include:

Open risks
High-priority risks
Risk treatment completion
Risk ageing
Emerging risks

Project issues

An issue is a problem that has already occurred and requires resolution.

Issues differ from risks.

A risk may happen.

An issue has already happened.

Project reporting should therefore distinguish between:

Risks → Potential future problems

Issues → Existing problems

Dependencies

Projects often depend on other teams, systems, suppliers or decisions.

Dependency measures can identify:

Overdue dependencies
Critical dependencies
Dependency owners
Dependency impact

Dependency management is particularly important for complex transformation programmes.

Benefits

A benefit is a measurable improvement expected to result from a project or programme.

Benefits should be defined before implementation where possible.

Examples include:

Improved service quality
Reduced process time
Improved customer experience
Increased system reliability
Improved workforce capability

Benefits realisation

Benefits realisation measures whether expected improvements actually occur.

This is important because successful project delivery does not automatically guarantee successful organisational outcomes.

A project may deliver all its technical requirements but fail to produce the expected operational improvement.

Programme performance

A programme coordinates related projects and activities to achieve broader outcomes.

Programme performance should therefore examine:

Overall objectives
Project interdependencies
Strategic alignment
Benefits
Risks
Capability
Organisational readiness

The focus moves from individual project delivery to the combined outcome.

6.6 Technology and IT Performance

Technology supports many organisational processes and services.

Technology performance therefore needs to be measured not only from a technical perspective but also in terms of the services and outcomes that technology enables.

IT availability

Availability measures whether IT services are available when required.

Examples include:

Application availability
Infrastructure availability
Network availability
Service availability

Availability should be defined using appropriate service windows and agreed measurement rules.

Incidents

An incident is an unplanned interruption or reduction in the quality of an IT service.

Measures may include:

Incident volume
Incident severity
Response time
Resolution time
Repeat incidents
Major incidents

Service requests

A service request is a user request for a defined service or standard fulfilment activity.

Measures may include:

Request volume
Completion time
SLA achievement
Backlog
First-time completion

Changes

A change is an addition, modification or removal that may affect an IT service.

Change performance can include:

Successful changes
Failed changes
Emergency changes
Change-related incidents
Change completion
Unauthorised changes

Problems

A problem is the underlying cause or potential cause of one or more incidents.

Problem management measures may include:

Open problems
Problem ageing
Root-cause identification
Known errors
Recurring incidents
Corrective action completion

Service levels

IT services may be measured against defined service levels.

Measures may include:

Availability
Response
Resolution
Request fulfilment
Service quality

Application performance

Application measures may include:

Response time
Availability
Error rates
Transaction success
Performance degradation
User experience

Infrastructure performance

Infrastructure measures may include:

Availability
Capacity
Utilisation
Performance
Fault frequency
Recovery

Digital performance

Digital services can be measured using:

Availability
Response time
Completion rates
Error rates
User satisfaction
Customer effort
Accessibility
Digital journey performance

Technology risk

Technology risk measures may include:

Critical vulnerabilities
Unsupported technology
System dependencies
Recovery capability
Control failures
Technology incidents
Resilience gaps

Business and IT alignment

Technology performance should ultimately connect to organisational performance.

For example:

IT availability → Service availability → Customer experience → Organisational outcome

This prevents IT measurement from becoming disconnected from the services it supports.

6.7 Supplier, Vendor and Integrated Corporate Performance

Many organisations depend on suppliers and external service providers.

Supplier performance therefore forms an important part of overall corporate performance.

Supplier quality

Quality measures may include:

Defect rates
Service quality
Rework
Non-conformities
Corrective action

Delivery performance

Delivery measures may include:

On-time delivery
Milestone achievement
Service availability
Completion performance
Delivery delays

Supplier responsiveness

Responsiveness measures may include:

Response time
Issue resolution time
Escalation response
Support responsiveness

Service level performance

Where supplier agreements contain defined service levels, organisations should monitor actual performance against those requirements.

Possible measures include:

SLA achievement
Response compliance
Resolution compliance
Availability
Service quality

Supplier risk

Supplier risk measures may include:

Critical supplier dependencies
Open supplier risks
Overdue corrective actions
Service continuity risks
Dependency concentration
Resilience weaknesses

Supplier performance should therefore consider both current service delivery and future resilience.

Contract performance

Contract performance can include whether suppliers are meeting agreed obligations.

The emphasis should be on service delivery, quality, compliance, responsiveness and agreed requirements.

Integrated corporate performance

The dimensions discussed throughout this chapter should not exist as isolated measurement silos.

A complete performance view brings them together.

For example:

Customer Performance

↓

People Performance

↓

Process Performance

↓

Quality Performance

↓

Risk and Compliance

↓

Project Performance

↓

Technology Performance

↓

Supplier Performance

These dimensions interact.

A technology failure can affect a process.

A process problem can affect customers.

A capability gap can affect quality.

A supplier problem can affect technology.

A project delay can increase operational risk.

The performance ecosystem

Organisational performance is therefore better understood as an interconnected system.

A useful model is:

People + Processes + Technology + Suppliers + Governance → Outputs → Customer and Organisational Outcomes

The exact relationships will vary between organisations.

The important point is that performance dimensions influence one another.

Avoiding isolated KPIs

A common problem is measuring each function independently.

For example:

Customer service measures customer satisfaction
IT measures availability
Operations measures throughput
HR measures workforce metrics
Quality measures defects
Risk measures risk exposure

Each function may report green performance while the overall customer experience remains poor.

This can happen because functional optimisation does not always produce end-to-end optimisation.

End-to-end performance

End-to-end performance examines the complete journey from initial requirement through to final outcome.

For example:

Customer Request → Intake → Processing → Approval → Fulfilment → Completion → Customer Outcome

Every stage contributes to the final result.

Measuring only one stage can hide problems elsewhere.

Corporate performance scorecard

A corporate scorecard can bring major dimensions together.

For example:

Dimension	Example Performance Questions
Customer	Are customers receiving the required experience and service quality?
People	Do we have the capability, capacity and engagement required?
Process	Are critical processes efficient, effective and reliable?
Quality	Are outputs meeting required standards?
Risk	Are significant risks controlled within acceptable boundaries?
Compliance	Are important obligations being met?
Projects	Are strategic initiatives delivering their intended outcomes?
Technology	Are technology-enabled services reliable and effective?
Suppliers	Are critical external providers meeting required standards?

The exact measures should be tailored to the organisation.

Balanced measurement

A strong corporate performance system should avoid overemphasising one dimension.

If the organisation focuses only on speed, quality may suffer.

If it focuses only on quality, responsiveness may suffer.

If it focuses only on internal performance, customer experience may suffer.

If it focuses only on current results, future capability may suffer.

Balanced measurement provides a broader and more reliable view.

The integrated performance model

A practical model is:

Strategy → Objectives → Dimensions → KPIs → Targets → Data → Analysis → Review → Decisions → Actions → Outcomes

The dimensions provide breadth.

The KPIs provide measurement.

The analysis provides understanding.

The review provides management attention.

The decisions and actions create change.

The outcomes provide evidence of whether the organisation is improving.

The ultimate principle

Corporate performance is not a single number.

It is the combined performance of the interconnected elements that enable an organisation to achieve its objectives.

A mature performance system therefore asks:

Are our customers receiving the required experience?

Do our people have the required capability and capacity?

Are our processes effective and efficient?

Is quality being maintained?

Are significant risks being controlled?

Are required obligations being met?

Are projects delivering their intended outcomes?

Is technology supporting reliable services?

Are suppliers performing as required?

And most importantly:

How do these dimensions interact to determine overall organisational performance?

The strongest corporate performance systems answer these questions together.

They do not merely measure departments.

They measure the organisation as an interconnected system.

That is the foundation of genuinely integrated corporate performance management.

7. Data, Analytics and Performance Technology

Performance measurement depends on information.

If the underlying data is inaccurate, incomplete, inconsistent or unavailable, even the most sophisticated performance framework can produce misleading results.

Data therefore sits at the foundation of corporate performance management.

Technology provides the infrastructure for collecting, storing, integrating, analysing and presenting that data.

Analytics transforms data into information and information into insight.

The objective is not simply to accumulate more data.

The objective is to create trusted performance information that helps people understand what is happening, why it is happening and what action may be appropriate.

A useful performance information chain is:

Data → Information → Analysis → Insight → Decision → Action → Outcome

Each stage depends on the quality of the stage before it.

7.1 Performance Data and Data Sources

Performance data is information collected or generated to measure organisational performance.

It may come from operational systems, applications, databases, surveys, documents, spreadsheets, sensors or manually maintained records.

The data required depends on the performance questions the organisation needs to answer.

Start with performance questions

Data collection should begin with purpose.

The organisation should first ask:

What do we need to know?
Why do we need to know it?
What decisions will the information support?
What measures are required?
What data is needed to calculate those measures?

This prevents unnecessary data collection.

Operational systems

Operational systems are often the primary source of performance data.

Examples include:

Service management systems
Customer service platforms
Human resources systems
Project management systems
Quality management systems
Risk systems
Workflow systems
Enterprise applications

These systems capture information as part of normal organisational activity.

Applications

Individual applications may contain important performance information.

For example, an application may record:

Transaction times
User activity
Errors
Availability
Process completion
Workflow stages

Application data can therefore provide detailed operational insight.

Databases

Databases store structured information that can be used for performance reporting and analysis.

A database may contain millions of records while still requiring careful interpretation.

Large quantities of data do not automatically create high-quality information.

Spreadsheets

Spreadsheets remain common sources of performance information.

They can be useful for:

Local analysis
Manual data collection
Temporary reporting
Small-scale performance tracking
Data preparation

However, uncontrolled spreadsheets can create significant risks.

Examples include:

Different versions
Manual errors
Inconsistent definitions
Broken formulas
Missing data
Limited auditability

Structured data

Structured data is information organised according to a defined format.

Examples include:

Tables
Databases
Transaction records
KPI values
Dates
Codes
Categories

Structured data is generally easier to analyse automatically.

Unstructured data

Unstructured data does not follow a rigid tabular structure.

Examples include:

Emails
Documents
Text responses
Customer comments
Interview notes
Reports
Images

Unstructured information can contain valuable performance insight.

Modern analytical technologies can increasingly extract useful patterns from such information.

Qualitative data

Not all performance information is numerical.

Qualitative information includes:

Customer comments
Employee feedback
Interview findings
Audit observations
Review notes
Expert assessments

Qualitative evidence can explain why a numerical result changed.

Data collection

Data collection methods may include:

Automated system capture
Surveys
Manual entry
Sensors
Forms
Interviews
Audits
Inspections
Operational logs

The method should be appropriate to the purpose.

Data frequency

Data may be collected:

Continuously
In real time
Daily
Weekly
Monthly
Quarterly
Annually

The appropriate frequency depends on how quickly the performance condition changes.

There is little value in collecting information every minute if the underlying performance question only requires monthly analysis.

Data lineage

Data lineage describes where data comes from and how it changes as it moves through systems.

For example:

Source System → Integration → Transformation → Calculation → KPI → Dashboard

Understanding this chain helps organisations investigate discrepancies and validate performance information.

Data ownership

Every important data set should have appropriate ownership.

The owner should understand:

What the data represents
Where it comes from
How it is maintained
What quality standards apply
Who can access it
How it is used

Data ownership is a critical component of performance governance.

7.2 Data Quality and Data Governance

Good performance measurement requires trustworthy data.

Data quality describes how suitable data is for its intended purpose.

A data set can contain thousands of records and still be unsuitable for decision-making.

Accuracy

Accuracy means that the data correctly represents the thing it is intended to represent.

For example, if a service request was actually resolved after 12 hours, a recorded resolution time of 6 hours would be inaccurate.

Completeness

Completeness concerns whether required information is present.

Missing values can distort performance calculations.

For example, if many service requests have no recorded completion time, an average resolution-time KPI may be misleading.

Consistency

Consistency means that data follows compatible definitions and formats.

For example, if one team records a closed case as "complete" while another uses "resolved" to represent the same condition, reporting may become inconsistent.

Timeliness

Timeliness concerns whether data is available when required.

Information that arrives too late may have limited value for operational decision-making.

Validity

Validity means that data conforms to defined rules.

For example, a percentage should normally fall within an appropriate range.

An invalid value may indicate an error in capture or transformation.

Uniqueness

Uniqueness means that records are not unintentionally duplicated.

Duplicate records can distort counts and performance calculations.

Data integrity

Data integrity refers to the reliability and consistency of data throughout its lifecycle.

Data should remain accurate and appropriately controlled as it is created, stored, transferred and transformed.

Data governance

Data governance is the framework of policies, responsibilities, processes and controls used to manage data.

It establishes how data should be:

Defined
Owned
Created
Maintained
Accessed
Protected
Used
Changed
Retained

Data definitions

A major source of performance reporting problems is inconsistent terminology.

For example, different teams may define:

Customer
Incident
Resolution
Active case
Completed request
Available service

differently.

The organisation therefore needs agreed definitions for important data elements and KPIs.

Data standards

Data standards establish common rules.

They may define:

Naming conventions
Data formats
Codes
Categories
Required fields
Validation rules
Calculation methods

Standards improve consistency.

Data controls

Data controls help prevent or identify errors.

Examples include:

Validation rules
Mandatory fields
Duplicate detection
Access controls
Approval workflows
Reconciliation
Data quality checks
Exception reporting

Controls should be proportionate to the importance of the data.

Data quality monitoring

Data quality itself can be measured.

Possible measures include:

Percentage of complete records
Duplicate rate
Invalid record rate
Timeliness
Error rate
Missing-field rate

This creates an important principle:

The organisation should measure the quality of the data used to measure performance.

Data governance and accountability

Data governance should clearly identify:

Data owners
Data stewards
System owners
KPI owners
Reporting owners
Access responsibilities

Without clear accountability, data problems can remain unresolved.

7.3 Data Integration and Information Architecture

Organisations rarely store all performance information in one system.

Different functions often operate different applications.

Data integration connects these sources so that performance information can be analysed consistently.

Data integration

Data integration is the process of combining information from multiple sources so that it can be used together.

For example:

Customer System + Service Management System + Workforce System + Project System

may collectively provide a more complete view of organisational performance.

Why integration matters

Without integration, organisations may create isolated reporting environments.

One team may know what customers are experiencing.

Another may know what operational processes are doing.

Another may know how technology is performing.

Another may know about workforce capacity.

Integration allows these perspectives to be examined together.

Data warehouse

A data warehouse is a structured repository designed to support reporting and analysis.

It typically brings together data from multiple operational systems in a form optimised for analytical use.

Data lake

A data lake is a repository that can store large volumes of data in different formats.

It may contain structured, semi-structured and unstructured information.

Data lakes can support advanced analytics but require appropriate governance.

Master data

Master data refers to important shared information used consistently across systems.

Examples may include:

Customer
Employee
Service
Location
Organisation
Supplier
Product or service category

Inconsistent master data can make integrated performance reporting difficult.

Data flows

A data flow describes how information moves from one system or process to another.

Understanding data flows helps identify:

Source systems
Transformations
Dependencies
Interfaces
Calculation points
Control points

Information architecture

Information architecture describes how information is organised, structured and connected so that it can support organisational needs.

A performance information architecture should connect:

Business Questions → Data Requirements → Data Sources → Integration → Storage → Transformation → Analytics → Reporting

Common integration problems

Data integration can create challenges such as:

Different definitions
Different formats
Missing identifiers
Duplicate records
Conflicting values
Different refresh frequencies
Legacy systems
Manual processes

These issues need to be addressed before integrated performance information can be trusted.

Data reconciliation

Reconciliation is the process of comparing information from different sources to identify differences.

For example, two systems may report different numbers of completed service requests.

Reconciliation helps determine why.

Possible causes include:

Different definitions
Timing differences
Missing records
Duplicate records
Transformation errors

Performance information architecture

A mature environment may use an architecture such as:

Operational Systems → Integration Layer → Data Platform → Semantic Model → Analytics → Dashboards → Performance Reviews

A semantic model provides a consistent business interpretation of the data.

It can define how measures, dimensions and relationships should be understood.

Avoiding the "single database" misconception

A single source of truth does not necessarily require a single physical system.

An organisation may have many systems while still maintaining a consistent definition of important information.

The key requirement is controlled interpretation.

7.4 Business Intelligence and Analytics

Business Intelligence transforms data into information that people can use.

Analytics goes further by examining patterns, relationships and potential explanations.

BI reporting

BI platforms can provide:

Dashboards
Scorecards
KPI reports
Trend analysis
Filters
Drill-down
Automated refresh
Exception reporting

This reduces dependence on manually prepared reports.

Descriptive analytics

Descriptive analytics answers:

What happened?

Examples include:

KPI results
Historical trends
Volume analysis
Performance distributions
Status summaries

Diagnostic analytics

Diagnostic analytics answers:

Why did it happen?

It may use:

Segmentation
Correlation
Root-cause analysis
Variance analysis
Process analysis

Predictive analytics

Predictive analytics answers:

What may happen next?

It can use historical patterns, current information and analytical models.

Examples include:

Forecasting service demand
Predicting workload
Identifying potential performance deterioration
Forecasting capacity requirements

Prescriptive analytics

Prescriptive analytics asks:

What could we do?

It may evaluate potential actions against defined conditions and objectives.

This can support decision-making but should not be treated as a substitute for appropriate human judgement.

Self-service analytics

Self-service analytics allows users to explore approved information independently.

Benefits may include:

Faster analysis
Greater flexibility
Reduced reporting dependency
More local insight

However, governance remains important.

Users should work from approved definitions and trusted data.

Analytical models

An analytical model describes relationships within data.

Models may be used for:

Forecasting
Classification
Anomaly detection
Segmentation
Trend analysis

Models should be validated before being used for important decisions.

Anomaly detection

Anomaly detection identifies observations that differ significantly from expected patterns.

Examples include:

Sudden increase in incidents
Unexpected reduction in service volume
Unusual processing times
Unusual access activity
Unexpected quality deterioration

An anomaly is a signal for investigation.

It is not automatically evidence of a problem.

Performance forecasting

Analytics can support forecasting by identifying patterns in historical and current information.

Forecasts should include appropriate assumptions and limitations.

Insight generation

The objective of analytics is not to produce more charts.

The objective is to generate useful insight.

A useful insight should help answer:

What changed?
Why?
What does it mean?
What could happen next?
What should be investigated?
What action might be appropriate?

Analytical maturity

Analytical capability can develop through stages:

Reporting → Descriptive Analytics → Diagnostic Analytics → Predictive Analytics → Prescriptive Analytics

Organisations should not rush to advanced analytics before establishing reliable basic reporting.

Strong foundations matter.

7.5 Automation and Artificial Intelligence

Automation and Artificial Intelligence can significantly increase the speed and scale of performance management.

They can reduce repetitive manual work and help identify patterns that may otherwise be difficult to detect.

Automated data collection

Data can be collected automatically from operational systems.

This reduces manual entry and can improve timeliness.

However, automated collection does not guarantee data quality.

Incorrect source data can still be collected automatically.

Automated calculations

KPIs can be calculated automatically according to approved definitions.

This reduces manual calculation errors.

The calculation logic should still be documented and controlled.

Automated reporting

Reports can be generated and distributed automatically according to defined schedules.

Automation can support:

Daily reporting
Weekly reporting
Monthly reporting
Exception reporting
Alerting

Anomaly detection

AI and analytical tools can identify unusual patterns.

For example:

Unexpected changes in service volume
Unusual processing times
Sudden quality deterioration
Unusual system behaviour

The tool identifies a pattern.

People should determine whether the pattern is meaningful.

AI-assisted data quality

AI can support the identification of:

Missing information
Duplicates
Inconsistent classifications
Unusual records
Potential errors

These capabilities can assist data-quality teams but should not remove appropriate controls.

Automated commentary

AI can assist with performance commentary by summarising:

Significant KPI movements
Major trends
Exceptions
Changes from previous periods

However, generated commentary should be checked against the underlying evidence.

AI-assisted analysis

AI can help users explore questions such as:

Which KPIs deteriorated most?
Which areas changed significantly?
Which services show recurring problems?
Which patterns require investigation?

AI can therefore make analytical access easier for non-specialist users.

Automation of repetitive work

Automation is particularly valuable when a task is:

Repetitive
Rule-based
High volume
Time-consuming
Clearly defined

Examples include:

Data extraction
Data transformation
Report generation
Notifications
Data validation
Routine reconciliation

Human oversight

Automation should not remove accountability.

People should remain responsible for important performance decisions.

A useful principle is:

Automate the repeatable work. Govern the important decisions.

7.6 Performance Management Technology

Performance management technology brings together data, measurement, reporting, analytics and management processes.

The appropriate solution depends on organisational maturity and requirements.

Spreadsheets

Spreadsheets can provide a practical starting point.

They are particularly useful in greenfield environments where the organisation is still defining:

KPIs
Definitions
Reporting structures
Data requirements

However, they should not become permanent substitutes for appropriate systems where scale and complexity require stronger controls.

BI platforms

BI platforms can provide:

Data integration
Dashboards
Interactive reports
Analytics
Scheduled refresh
Drill-down
User access controls

They are often central to modern performance environments.

Enterprise Performance Management

Enterprise Performance Management, or EPM, refers broadly to technology and processes used to manage organisational performance.

EPM capabilities may include:

Performance frameworks
Objectives
KPIs
Targets
Scorecards
Dashboards
Reporting
Reviews
Action tracking

The precise functionality varies between platforms.

Performance management platforms

Dedicated performance management platforms may integrate:

KPI management
Objectives
Reviews
Dashboards
Actions
Governance
Workflow

This can reduce fragmentation.

Reporting systems

Reporting systems provide controlled production and distribution of performance information.

They can support:

Standard reports
Scheduled reports
Executive packs
Operational reports
Exception reports

Dashboard technology

Dashboard technology enables visual presentation of performance information.

Important capabilities may include:

Filtering
Drill-down
Role-based views
Refresh
Alerts
Trend analysis

Technology architecture

A performance technology architecture should consider:

Data sources
Integration
Storage
Analytics
Reporting
Security
Access
Governance
Automation
User experience

Technology should be designed as part of the broader performance operating model.

Technology selection

Technology selection should begin with requirements.

A useful sequence is:

Performance Purpose → Business Requirements → Data Requirements → Reporting Requirements → User Requirements → Technical Requirements → Technology Selection

This prevents the organisation from selecting a tool simply because it has attractive features.

Greenfield performance environments

A greenfield environment is a situation in which a new capability is being designed without needing to preserve an extensive existing performance architecture.

Greenfield environments provide an opportunity to establish:

Clear definitions
Good governance
Clean data structures
Consistent KPI design
Appropriate technology

The risk is overengineering.

A new environment should remain proportionate to actual requirements.

Mature performance environments

A mature environment may contain:

Multiple systems
Historical data
Established KPIs
Legacy reports
Existing dashboards
Complex integrations

The challenge is often rationalisation rather than simple implementation.

The organisation may need to remove duplication and simplify existing reporting.

Technology adoption

Technology is only useful if people actually use it.

Adoption depends on:

Usability
Training
Clear purpose
Trust
Leadership support
Data quality
Appropriate access
Integration into management routines

A technically sophisticated platform can fail if users do not trust the information.

7.7 Technology, Data and Information Risks

Technology and data introduce risks that can directly affect corporate performance.

A performance framework should therefore measure and manage these risks.

Data security

Performance information may contain sensitive organisational or personal information.

Security controls should protect information from:

Unauthorised access
Unauthorised modification
Loss
Disclosure
Destruction

Access control

Access control determines who can view, create, modify or administer information.

Access should be appropriate to role and responsibility.

Data integrity risk

Data integrity can be damaged through:

Manual errors
System errors
Poor integration
Uncontrolled changes
Duplicate records
Incorrect transformations

Integrity controls should therefore be incorporated into the data architecture.

System reliability

Performance reporting depends on technology being available and reliable.

If critical reporting systems frequently fail, performance information may become unavailable when management needs it.

Technology dependency

Organisations can become dependent on particular systems, suppliers or technologies.

Dependency should be understood and monitored.

Legacy systems

Legacy systems may create:

Integration difficulties
Data quality problems
Limited automation
Obsolete interfaces
Unsupported technology

Legacy constraints should be recognised when designing performance architecture.

Data quality risk

Poor data quality can produce incorrect performance conclusions.

For example:

Poor source data → Incorrect KPI → Incorrect analysis → Incorrect decision

This chain demonstrates why data quality is a performance risk rather than merely a technical issue.

Information risk

Information risk occurs when decision-makers receive information that is:

Incorrect
Incomplete
Late
Misleading
Poorly defined
Taken out of context

Information risk can be particularly serious because users may trust the appearance of an official report.

Model risk

Analytical models can also create risk.

A model may produce unreliable results because of:

Poor data
Incorrect assumptions
Inappropriate methodology
Changing conditions
Model limitations

Models should therefore be appropriately validated and monitored.

Automation risk

Automation can increase speed while also increasing the scale of errors.

If an incorrect rule is automated, the same mistake may be repeated across thousands of records.

Automation should therefore include:

Testing
Validation
Monitoring
Exception handling
Appropriate human oversight

Dashboard risk

Dashboards can mislead users through:

Poor definitions
Incorrect calculations
Outdated data
Excessive simplification
Misleading visualisation
Missing context

A visually impressive dashboard can therefore still be a poor management tool.

Information overload

Technology makes it easy to display more information.

That does not mean users need more information.

Too much information can reduce attention and obscure important signals.

The objective should remain:

Relevant information at the right level of detail at the right time.

The performance technology chain

A complete performance technology environment can be represented as:

Source Data → Data Quality → Integration → Information Architecture → Analytics → KPIs → Dashboards → Reports → Reviews → Decisions → Actions

Weakness at any stage can affect the final outcome.

The ultimate principle

Technology should make performance management more reliable, accessible and actionable.

It should not make performance management more complicated simply because technology makes complexity possible.

The strongest performance technology environments combine:

Trusted Data + Clear Definitions + Strong Governance + Appropriate Analytics + Effective Technology + Human Oversight

The objective is not to create the largest data platform.

It is to create a trusted flow of performance information that helps the organisation understand reality, respond intelligently and improve continuously.

8. Governance, Reviews and Continuous Improvement

Performance measurement creates information.

Governance determines how that information is owned, reviewed and used.

Without effective governance, performance information can become fragmented, inconsistent or disconnected from management action.

A strong performance governance system establishes clear responsibilities, decision rights, review forums and escalation mechanisms.

It also creates a disciplined connection between measurement and improvement.

The complete cycle is:

Measure → Analyse → Review → Decide → Act → Improve → Measure Again

This chapter explains how organisations can establish the governance structures and management practices required to make that cycle work.

8.1 Performance Governance and Organisational Roles

Performance governance is the framework through which an organisation establishes accountability, decision rights, oversight and control over its performance management system.

Governance answers fundamental questions:

Who owns performance?
Who owns the KPI?
Who owns the data?
Who reviews the results?
Who makes decisions?
Who can change a KPI?
Who escalates problems?
Who ensures that actions are completed?

Without clear answers, performance management can become everyone's responsibility and therefore nobody's responsibility.

Board and senior leadership

At the highest level, organisational leadership is responsible for understanding whether the organisation is achieving its objectives.

Leadership should provide:

Direction
Priorities
Accountability
Oversight
Decision-making
Support for improvement

Senior leaders should focus on significant performance conditions rather than attempting to manage every operational measure personally.

Executive management

Executive management translates organisational priorities into measurable objectives and ensures that performance is reviewed regularly.

Responsibilities may include:

Approving objectives
Reviewing strategic KPIs
Challenging performance
Making decisions
Allocating organisational attention
Escalating significant issues
Monitoring improvement

Managers

Managers are responsible for managing performance within their areas of accountability.

They should understand:

What their objectives are
Which KPIs they own
What the results mean
Which factors influence performance
What actions are required
When escalation is appropriate

KPI owners

The KPI owner is accountable for the relevance and management of a particular KPI.

The owner should ensure that:

The KPI remains meaningful
The definition is understood
Performance is reviewed
Significant variances are investigated
Actions are initiated where required

Data owners

The data owner is responsible for the quality and management of the underlying data.

This includes understanding:

Data definitions
Data sources
Data quality
Access
Controls
Retention
Appropriate use

Reporting owners

The reporting owner is responsible for producing and distributing performance information according to agreed standards.

This may include:

Data collection
Validation
Report production
Dashboard refresh
Distribution
Version control

Analysts

Performance analysts help convert data into insight.

Their role may include:

Trend analysis
Variance analysis
Benchmarking
Root-cause analysis
Forecasting
Data interpretation
Performance commentary

Analysts should challenge assumptions while remaining evidence-based.

Performance management function

Larger organisations may establish a dedicated performance management function.

Its responsibilities may include:

Performance framework design
KPI governance
Reporting standards
Dashboard management
Performance reviews
Data quality coordination
Methodology
Maturity assessment
Continuous improvement

Decision rights

Governance should define who can make decisions.

For example:

KPI owner: May propose KPI changes

Performance governance forum: May approve KPI definitions

Executive leadership: May approve strategic changes

The exact arrangement depends on organisational structure.

Governance principles

Effective performance governance should provide:

Clarity: Everyone understands their responsibilities

Accountability: Ownership is explicit

Transparency: Performance information is visible to appropriate users

Consistency: Definitions and processes are controlled

Evidence: Decisions are based on reliable information

Timeliness: Information reaches decision-makers when needed

Action: Performance discussions lead to appropriate responses

8.2 Performance Review Forums and Processes

Performance reviews create a structured opportunity to examine results and make decisions.

A performance review is not simply a meeting where people read numbers aloud.

It is a management process.

Executive performance reviews

Executive reviews focus on strategic and organisational performance.

Typical subjects include:

Strategic objectives
Major KPI movements
Significant risks
Major initiatives
Customer performance
Workforce capability
Technology performance
Important decisions

The discussion should concentrate on matters requiring leadership attention.

Business performance reviews

Business or functional reviews examine performance within a particular organisational area.

They may cover:

Objectives
KPIs
Process performance
Customer experience
Quality
Workforce
Technology
Risks
Improvement actions

Operational reviews

Operational reviews focus on immediate and near-term performance.

They may examine:

Workload
Backlogs
Incidents
Service levels
Quality
Capacity
Bottlenecks
Immediate corrective actions

Regular review cycles

Organisations may establish different review frequencies.

For example:

Frequent operational reviews
Monthly management reviews
Quarterly strategic reviews
Annual strategic assessments

The frequency should reflect how quickly the performance environment changes.

Performance review agenda

A structured agenda may include:

1. Previous actions

What was agreed previously?

2. Overall performance

What does the current performance position look like?

3. Significant exceptions

Which results require attention?

4. Trends

What direction is performance moving?

5. Root causes

Why are significant changes occurring?

6. Risks

What could affect future performance?

7. Forecast

What may happen next?

8. Decisions

What decisions are required?

9. Actions

What must be done?

10. Accountability

Who owns each action and when is it due?

Review discipline

A review meeting should not become a general discussion without conclusions.

Every significant issue should ideally lead to one of three outcomes:

No action required
Further investigation required
Action or decision required

This keeps the review focused.

Evidence-based review

Performance discussions should distinguish between:

Facts
Analysis
Assumptions
Opinions
Predictions

For example:

Fact: Resolution performance declined from 94% to 88%

Analysis: The decline is concentrated in two service categories

Hypothesis: Increased complexity may be contributing to the decline

Action: Investigate case complexity and process capacity

This structure prevents assumptions from being presented as established facts.

Review outputs

Every formal performance review should produce a clear record of:

Decisions
Actions
Owners
Due dates
Escalations
Follow-up requirements

The value of the meeting should therefore continue after the meeting ends.

8.3 Accountability, Escalation and Decision-Making

Performance management requires accountability.

Accountability means that a person or group is responsible for explaining performance and taking appropriate action within their area of responsibility.

Accountability should be clear but reasonable.

Accountability versus blame

Accountability means:

"Who is responsible for understanding and responding to this?"

Blame means:

"Who should be held responsible for what went wrong?"

These are not the same question.

Effective performance cultures emphasise accountability while investigating causes fairly.

Ownership

Ownership should exist at multiple levels.

For example:

Executive owner
Business owner
KPI owner
Process owner
Data owner
Action owner

Different roles may be held by different people.

Escalation

Escalation is the process of moving an issue to a higher level of authority when it cannot be resolved at the current level.

Escalation may be required when:

A threshold is breached
A risk exceeds tolerance
An issue remains unresolved
A decision requires greater authority
Multiple teams cannot agree
A dependency threatens a critical outcome

Escalation criteria

Escalation should be defined rather than left entirely to personal judgement.

Criteria may include:

Severity
Duration
Customer impact
Organisational impact
Risk
Regulatory significance
Strategic importance

Decision rights

A decision right defines who has authority to make a particular decision.

Clear decision rights prevent:

Delays
Confusion
Duplicate decisions
Unnecessary escalation

Decision logs

A decision log records important decisions and their rationale.

It may include:

Decision
Date
Decision owner
Evidence considered
Rationale
Actions
Review date

Decision logs can improve transparency and organisational learning.

Performance failure

A performance failure occurs when expected performance is not achieved.

The response should consider:

Severity
Cause
Duration
Impact
Risk
Recurrence
Corrective action

Not every missed target represents a serious organisational failure.

The context matters.

Persistent underperformance

Repeated underperformance requires deeper investigation.

Useful questions include:

Has the problem been recurring?
Has the root cause been identified?
Were previous actions effective?
Is the target realistic?
Is the process capable?
Is ownership clear?
Is the underlying data reliable?

Escalation should be timely

Waiting until a problem becomes severe can reduce the available options.

Early escalation can allow management to intervene while the issue remains manageable.

8.4 Corrective Action, Preventive Action and Root-Cause Improvement

Performance management should result in action when action is required.

Corrective action

Corrective action addresses an existing problem.

For example:

A service process repeatedly fails to meet its required resolution time.

Corrective action may involve addressing the immediate cause and restoring expected performance.

Preventive action

Preventive action aims to reduce the likelihood of a problem occurring.

For example:

An organisation identifies a weakness in a process before a major failure occurs and strengthens the relevant control.

Containment

Containment is an immediate response designed to limit the impact of an existing problem.

Containment may be necessary before the underlying root cause can be addressed.

For example:

A technology problem may require an immediate workaround while a permanent solution is investigated.

Root-cause analysis

Corrective action should ideally address the underlying cause rather than only the visible symptom.

Useful techniques include:

Five Whys
Fishbone analysis
Pareto analysis
Process analysis
Fault analysis
Data analysis

Action logs

An action log records agreed improvement or corrective actions.

It should normally include:

Action
Owner
Priority
Due date
Status
Evidence
Outcome
Closure date

Action ageing

Actions should be monitored for how long they remain open.

Long-running actions may indicate:

Insufficient ownership
Poor prioritisation
Dependency problems
Lack of resources
Inadequate decision-making

Action closure

An action should not automatically be considered complete simply because someone says it is finished.

Where appropriate, closure should require evidence.

For example:

Action: Update service process

Evidence: New process implemented and approved

Outcome: Service performance improved and remained stable

This distinguishes activity from effectiveness.

Corrective action effectiveness

The organisation should ask:

Did the action solve the problem?

Possible measures include:

KPI improvement
Reduced recurrence
Reduced defects
Improved service quality
Reduced customer complaints

Recurring problems

Repeated problems are particularly important.

If the same problem occurs repeatedly, previous interventions may have addressed symptoms rather than the underlying cause.

Recurring problems should therefore trigger deeper analysis.

Improvement action hierarchy

A useful sequence is:

Contain → Correct → Identify Root Cause → Prevent Recurrence → Verify Effectiveness

This creates a disciplined approach to improvement.

8.5 Continuous Improvement and Benefits Realisation

Continuous improvement is the ongoing effort to improve processes, services, capabilities and organisational performance.

It does not necessarily mean constant major transformation.

Many improvements are small.

The important principle is sustained learning and improvement.

Improvement cycle

A practical improvement cycle is:

Identify → Analyse → Design → Implement → Measure → Learn → Refine

This cycle can be repeated.

Identifying improvement opportunities

Improvement opportunities may come from:

KPI trends
Customer feedback
Employee feedback
Audit findings
Risk analysis
Root-cause analysis
Benchmarking
Process reviews
Technology analysis

Improvement initiatives

An improvement initiative should have:

Clear objective
Defined scope
Owner
Measures
Target
Actions
Timeline
Expected outcome

Prioritising improvements

Not every improvement can be implemented immediately.

Prioritisation can consider:

Performance impact
Customer impact
Risk
Urgency
Feasibility
Dependencies
Organisational capability

Benefits

A benefit is a measurable positive change resulting from an initiative.

Examples include:

Improved customer experience
Reduced process time
Improved quality
Increased reliability
Improved employee capability
Reduced operational risk

Benefits realisation

Benefits realisation is the process of determining whether expected benefits actually occurred.

A project can be completed successfully without realising its intended benefits.

For example:

Project outcome: New service platform implemented

Expected benefit: Improved service resolution

The implementation itself is not the benefit.

The benefit is the improvement in service performance that results from the implementation.

Benefits tracking

Benefits should be tracked using defined measures.

A benefits tracker may include:

Benefit
Owner
Baseline
Target
Current result
Expected date
Actual result
Status
Evidence

Benefits ownership

Benefits often continue beyond project closure.

Therefore, benefit ownership should normally transfer to the operational or business area responsible for realising the outcome.

Improvement verification

An improvement should be verified after implementation.

The organisation should compare:

Before → Intervention → After

This helps determine whether the intervention produced the intended change.

Continuous improvement versus continuous activity

Continuous improvement should not become continuous change for its own sake.

Change should have a purpose.

A mature organisation asks:

What problem are we solving?
What evidence supports the need?
What improvement is expected?
How will we measure it?
How will we know whether it worked?

8.6 Performance Culture and Behaviour

Performance systems influence organisational behaviour.

People pay attention to what leaders measure, discuss and reward.

Performance measurement should therefore be designed with behavioural consequences in mind.

Transparency

Transparency means making appropriate performance information visible to the people who need it.

Transparency can support:

Trust
Accountability
Learning
Early identification of problems

Accountability culture

A strong accountability culture encourages people to understand their responsibilities and respond to performance issues.

It does not require a culture of fear.

Learning culture

A learning culture treats performance information as a source of organisational learning.

When something goes wrong, the organisation asks:

What happened?
What can we learn?
What should change?
How can recurrence be prevented?

Blame culture

A blame culture can damage performance measurement.

If people fear punishment for reporting poor performance, they may:

Hide problems
Delay escalation
Alter data
Avoid ownership
Focus on appearances

This can make performance information less reliable.

KPI gaming

KPI gaming occurs when people optimise the measure rather than the underlying outcome.

Examples include:

Closing cases prematurely
Reclassifying problems
Avoiding difficult work
Prioritising easy cases
Manipulating reporting periods

KPI gaming is often a sign that the measurement system has created unintended incentives.

Balanced measurement

Balanced measurement can reduce gaming.

For example, instead of measuring only speed, an organisation may combine:

Speed + Quality + Customer Experience + Resolution

This makes it more difficult to improve one measure by damaging another.

Leadership behaviour

Leaders influence performance culture through what they ask about.

If leaders ask only:

"Why is this KPI red?"

people may focus on avoiding red status.

If leaders ask:

"What is happening, why is it happening and what are we learning?"

the conversation becomes more constructive.

Incentives

Measurement can influence incentives.

Incentives should be designed carefully because poorly designed incentives may encourage undesirable behaviour.

Where performance measures influence rewards or recognition, organisations should ensure that the measures represent genuine performance rather than easily manipulated activity.

Psychological safety

People should be able to raise genuine performance concerns without automatically being treated as the cause of the problem.

This supports early escalation and better information.

Responsible measurement

Responsible performance measurement considers:

Purpose
Fairness
Context
Data quality
Human impact
Unintended consequences

The measurement system should help people improve rather than simply monitor them.

8.7 Turning Performance Information into Organisational Results

The ultimate purpose of performance management is to create better organisational results.

The measurement system should therefore form a closed loop.

The performance-to-action cycle

A practical model is:

Measurement → Analysis → Review → Decision → Action → Improvement → Benefits → Outcomes

Each stage adds value.

Measurement

Measurement establishes what happened.

Analysis

Analysis determines what the information may mean.

Review

Review brings the information into a management forum.

Decision

Decision determines what should happen.

Action

Action implements the decision.

Improvement

Improvement changes the process, service, capability or operating environment.

Benefits

Benefits identify whether the improvement produced the intended positive change.

Outcomes

Outcomes demonstrate whether the organisation is achieving its broader objectives.

The closed loop

Once the outcome is observed, it becomes part of the next measurement cycle.

The complete loop becomes:

Measure → Analyse → Review → Decide → Act → Improve → Measure Again

This is the foundation of effective performance management.

Connecting performance information to strategy

The strongest systems maintain the connection:

Strategy → Objectives → KPIs → Data → Analysis → Decisions → Actions → Outcomes

If this connection breaks, performance management can become a reporting exercise.

Management action is the critical link

The most important transition is:

Information → Decision

An organisation can have excellent dashboards and still perform poorly if nobody acts on the information.

Action tracking

Actions should be tracked until completion.

However, completion should not be the final test.

The organisation should also ask:

Did the action produce the intended result?

Benefits tracking

Benefits provide evidence that actions and initiatives produced meaningful change.

This creates accountability for outcomes rather than simply activities.

Organisational learning

Performance management should also create organisational memory.

The organisation should retain knowledge about:

What happened
Why it happened
What was done
What worked
What did not work
What should be repeated
What should be avoided

This prevents the organisation from repeatedly solving the same problem.

Performance governance maturity

As performance governance matures, organisations generally move from:

Reporting → Reviewing → Managing → Improving → Learning

The organisation gradually becomes more capable of using performance information proactively.

Greenfield governance

In a greenfield environment, governance should be established early.

Important foundations include:

Clear ownership
KPI definitions
Review forums
Decision rights
Escalation rules
Action tracking
Data governance

Starting with clear governance can prevent significant future complexity.

Mature governance

In a mature environment, the challenge may be simplification.

The organisation may need to:

Remove duplicate forums
Rationalise KPIs
Simplify reports
Clarify overlapping responsibilities
Improve decision-making
Retire obsolete measures

Maturity does not mean adding more governance.

It means making governance effective and proportionate.

The complete governance model

A practical model is:

Purpose → Objectives → Measures → Data → Analysis → Review → Decision Rights → Actions → Accountability → Benefits → Learning

Each element supports the next.

The ultimate principle

Performance governance should make it clear:

Who knows?

Who decides?

Who acts?

Who is accountable?

Who verifies the result?

When these questions have clear answers, performance information can become a powerful management capability.

The ultimate objective is not to create more meetings, reports or governance structures.

It is to create an organisation that can:

Measure accurately → Understand intelligently → Decide confidently → Act effectively → Learn continuously

That is the essence of performance governance and continuous improvement.

9. Performance Maturity, Operating Model and Complete Toolkit

Organisations differ significantly in their ability to manage performance.

Some have little formal measurement.

Others have large numbers of KPIs but struggle to use them effectively.

More mature organisations connect strategy, objectives, measures, data, analysis, governance and action into a coherent performance management system.

Performance maturity describes the level of capability an organisation has developed in managing performance.

Maturity is not simply about having more technology or more KPIs.

A mature organisation can have fewer measures than an immature organisation while producing better performance insight.

The objective of maturity assessment is therefore not to create a ranking.

It is to understand the current state, identify gaps and determine what should improve.

9.1 Performance Maturity Model

A performance maturity model provides a structured way to describe the development of performance management capability.

A useful six-level model is:

Level	Maturity	Typical Characteristics
Level 0	Non-Existent	Little or no formal performance measurement
Level 1	Initial	Basic measures exist but are inconsistent and largely reactive
Level 2	Developing	Defined KPIs and reporting begin to emerge
Level 3	Defined	A structured performance framework and governance model exist
Level 4	Managed	Performance is actively analysed, reviewed and managed
Level 5	Optimised	Performance management is integrated, predictive and continuously improved

These levels provide a reference model.

They should not be treated as rigid categories.

An organisation may have Level 4 capability in one dimension and Level 2 capability in another.

Level 0: Non-Existent

At Level 0, there is little or no formal performance management capability.

Performance may be discussed informally.

Information may exist within individual teams.

There may be no consistent definitions, KPI framework or formal review process.

Typical characteristics include:

No agreed performance framework
Limited performance data
Informal reporting
Unclear ownership
Reactive management
Minimal governance

The first priority is usually to establish basic visibility.

Level 1: Initial

At Level 1, some performance measures exist.

Different teams may create their own reports.

Measures are often activity-focused.

Definitions may vary.

Performance management is usually reactive.

Typical characteristics include:

Local measures
Basic reports
Inconsistent definitions
Limited ownership
Manual reporting
Reactive problem solving
Limited trend analysis

The organisation begins to recognise the need for structured performance management.

Level 2: Developing

At Level 2, the organisation begins establishing a more consistent measurement system.

KPIs are defined.

Targets are introduced.

Reporting becomes more regular.

Performance ownership becomes clearer.

Typical characteristics include:

Defined KPIs
Basic KPI dictionary
Regular reporting
Targets
Performance dashboards
Initial governance
Basic variance analysis

However, integration between strategy, data, analysis and action may still be incomplete.

Level 3: Defined

At Level 3, performance management becomes a recognised organisational capability.

The organisation has a structured framework connecting strategy, objectives, measures and management action.

Typical characteristics include:

Formal performance framework
Clear objectives
Defined KPI architecture
KPI governance
Consistent reporting
Performance review forums
Data ownership
Root-cause analysis
Structured action tracking

Performance management is no longer simply a reporting activity.

Level 4: Managed

At Level 4, performance information is actively used to manage the organisation.

Analysis becomes more sophisticated.

Trends, benchmarks, forecasts and risks are considered together.

Typical characteristics include:

Integrated performance analysis
Strong governance
Reliable data
Regular performance reviews
Forecasting
Benchmarking
Early-warning indicators
Benefits tracking
Continuous improvement

Management decisions are increasingly evidence-based.

Level 5: Optimised

At Level 5, performance management is deeply integrated into organisational management.

The organisation uses advanced analytics and automation appropriately.

Performance information is increasingly forward-looking.

The organisation learns from performance and continuously improves its measurement system.

Typical characteristics include:

Integrated performance ecosystem
Advanced analytics
Predictive indicators
Automated reporting
Strong data governance
Dynamic performance monitoring
Continuous KPI optimisation
Embedded performance culture
Organisational learning

Maturity is multidimensional

An organisation should not assume that it has one maturity level.

It may have:

Strong technology
Weak governance
Good KPIs
Poor data quality
Strong analysis
Weak action management

Maturity should therefore be assessed across multiple dimensions.

The purpose of maturity assessment

The purpose is not to obtain a label.

It is to answer:

Where are we now?

Where do we need to be?

What gaps exist?

Which gaps matter most?

What should we improve first?

9.2 Assessing Performance Maturity

A structured maturity assessment examines the organisation across multiple dimensions.

A useful model includes:

Strategy
Governance
Leadership
Processes
Performance measurement
Data
Reporting
Technology
Culture

Strategy maturity

Questions include:

Are strategic priorities clearly defined?
Are objectives measurable?
Are KPIs linked to objectives?
Is strategy translated into operational performance?

Governance maturity

Questions include:

Are performance roles defined?
Are decision rights clear?
Are KPI changes governed?
Are performance reviews structured?

Leadership maturity

Questions include:

Do leaders actively use performance information?
Do leaders ask meaningful questions?
Are performance issues addressed?
Is accountability clear?

Process maturity

Questions include:

Are important processes defined?
Are process measures established?
Are bottlenecks understood?
Is continuous improvement embedded?

Performance measurement maturity

Questions include:

Are KPIs clearly defined?
Are leading and lagging indicators balanced?
Are targets meaningful?
Are obsolete measures retired?

Data maturity

Questions include:

Is data accurate?
Is data complete?
Are definitions consistent?
Is data ownership established?
Is data lineage understood?

Reporting maturity

Questions include:

Are reports designed for decisions?
Are dashboards appropriate for their audiences?
Is reporting automated where appropriate?
Is reporting duplication controlled?

Technology maturity

Questions include:

Are performance systems integrated?
Are dashboards reliable?
Is analytical capability available?
Are technology dependencies understood?

Culture maturity

Questions include:

Do people trust performance information?
Are problems reported openly?
Is accountability constructive?
Is performance information used for learning?
Is KPI gaming discouraged?

Maturity scoring

An organisation may assign a maturity level to each dimension.

For example:

Dimension	Current Level
Strategy	3
Governance	2
Leadership	3
Processes	2
Performance Measurement	3
Data	2
Reporting	3
Technology	2
Culture	2

The numbers should be supported by evidence.

A maturity score without evidence provides little value.

Evidence-based assessment

Evidence may include:

Strategy documents
KPI dictionaries
Dashboards
Reports
Governance terms of reference
Review agendas
Action logs
Data quality assessments
Technology architecture
Interviews
Process documentation

Assessment workshops

Maturity assessments often benefit from structured workshops.

Different stakeholders can provide different perspectives.

For example:

Leadership
Performance teams
Analysts
Process owners
Technology teams
Data owners
Operational managers

This reduces dependence on one person's interpretation.

Current versus desired maturity

The assessment should distinguish between:

Current state

and

Desired state

The desired state should be appropriate to organisational needs.

Not every organisation needs Level 5 capability across every dimension.

The target should be proportionate.

9.3 Capability Assessment, Benchmarking and Gap Analysis

Maturity tells an organisation where it stands.

Capability assessment examines what the organisation can actually do.

Capability

A capability is the organisation's ability to perform a particular function consistently.

For example:

Performance Reporting Capability

may include:

Data collection
KPI calculation
Dashboard production
Commentary
Distribution
Review

Capability assessment

A capability assessment examines:

People
Process
Technology
Data
Governance
Skills
Controls

This provides a broader picture than simply assessing whether a process exists.

Current state

The current state describes how performance management operates today.

It should be based on evidence rather than assumptions.

Desired state

The desired state describes how the capability should operate in the future.

It should reflect:

Strategy
Organisational needs
Risk
Complexity
User requirements
Available capability

Gap analysis

Gap analysis identifies the difference between the current state and desired state.

For example:

Current: KPIs exist but definitions vary between teams

Desired: A controlled enterprise KPI dictionary exists

Gap: KPI standardisation and governance

Capability gaps

Common capability gaps include:

Lack of ownership
Weak KPI definitions
Poor data quality
Limited analytical skills
Fragmented technology
Weak governance
Inconsistent reporting
Poor action tracking

Benchmarking maturity

Benchmarking can help provide context.

However, organisations should avoid assuming that another organisation's maturity level is automatically appropriate.

The relevant question is:

What capability is required for our organisation?

Gap prioritisation

Not every gap should be addressed simultaneously.

Prioritisation can consider:

Strategic importance
Risk
Customer impact
Performance impact
Dependency
Effort
Organisational readiness

Improvement roadmap

A maturity assessment should lead to a roadmap.

A roadmap may define:

Immediate priorities → Near-term improvements → Medium-term capability development → Longer-term optimisation

Avoid transformation for transformation's sake

The purpose of a maturity programme is improvement.

The organisation should avoid implementing sophisticated processes or technology simply because they appear mature.

Capability should be designed around actual requirements.

9.4 Performance Management Operating Model

An operating model describes how an organisational capability is structured and operated.

A performance management operating model defines how people, processes, data, technology and governance work together.

People

People provide:

Leadership
Ownership
Analysis
Governance
Decision-making
Operational management

Roles should be clear.

Processes

Performance processes may include:

KPI definition
Data collection
Reporting
Analysis
Performance reviews
Action management
Benefits tracking
KPI review

Technology

Technology supports:

Data collection
Integration
Analysis
Dashboards
Reporting
Workflow
Automation

Data

Data provides the evidence required to understand performance.

Data governance should establish:

Definitions
Ownership
Quality
Access
Lineage

Governance

Governance provides:

Accountability
Decision rights
Standards
Review structures
Escalation
Control

Reporting

Reporting converts performance information into communication appropriate to different audiences.

Accountability

The operating model should establish who owns:

Objectives
KPIs
Data
Processes
Reports
Actions
Benefits

Decision-making

Performance information must reach people with authority to act.

This means the operating model should connect reporting with decision rights.

Organisational capability

The operating model should also consider skills.

Performance management may require capability in:

Business analysis
Data analysis
Visualisation
Performance management
Process improvement
Governance
Change management

Centralised model

A centralised performance function may own most performance activities.

Advantages can include:

Consistency
Standardisation
Central governance
Shared expertise

Potential limitations include:

Distance from operational teams
Slower local response
Risk of excessive central control

Federated model

A federated model distributes performance capability across functions while maintaining common standards.

This can provide:

Local expertise
Greater business understanding
Shared standards
Distributed ownership

Hybrid model

A hybrid model combines central standards with local capability.

For many organisations, this can provide a practical balance.

The appropriate model depends on organisational size, complexity and maturity.

9.5 Designing and Implementing a Corporate Performance Framework

A corporate performance framework connects strategy with measurement and action.

A practical implementation sequence can begin with organisational purpose.

Step 1: Understand the strategy

Identify:

Strategic priorities
Objectives
Outcomes
Major initiatives

Step 2: Understand the operating model

Understand how the organisation actually operates.

Identify:

Functions
Processes
Services
Customers
Technology
Suppliers
Dependencies

Step 3: Identify performance questions

Ask:

What does leadership need to know?
What do managers need to know?
What needs early warning?
What outcomes matter most?

Step 4: Define objectives

Translate strategic priorities into measurable objectives.

Step 5: Define measures

Identify measures that provide evidence of progress.

Step 6: Select KPIs

Choose the measures that deserve formal KPI status.

Step 7: Define KPI architecture

Document:

Definitions
Formulas
Data sources
Owners
Frequency
Targets
Thresholds

Step 8: Establish data requirements

Identify:

Sources
Data quality
Integration
Lineage
Ownership

Step 9: Design dashboards and reports

Create views appropriate to:

Executives
Managers
Operational teams
Analysts

Step 10: Establish governance

Define:

Review forums
Decision rights
Escalation
Accountability
KPI governance

Step 11: Implement performance reviews

Create a regular cycle of:

Measure → Analyse → Review → Decide → Act

Step 12: Establish action tracking

Track:

Actions
Owners
Due dates
Status
Evidence
Outcomes

Step 13: Measure benefits

Determine whether actions and initiatives produced intended results.

Step 14: Review the framework

The framework itself should be reviewed regularly.

This prevents the measurement system from becoming outdated.

Implementation roadmap

A practical roadmap may include:

Phase 1: Discovery and current-state assessment

Phase 2: Framework and KPI design

Phase 3: Data and reporting design

Phase 4: Technology implementation

Phase 5: Governance and review implementation

Phase 6: Continuous improvement

The exact sequencing should be adapted to the organisation.

9.6 Complete Corporate Performance Toolkit

A performance professional should have a practical set of tools that support the entire performance lifecycle.

KPI catalogue

A KPI catalogue lists the organisation's approved KPIs.

It may include:

KPI name
Category
Objective
Owner
Status
Reporting frequency

KPI dictionary

The KPI dictionary provides the detailed definition of each KPI.

It should contain sufficient information for consistent calculation and interpretation.

KPI template

A KPI template can capture:

Name
Purpose
Definition
Formula
Unit
Source
Owner
Baseline
Target
Threshold
Frequency
Reporting period

Objective template

An objective template can capture:

Objective
Strategic priority
Owner
Outcome
Measures
Target
Initiatives

OKR template

An OKR, or Objectives and Key Results, template can capture:

Objective
Key Result
Baseline
Target
Current status
Owner
Review cycle

Balanced Scorecard

A Balanced Scorecard can structure objectives and measures across selected organisational perspectives.

For this performance framework, the emphasis remains on non-financial dimensions such as:

Customer
Internal process
Learning and growth

Strategy map

A strategy map can show relationships between strategic objectives.

It helps communicate how different objectives are expected to contribute to broader organisational outcomes.

Performance scorecard

A performance scorecard may include:

Objective
KPI
Actual
Target
Variance
Status
Trend
Commentary
Action

Dashboard template

A dashboard template may include:

KPI cards
Trends
Targets
Variances
Exceptions
Commentary
Actions

Performance report

A standard performance report can include:

Executive summary
Overall performance
Significant exceptions
Trends
Root causes
Risks
Improvement actions
Decisions required

Review agenda

A performance review agenda may include:

Previous actions
Current performance
Exceptions
Trends
Root causes
Risks
Forecasts
Decisions
Actions

Variance analysis template

A variance analysis template can capture:

KPI
Target
Actual
Variance
Significance
Cause
Evidence
Action

Root-cause analysis template

A root-cause template can include:

Problem
Symptoms
Evidence
Potential causes
Root cause
Corrective action
Preventive action
Verification

Action log

An action log should include:

Action
Owner
Priority
Due date
Status
Evidence
Outcome

Benefits tracker

A benefits tracker can include:

Benefit
Owner
Baseline
Target
Current result
Expected date
Actual result
Status
Evidence

Risk-performance matrix

A risk-performance matrix connects performance conditions with risk.

For example:

Performance Condition	Risk Position	Management Response
Strong performance	Low risk	Continue monitoring
Strong performance	Increasing risk	Investigate underlying exposure
Weak performance	Low risk	Improvement required
Weak performance	High risk	Immediate management attention

Maturity assessment

A maturity assessment can evaluate:

Strategy
Governance
Leadership
Processes
Measurement
Data
Reporting
Technology
Culture

Master performance toolkit

The complete toolkit can therefore be viewed as:

Strategy Map + Objective Catalogue + KPI Catalogue + KPI Dictionary + Scorecard + Dashboard + Performance Report + Variance Analysis + Root-Cause Analysis + Action Log + Benefits Tracker + Risk Matrix + Maturity Assessment

These tools support different stages of the performance lifecycle.

9.7 Worked Example, Master Checklist and Glossary

A complete performance framework should be capable of being followed from beginning to end.

Consider a generic service organisation seeking to improve customer service responsiveness.

Step 1: Strategic priority

Strategic Priority: Improve customer service quality and responsiveness

Step 2: Objective

Objective: Improve the speed and quality of customer enquiry resolution

Step 3: Performance questions

Management asks:

How quickly are enquiries resolved?
Are customers receiving correct answers?
Are customers having to contact the organisation repeatedly?
Where are delays occurring?
Is performance improving?

Step 4: KPIs

Potential KPIs include:

Percentage resolved within required timeframe
Average resolution time
First-contact resolution
Customer satisfaction
Repeat contact rate
Complaint rate

Step 5: Targets

Targets are established for each KPI based on organisational requirements and appropriate evidence.

Step 6: Data

Data is collected from:

Customer service system
Survey platform
Complaint system
Operational reporting

Step 7: Dashboard

The dashboard shows:

Actual
Target
Variance
Trend
Status
Significant exceptions

Step 8: Analysis

The dashboard shows that resolution performance has declined.

Further analysis reveals that the deterioration is concentrated within complex enquiries.

Step 9: Root cause

Investigation identifies:

Additional approval requirements
Incomplete information at intake
Limited specialist capacity

Step 10: Action

Management agrees:

Improve information captured at intake
Simplify the approval workflow
Increase specialist cross-training

Step 11: Measurement

Performance is monitored after implementation.

Step 12: Benefits

The organisation assesses whether:

Resolution time improved
First-contact resolution improved
Customer satisfaction improved
Repeat contacts declined

Step 13: Review

The performance review confirms whether the improvement has been sustained.

This example demonstrates the complete chain:

Strategy → Objective → Performance Questions → KPIs → Targets → Data → Dashboard → Analysis → Root Cause → Action → Benefits → Outcome

Master implementation checklist

A performance professional can use the following checklist.

Strategy

Strategic priorities are clearly defined
Objectives are measurable
Performance measures are linked to objectives
Strategic and operational performance are connected

KPIs

Every KPI has a clear purpose
KPI definitions are documented
Formulas are agreed
Owners are assigned
Targets are established
Thresholds are defined
Obsolete KPIs are retired

Data

Data sources are known
Data ownership is clear
Data quality is assessed
Definitions are consistent
Data lineage is understood
Access is controlled

Reporting

Reports have defined audiences
Dashboards support decisions
Actual and target are shown together
Trends are visible
Significant variances are explained
Reporting duplication is controlled

Governance

Performance roles are defined
Review forums exist
Decision rights are clear
Escalation criteria are defined
Actions are tracked

Analysis

Variance analysis is performed
Trends are reviewed
Root causes are investigated
Benchmarking is used appropriately
Forecasting is used where useful

Improvement

Corrective actions are tracked
Preventive actions are considered
Benefits are measured
Improvement effectiveness is verified
The performance system itself is reviewed

Essential glossary

Actual: The performance result that occurred during a defined period

Benchmark: A reference point used to compare performance

Baseline: A starting or reference performance position

Business Intelligence: Technology and methods used to access, analyse and understand organisational data

Capability: An organisation's ability to perform a particular function

Dashboard: A visual presentation of performance information

Data governance: Policies, responsibilities and controls used to manage data

Data lineage: The path through which data moves from source to final use

Effectiveness: The degree to which intended outcomes are achieved

Efficiency: The relationship between outputs and resources used

Forecast: An estimate of future performance based on available information and assumptions

Indicator: A signal that provides information about a condition or trend

KPI: A Key Performance Indicator selected to monitor an important aspect of performance

KPI dictionary: A controlled catalogue containing detailed KPI definitions and supporting information

Leading indicator: A measure that may provide an early signal of future performance

Lagging indicator: A measure that records an outcome that has already occurred

Maturity: The level of organisational capability developed in a particular area

Metric: A quantified measurement used to understand or assess performance

Measure: A quantified representation of something that can be observed

Outcome: A result or effect produced by activities or services

Output: Something produced by a process or activity

Performance gap: The difference between current performance and a desired or reference position

Performance governance: The framework used to establish accountability, decision rights and oversight for performance

Performance management: The process of using performance information to plan, measure, analyse, review and improve organisational performance

Performance measurement: The process of quantifying performance using defined measures

Root cause: An underlying factor contributing to a problem whose treatment can help prevent recurrence

Target: The desired level of performance

Threshold: A defined level at which attention or action may be required

Tolerance: An acceptable range of variation around an expected level

Trend: The direction or pattern of performance over time

The complete performance management architecture

The entire book can now be represented through a connected architecture:

Strategy

↓

Objectives

↓

Performance Framework

↓

KPIs and Measures

↓

Targets and Thresholds

↓

Data

↓

Dashboards and Reports

↓

Analysis

↓

Performance Reviews

↓

Decisions

↓

Actions

↓

Improvement

↓

Benefits and Outcomes

↓

Measurement Again

This architecture demonstrates an important principle.

Corporate performance is not a collection of independent activities.

It is an integrated management system.

The ultimate principle

Performance maturity is achieved when an organisation can consistently connect:

Purpose → Strategy → Objectives → Measures → Data → Insight → Decisions → Actions → Outcomes → Learning

The objective is not simply to reach a particular maturity level.

The objective is to develop the capability required to manage performance effectively.

A mature organisation knows what it wants to achieve.

It knows how performance will be measured.

It trusts the information it receives.

It understands what the information means.

It knows who is accountable.

It acts on important findings.

It measures whether those actions worked.

And it continuously improves the entire system.

That is the essence of a complete corporate performance capability.

10. The Role of AI in Corporate Performance Measurement

Artificial Intelligence is increasingly becoming part of the performance management landscape.

AI can help organisations collect information, identify patterns, detect anomalies, analyse trends, generate commentary, support forecasting and assist decision-making.

However, AI should not be treated as a replacement for sound performance management.

Poorly defined KPIs remain poorly defined when AI is introduced.

Poor-quality data remains poor-quality data.

Weak governance remains weak governance.

AI can increase analytical capability, but it can also increase the speed at which errors are produced or misleading conclusions are communicated.

The strongest approach is therefore to treat AI as an additional capability within an established performance management system.

A useful model is:

AI + Trusted Data + Clear Objectives + Strong Governance + Human Oversight = Enhanced Performance Management

This chapter examines how AI can support corporate performance measurement and where appropriate controls are required.

10.1 Understanding AI in Corporate Performance

Artificial Intelligence, or AI, refers broadly to technologies that enable computer systems to perform tasks that traditionally require forms of human intelligence.

These tasks can include:

Pattern recognition
Classification
Prediction
Language processing
Anomaly detection
Recommendation
Content generation
Data interpretation

AI is not one single technology.

It includes several different approaches and capabilities.

Machine learning

Machine learning involves systems that identify patterns in data and use those patterns to perform tasks or make estimates.

Machine learning can support:

Forecasting
Classification
Anomaly detection
Pattern recognition

The quality of the result depends heavily on the quality and relevance of the data used.

Generative AI

Generative AI produces new content based on patterns learned from data.

It can generate:

Text
Summaries
Explanations
Narratives
Questions
Structured outputs

Within performance management, generative AI can help turn complex performance information into readable commentary.

Natural Language Processing

Natural Language Processing, or NLP, enables systems to process and interpret human language.

NLP can help analyse:

Customer comments
Employee feedback
Survey responses
Audit reports
Performance commentary
Service records

This can make large volumes of textual information easier to analyse.

Predictive models

Predictive models use data and statistical or machine-learning techniques to estimate future conditions.

Examples include:

Expected service demand
Likely workload
Potential performance deterioration
Expected resolution times

A predictive model provides an estimate rather than certainty.

AI-assisted decision support

AI can help decision-makers by:

Identifying relevant information
Highlighting patterns
Comparing scenarios
Summarising evidence
Identifying anomalies
Suggesting questions for investigation

The final decision should remain appropriately governed.

Traditional reporting versus AI

Traditional reporting generally answers:

What happened?

Analytics can help answer:

Why did it happen?

Predictive analytics asks:

What may happen next?

AI can potentially support all three areas while also making interaction with performance information more accessible.

AI is not a performance framework

AI does not replace:

Strategy
Objectives
KPIs
Targets
Governance
Accountability
Management decisions

AI is a capability that operates within the performance framework.

AI maturity

Organisations should consider their level of AI capability.

A useful progression is:

Manual Reporting → Automated Reporting → Analytical Assistance → AI-Assisted Analysis → Predictive AI → Integrated AI Performance Management

The organisation should establish strong foundations before adopting advanced capabilities.

10.2 AI for Data Collection, Preparation and Data Quality

Data quality is fundamental to performance measurement.

AI can assist with data preparation and quality management but it cannot automatically make unreliable data trustworthy.

Data classification

AI can help classify large volumes of information.

For example, it may classify:

Customer complaints
Service incidents
Project issues
Risk records
Employee feedback

This can reduce manual categorisation.

Duplicate detection

AI can identify records that appear to represent the same underlying entity.

For example, customer or service records may contain:

Different spellings
Different formats
Repeated entries

Potential duplicates can be flagged for review.

Missing data

AI can identify patterns in missing information.

It may highlight:

Missing fields
Incomplete records
Unexpected gaps
System-specific omissions

The system should distinguish between identifying missing data and inventing missing information.

Anomaly detection

AI can identify unusual records.

For example:

A service request with an unusually long resolution time
A sudden change in transaction volume
An unexpected data value
An unusual operational pattern

An anomaly should trigger investigation rather than automatic correction.

Data categorisation

AI can help categorise unstructured information.

For example, customer comments might be grouped into:

Waiting time
Service quality
Accessibility
Technology
Staff interaction
Process complexity

This can reveal themes across thousands of comments.

Data reconciliation

AI may assist in comparing information from multiple systems.

For example:

System A: 4,820 completed cases

System B: 4,765 completed cases

AI-assisted analysis could help identify where the difference originates.

Possible explanations might include:

Timing
Different definitions
Missing records
Duplicate records
Integration problems

Data preparation

AI can assist with repetitive preparation activities such as:

Standardising formats
Categorising records
Identifying inconsistent values
Detecting unusual patterns
Flagging incomplete records

Human validation

Automated data preparation should still have appropriate validation.

The organisation should know:

What the AI changed
Why it changed it
What rules were applied
What uncertainty exists
Who approved the process

Data quality monitoring

AI can support continuous data quality monitoring.

Instead of checking data only periodically, the organisation can identify emerging quality problems as they occur.

Data quality limitations

AI may incorrectly classify information.

It may misinterpret context.

It may identify a genuine variation as an anomaly.

It may fail to detect a subtle error.

Therefore:

AI-assisted data quality is not the same as guaranteed data quality.

The AI data-quality cycle

A practical model is:

Collect → Validate → Classify → Detect Anomalies → Review → Correct → Monitor

AI can support several stages.

Human accountability remains important.

10.3 AI for KPI Design, Monitoring and Performance Analysis

AI can assist organisations in designing and managing KPI systems.

However, KPI selection should remain driven by organisational purpose and objectives.

KPI discovery

AI can analyse strategy documents, objectives, operational information and existing measurement catalogues to identify potential measures.

It may suggest:

Candidate KPIs
Supporting measures
Leading indicators
Lagging indicators
Data sources

These should be reviewed by performance professionals.

KPI definition

AI can help draft KPI definitions.

For example, it can assist with:

KPI descriptions
Formula wording
Measurement units
Reporting frequency
Data requirements

The final definition should be formally approved.

KPI rationalisation

Organisations often accumulate too many measures.

AI can help identify:

Duplicate KPIs
Similar measures
Measures with low usage
Obsolete measures
Conflicting definitions

This can support KPI rationalisation.

KPI monitoring

AI can continuously monitor performance against defined conditions.

It can identify:

Target breaches
Rapid deterioration
Unusual variation
Persistent underperformance
Unexpected improvement

Trend identification

AI can examine historical data to identify trends that may not be immediately visible.

For example:

A KPI may remain within target while gradually deteriorating.

AI can highlight the trajectory before a formal threshold is breached.

Variance analysis

AI can assist in identifying significant variances.

It may compare:

Actual versus target
Current versus previous period
Current versus baseline
Actual versus forecast

The analysis can then identify areas requiring investigation.

Correlation analysis

AI can identify relationships between measures.

For example:

Increased backlog and increased response time
Higher complexity and longer resolution time
Training completion and quality performance

However, correlation does not automatically establish causation.

The relationship requires appropriate investigation.

Anomaly detection

AI can monitor large numbers of KPIs simultaneously and identify unusual movements.

This can help analysts focus attention on important exceptions.

Identifying obsolete KPIs

AI can help identify measures that:

Are no longer connected to current objectives
Are rarely used
Duplicate other measures
Have consistently poor data quality
No longer influence decisions

This supports KPI lifecycle management.

AI and performance questions

AI can also help users ask better questions.

For example:

Which KPIs changed most significantly?
Which services have deteriorated?
Which issues are recurring?
Which areas show unusual variation?
Which measures appear to be moving together?

This makes analytical capability more accessible.

AI should not choose KPIs automatically

A KPI is important because it relates to organisational purpose and objectives.

AI can recommend candidate measures.

It should not independently determine what the organisation considers important.

That remains a management and governance responsibility.

10.4 AI for Dashboards, Reporting and Performance Commentary

AI can change how people interact with performance information.

Traditional dashboards require users to interpret charts and tables.

AI can provide an additional conversational layer.

Automated summaries

AI can summarise large performance reports.

For example:

"Overall service performance remained stable but two service categories deteriorated significantly during the reporting period."

This can help executives understand the key message quickly.

Performance commentary

AI can draft commentary based on defined data.

A useful commentary may explain:

What changed
How significant the change was
Where it occurred
What evidence is available
What requires attention

Narrative generation

AI can convert structured information into readable narrative.

For example:

Data: Resolution performance declined from 94% to 89%

AI-generated draft: Performance declined by five percentage points during the reporting period with the largest deterioration occurring within complex service requests.

The draft should be validated against the underlying data.

Exception summaries

AI can identify and summarise the most significant exceptions.

This can reduce the effort required to review large performance packs.

Natural-language interaction

Users can increasingly ask questions in ordinary language.

For example:

Which KPIs deteriorated this period?
What changed most significantly?
Show me the areas below target
Which services have recurring problems?
What are the largest emerging risks?

This can make performance information more accessible.

Drill-down through conversation

AI may allow a user to move from summary to detail conversationally.

For example:

Question: Why did service performance decline?

Follow-up: Which teams were most affected?

Follow-up: When did the deterioration begin?

Follow-up: What changed at that time?

This can make analytical investigation more intuitive.

Automated management reports

AI can assist in preparing:

Executive summaries
Performance packs
KPI commentary
Exception reports
Review agendas
Action summaries

This can reduce repetitive reporting effort.

Human review

AI-generated performance commentary should be reviewed where accuracy matters.

The reviewer should confirm:

The numbers are correct
The interpretation is supported
The language does not overstate certainty
Important context has not been omitted

Hallucinations

A hallucination occurs when an AI system generates information that is unsupported or incorrect.

In performance reporting, this could be particularly dangerous.

For example, an AI system might produce a plausible explanation for a KPI decline that is not supported by the data.

AI should therefore distinguish between:

Observed evidence

and

Possible explanation

Source traceability

Where possible, AI-generated analysis should allow users to trace important claims back to the underlying data.

This improves confidence and auditability.

The AI reporting model

A useful approach is:

Data → Validated KPI → AI Analysis → Draft Commentary → Human Review → Published Report

This combines automation with control.

10.5 AI for Forecasting, Prediction and Early-Warning Indicators

One of the most valuable applications of AI is helping organisations look ahead.

Forecasting

AI can analyse historical and current information to estimate future performance.

Possible applications include:

Service demand
Workload
Resolution time
Capacity
Incident volume
Customer contact

Pattern recognition

AI can identify patterns that may be difficult to detect manually.

For example:

Gradual deterioration
Repeating cycles
Unusual combinations of events
Emerging changes in demand

Predictive performance

Predictive models can estimate whether a KPI is likely to move outside an acceptable range.

For example:

A service KPI is currently within target but the model identifies a high likelihood of deterioration based on increasing workload and declining capacity.

This creates an opportunity for earlier intervention.

Early-warning indicators

AI can combine multiple indicators to identify emerging conditions.

For example:

Increasing backlog + increasing complexity + declining capacity = potential future service deterioration

Each measure individually may appear manageable.

Together, they may provide a stronger warning signal.

Scenario analysis

AI can help explore scenarios.

For example:

"What might happen if workload increases significantly?"

"What might happen if a planned process improvement is delayed?"

"What might happen if system availability declines?"

Scenario analysis can help management prepare responses.

Sensitivity analysis

AI can also examine how changes in assumptions affect potential outcomes.

This can reveal which variables have the greatest influence on expected performance.

Forecast uncertainty

Forecasts should not be presented as guaranteed outcomes.

Important factors include:

Data quality
Historical relevance
Model assumptions
Changing conditions
Unexpected events

Where appropriate, forecasts should include uncertainty ranges or confidence information.

Model drift

Model drift occurs when the conditions represented by a model change over time.

A model trained using historical patterns may become less accurate when:

Customer behaviour changes
Processes change
Technology changes
Organisational structures change
External conditions change

Models therefore require monitoring.

Prediction versus decision

A model may indicate that a problem is likely.

That does not automatically determine what management should do.

For example:

AI: Performance deterioration is increasingly likely

Management: Determine the appropriate intervention

The distinction is important.

AI forecasting cycle

A useful model is:

Historical Data → Model → Forecast → Monitor Actuals → Assess Accuracy → Update Model

This creates a learning cycle.

10.6 AI-Assisted Decision-Making, Improvement and Performance Management

AI can support decision-making by helping people understand complex performance information.

It should generally be treated as decision support rather than an independent decision-maker.

Root-cause support

AI can analyse large datasets to identify potential relationships and recurring patterns.

It can help generate hypotheses for investigation.

For example:

"Performance deterioration appears concentrated among requests requiring a particular approval stage."

This is a useful starting point.

It is not automatically a confirmed root cause.

Improvement opportunities

AI can identify potential areas for improvement by examining:

Repeated delays
High rework
Recurring incidents
Customer complaints
Process bottlenecks
Capacity constraints

Action prioritisation

AI may help compare potential actions using defined criteria.

For example:

Performance impact
Urgency
Risk
Complexity
Dependency

The decision criteria should be transparent.

Outcome assessment

AI can compare performance before and after an intervention.

For example:

Before intervention: 87%

After intervention: 94%

The improvement is visible.

However, AI should also help examine whether other factors changed during the same period.

This reduces the risk of attributing all improvement to one action.

Management decision support

AI can help management by presenting:

Relevant evidence
Alternative interpretations
Potential scenarios
Key uncertainties
Areas requiring investigation

This can improve the quality of discussion.

AI recommendations versus management decisions

This distinction should remain explicit.

AI recommendation: Potential intervention A appears likely to improve service performance under the stated assumptions

Management decision: Approve, reject or investigate the proposed intervention

AI provides analysis.

Management retains accountability for the decision.

Human oversight

Human oversight is particularly important when decisions affect:

Customers
Employees
Critical services
Compliance
Risk
Organisational priorities

Explainability

Explainability concerns the ability to understand why an AI system produced a particular result or recommendation.

Where AI contributes to important performance decisions, users should understand:

What information was considered
What assumptions were used
What limitations exist
How confident the result is

AI and continuous improvement

AI can support continuous improvement by continuously examining performance information.

The cycle becomes:

Measure → Analyse → Identify Opportunity → Recommend → Decide → Act → Measure Again

This can increase the speed of organisational learning.

Avoiding automation bias

Automation bias occurs when people place excessive trust in an automated output simply because it was produced by a system.

An AI-generated recommendation should therefore be treated as evidence to assess rather than an instruction to follow automatically.

10.7 AI Governance, Risks, Ethics and the Future of Corporate Performance

AI introduces new governance requirements.

Organisations need to understand not only what AI can do but also how its outputs should be controlled.

Data privacy

AI systems may process large quantities of information.

Organisations must ensure that data is handled appropriately and that access is controlled.

Security

AI systems can introduce security considerations involving:

Data access
System access
Model access
Prompt or input information
Generated outputs
Integration points

Security controls should be appropriate to the environment.

Bias

AI systems can reproduce or amplify patterns present in their training or input data.

This can create biased results.

Performance professionals should therefore consider whether:

The data is representative
Categories are appropriate
Historical patterns contain bias
Outputs are consistent across relevant groups

Explainability

Important AI-supported decisions may require understandable explanations.

A system that produces a recommendation without sufficient context can make accountability difficult.

Hallucinations

AI systems can generate information that sounds plausible but is incorrect.

This creates particular risk when AI is used to generate performance commentary or explanations.

Incorrect analysis

AI can also produce incorrect conclusions from correct data.

Potential causes include:

Incorrect assumptions
Misinterpreted relationships
Poor model selection
Incomplete context

Correct data does not guarantee correct analysis.

Model drift

Models may become less reliable as the environment changes.

Performance systems should therefore include mechanisms for:

Monitoring
Validation
Recalibration
Retirement

Automation risk

Automating performance decisions can create excessive dependence on systems.

Critical decisions should have appropriate human oversight.

Auditability

An organisation should be able to determine:

What AI system was used
What data was used
What analysis was performed
What output was produced
Who reviewed it
What decision followed

This supports accountability.

Human accountability

AI does not remove organisational accountability.

If a manager uses an AI-generated analysis to support a decision, responsibility for the decision should remain appropriately assigned.

AI governance framework

A practical AI performance governance framework can include:

Purpose

Why is AI being used?

Data

What information does it use?

Model

How does it operate?

Controls

What safeguards exist?

Human oversight

Who reviews the output?

Validation

How is accuracy assessed?

Monitoring

How is ongoing performance monitored?

Auditability

Can the result be traced and reviewed?

Accountability

Who is responsible for the outcome?

AI use-case assessment

Before introducing AI into performance management, organisations should consider:

Business value
Data availability
Data quality
Risk
Complexity
Explainability
Human oversight
Security
Privacy
Operational impact

Not every performance problem requires AI.

AI in greenfield environments

A new performance environment can incorporate AI from the beginning.

However, the organisation should establish:

Clear data definitions
Reliable data architecture
KPI governance
Appropriate controls
Human oversight

before building advanced AI capability.

AI in mature environments

Mature environments may already contain:

Multiple data sources
Legacy systems
Established KPIs
Existing dashboards
Historical reports

AI implementation may therefore require integration and rationalisation.

The future of corporate performance

AI is likely to change how performance professionals work.

Routine activities may become increasingly automated.

Performance professionals may spend more time on:

Defining performance questions
Interpreting evidence
Challenging assumptions
Investigating causes
Designing improvements
Advising management
Governing AI-supported analysis

The role may therefore shift from producing information towards interpreting and governing information.

AI should augment people

The strongest model is not:

AI replaces performance professionals

It is:

AI augments performance professionals

AI can process large volumes of information quickly.

People provide:

Context
Judgement
Accountability
Organisational understanding
Ethical consideration
Decision authority

The AI-enabled performance cycle

A future-oriented performance system can be represented as:

Data → AI-Assisted Quality → KPI Monitoring → AI Analysis → Forecasting → Human Review → Decision → Action → Outcome → Continuous Learning

This creates a more dynamic performance environment.

The ultimate principle

AI can make performance management faster.

It can make analysis broader.

It can make reporting more accessible.

It can help identify patterns that might otherwise remain hidden.

But AI does not remove the fundamentals.

The organisation still needs:

Clear Strategy

Meaningful Objectives

Well-Designed KPIs

Trusted Data

Strong Governance

Responsible Analysis

Human Accountability

The most effective future performance environments will combine these foundations with carefully governed AI.

The central principle is therefore:

Use AI to increase insight, not to outsource responsibility.

When AI is combined with reliable data, clear objectives, disciplined governance and capable people, it can become a powerful component of corporate performance management.

The technology should serve the performance system.

The performance system should serve organisational objectives.

And organisational objectives should ultimately remain connected to meaningful outcomes.

11. 55 Essential Guidance Tips for Corporate Performance Professionals

Corporate performance professionals operate at the point where strategy, measurement, data, analysis, governance and management action meet.

The role is not simply to produce reports.

It is to help an organisation understand how it is performing, why performance is changing and what should happen next.

This requires technical capability but it also requires judgement.

The following 55 tips provide a practical field guide for performance analysts, consultants, managers, business analysts, transformation professionals and performance leaders.

They apply to both greenfield environments, where a performance capability is being established, and mature environments, where an existing system needs to be improved.

11.1 Start With the Business Purpose

Performance measurement should begin with purpose.

Before asking which KPIs are required, understand what the organisation is trying to achieve and why performance needs to be measured.

A performance system without a clear purpose can quickly become a collection of reports, dashboards and measures that consume effort without improving decisions.

The fundamental question is simple:

What decisions should this performance information help people make?

If that question cannot be answered, the measurement system may not yet have a sufficiently clear purpose.

Action Steps:

Define the organisational purpose that the performance system must support
Identify the decisions that performance information needs to improve

11.2 Understand the Strategy

A performance professional must understand the strategy before designing the measurement framework.

This means understanding strategic priorities, objectives, expected outcomes, major initiatives and the organisational capabilities required to achieve them.

A KPI may be technically accurate yet strategically irrelevant.

The purpose of performance measurement is not to measure everything that can be measured.

It is to measure what matters.

Action Steps:

Map strategic priorities to objectives and expected outcomes
Identify which aspects of strategy require evidence of progress

11.3 Understand the Operating Model

The operating model describes how an organisation is structured to deliver its objectives through people, processes, technology, data and governance.

Understanding it helps the performance professional identify where performance is actually created.

For example, a service problem may appear to be a team issue when the underlying cause is a process dependency, technology constraint or unclear ownership.

Performance measurement should therefore reflect how work actually flows through the organisation.

Action Steps:

Map the major organisational capabilities, processes and dependencies
Identify where performance is created, constrained and handed between teams

11.4 Identify the Real Performance Questions

Do not begin with a list of available data.

Begin with questions.

Examples include:

What is working?

What is deteriorating?

Where are customers experiencing problems?

Which processes are creating delays?

Which risks are increasing?

Which objectives are progressing?

Which interventions are producing results?

Good performance measurement answers meaningful questions.

Action Steps:

Create a list of the decisions and performance questions management needs answered
Link each important question to appropriate evidence

11.5 Never Start With KPIs

KPIs are important but they should not be the starting point.

Start with purpose, strategy, objectives and performance questions.

Then identify the information required to answer those questions.

Only then should KPIs be selected.

Starting with KPIs often produces a measurement system based on what data happens to be available rather than what the organisation actually needs to understand.

Action Steps:

Follow the sequence Purpose → Strategy → Objectives → Questions → Measures → KPIs
Challenge every proposed KPI by asking what decision it supports

11.6 Establish the Current State

Before designing a future performance environment, understand the current state.

Examine existing KPIs, reports, dashboards, data sources, governance arrangements, review forums and ownership.

The current state may contain useful capability that should be retained.

It may also contain duplication, inconsistent definitions and unnecessary reporting.

A strong future state begins with an accurate understanding of the present.

Action Steps:

Document current measures, reports, systems, owners and review processes
Identify strengths, weaknesses, duplication and gaps

11.7 Distinguish Symptoms From Causes

A KPI showing poor performance does not necessarily reveal the cause.

A backlog is a symptom.

A long resolution time may be a symptom.

A high error rate may be a symptom.

The underlying cause could involve capacity, process design, technology, training, dependencies or unclear requirements.

Treating symptoms without investigating causes often results in temporary improvement followed by recurrence.

Action Steps:

Separate observed performance problems from suspected causes
Use evidence-based root-cause analysis before defining corrective action

11.8 Define Every Important Term

Different teams often use the same word to mean different things.

Terms such as "resolved", "completed", "available", "active", "customer", "incident" and "productivity" may have different interpretations.

Without clear definitions, performance comparisons become unreliable.

A shared vocabulary is therefore part of the measurement system.

Action Steps:

Establish clear definitions for important performance terminology
Record definitions in a controlled glossary or KPI dictionary

11.9 Build a KPI Dictionary

A KPI dictionary creates a common reference for performance measures.

Each KPI should ideally include its name, definition, purpose, formula, unit, data source, reporting frequency, owner, target, thresholds and calculation rules.

This prevents different reports from calculating the same KPI differently.

It also makes onboarding and governance easier.

Action Steps:

Create a standard KPI definition template
Maintain the dictionary under formal ownership and governance

11.10 Establish Clear Ownership

Every important performance measure should have an owner.

The KPI owner is accountable for the relevance and use of the measure.

The data owner may be responsible for the underlying data.

The reporting owner may be responsible for producing and distributing the information.

Separating these responsibilities where necessary prevents accountability from becoming ambiguous.

Action Steps:

Assign named owners to KPIs, data and reporting activities
Document responsibilities using a clear governance model

11.11 Keep the KPI Set Manageable

More KPIs do not automatically create better performance management.

Too many measures create information overload.

Managers may struggle to distinguish important signals from background information.

A smaller set of meaningful KPIs can create greater focus than a large collection of weak measures.

The objective is not maximum measurement.

It is useful measurement.

Action Steps:

Remove duplicate, obsolete and low-value measures
Focus core dashboards on measures that influence important decisions

11.12 Balance Leading and Lagging Indicators

A leading indicator provides information about factors that may influence future performance.

A lagging indicator shows an outcome that has already occurred.

Both are useful.

Lagging indicators tell you what happened.

Leading indicators can provide an earlier signal of what may happen next.

A strong performance framework normally combines both.

Action Steps:

Identify leading indicators for important outcomes
Pair outcome measures with appropriate driver measures

11.13 Measure Outcomes Where Possible

Activities and outputs are often easier to measure than outcomes.

However, completing an activity does not necessarily mean that the desired result has been achieved.

For example, completing training does not automatically demonstrate improved capability.

Publishing a process does not automatically demonstrate process improvement.

Where practical, measurement should extend beyond activity towards meaningful outcomes.

Action Steps:

Identify the intended outcome behind each major activity
Add outcome measures where reliable evidence can be obtained

11.14 Do Not Confuse Activity With Performance

High activity levels do not automatically indicate strong performance.

A team may process many cases while creating significant rework.

A project may produce many documents without achieving its intended outcome.

A service may handle a high volume of requests while customer experience deteriorates.

Performance requires consideration of quality, outcomes, effectiveness and impact rather than activity alone.

Action Steps:

Examine quality and outcomes alongside activity measures
Ask whether increased activity is actually producing better results

11.15 Establish a Reliable Baseline

A baseline is the starting point against which subsequent performance can be compared.

Without a reliable baseline, it becomes difficult to determine whether performance has improved, deteriorated or simply changed.

Baselines should be based on appropriate historical or current evidence.

They should also reflect any important changes in definitions or measurement methods.

Action Steps:

Establish a documented baseline for important measures
Record the period, source and methodology used to create it

11.16 Set Meaningful Targets

A target provides a defined level of expected performance.

Targets should be meaningful rather than arbitrary.

A useful target should consider historical performance, organisational objectives, service expectations, available capability and relevant constraints.

Targets that are impossible may discourage people.

Targets that are too easy may provide little useful information.

Action Steps:

Link targets to objectives and evidence
Review targets when circumstances or strategic priorities change

11.17 Define Thresholds and Tolerances

Targets alone may not provide sufficient guidance.

A threshold identifies a point at which performance requires attention.

A tolerance defines an acceptable range of variation.

These concepts help establish when management intervention is required.

They also reduce unnecessary escalation of minor fluctuations.

Action Steps:

Define appropriate thresholds and tolerances for important KPIs
Establish what action should occur when each threshold is breached

11.18 Understand the Data Before Trusting It

A number appearing in a dashboard does not automatically make it reliable.

Understand where the data originates, how it is captured, how it is transformed and how the KPI is calculated.

Data should be understood before conclusions are drawn from it.

A sophisticated dashboard built on poorly understood data can create false confidence.

Action Steps:

Trace important KPIs from dashboard to source
Document calculation and transformation rules

11.19 Trace Measures Back to Source

Every important measure should have a clear data lineage.

Data lineage describes the path information follows from its original source through processing and transformation to its final presentation.

Traceability helps identify errors and improves confidence in reported information.

It also supports investigation when two systems produce different results.

Action Steps:

Document the source and transformation path for critical KPIs
Investigate unexplained differences between data sources

11.20 Challenge Data Quality

Data quality should be actively challenged rather than assumed.

Important dimensions include:

Accuracy
Completeness
Consistency
Timeliness
Validity
Uniqueness
Integrity

A performance professional should be willing to question a number when the evidence behind it is weak.

Action Steps:

Establish data-quality checks for critical measures
Record and address recurring data-quality problems

11.21 Create a Single Definition of the Truth

Different departments should not report different versions of the same KPI without a clear reason.

A single source of truth means that an agreed definition and controlled data source provide the authoritative basis for a measure.

This does not necessarily mean every organisation needs one physical database.

It means people should know which definition and source are authoritative.

Action Steps:

Establish authoritative definitions for important measures
Resolve conflicting KPI calculations through governance

11.22 Understand the Reporting Cycle

Performance information has a rhythm.

Some measures require real-time monitoring.

Others may be reviewed daily, weekly, monthly, quarterly or annually.

The reporting frequency should reflect how quickly the underlying performance can change and how quickly management can respond.

Reporting too frequently can create noise.

Reporting too slowly can delay action.

Action Steps:

Match reporting frequency to the speed and importance of performance change
Review whether each reporting cycle still supports timely decisions

11.23 Design Reports Around Decisions

A report should help someone understand something and decide what to do.

If a report contains many pages but does not support meaningful decisions, its value is questionable.

Start with the decisions and work backwards to determine what information is required.

Action Steps:

Identify the decisions supported by each major report
Remove information that does not contribute to those decisions

11.24 Design Dashboards for Their Audience

Different audiences require different levels of information.

Executives may need strategic indicators and exceptions.

Managers may need operational detail.

Analysts may need deeper datasets.

A single dashboard should not attempt to serve every audience equally.

Action Steps:

Define the audience and decisions before designing each dashboard
Provide appropriate levels of detail and drill-down

11.25 Keep Dashboards Simple

A dashboard should make important information easier to understand.

Too many charts, colours, filters and indicators can create confusion.

Good dashboard design prioritises clarity.

Every visual element should have a purpose.

Action Steps:

Remove unnecessary visual elements
Highlight the measures and exceptions that require attention

11.26 Show Trends, Not Just Current Values

A single value tells you where performance is now.

A trend provides context.

A KPI at 92% may look healthy until the trend shows a sustained decline from 98%.

Conversely, a KPI below target may be improving rapidly.

Performance should therefore be viewed through both current status and trajectory.

Action Steps:

Include appropriate historical trends for important KPIs
Assess both current position and direction of movement

11.27 Show Actual, Target and Variance Together

A number becomes more meaningful when its context is visible.

Showing actual performance alongside target and variance allows users to understand the performance position quickly.

Where appropriate, the baseline and previous period can also provide additional context.

Action Steps:

Present actual, target and variance together for key measures
Add historical context where it improves interpretation

11.28 Use Drill-Down Intelligently

Drill-down allows users to move from high-level performance to greater detail.

For example:

Corporate → Division → Service → Process → Individual Performance Area

Drill-down should answer useful questions.

It should not simply expose more data.

Action Steps:

Design drill-down paths around likely management questions
Stop the hierarchy where additional detail no longer supports decisions

11.29 Explain the Story Behind the Number

Performance numbers need interpretation.

A KPI may change because of workload, process changes, system problems, customer behaviour, capacity or other factors.

The performance professional should help explain what the number means while clearly distinguishing evidence from interpretation.

Action Steps:

Add concise commentary to significant performance movements
Separate confirmed causes from hypotheses and assumptions

11.30 Investigate Significant Variances

Not every variance requires the same response.

A small temporary fluctuation may require monitoring.

A large or persistent variance may require investigation.

Focus analytical effort where the performance signal is meaningful.

Action Steps:

Define criteria for significant variance
Prioritise investigation based on magnitude, persistence and organisational impact

11.31 Use Root-Cause Analysis

Root-cause analysis helps move from observation to understanding.

Useful techniques include:

Five Whys
Fishbone analysis
Pareto analysis
Process analysis
Fault analysis

The objective is not to assign blame.

It is to understand why the problem occurred and reduce the likelihood of recurrence.

Action Steps:

Select an appropriate root-cause technique for significant problems
Verify suspected causes with evidence before acting

11.32 Avoid Premature Conclusions

A performance change can have multiple explanations.

A correlation does not automatically demonstrate causation.

A sudden deterioration may coincide with a process change but further investigation may reveal another cause.

Good performance analysis is curious rather than hurried.

Action Steps:

Test alternative explanations before reaching conclusions
Clearly distinguish evidence, interpretation and assumption

11.33 Benchmark Carefully

Benchmarking compares performance or capability against an appropriate reference point.

Useful comparisons may include:

Historical performance
Internal organisational units
Comparable organisations
Industry information
Recognised good practice

However, differences in context can make apparently similar measures difficult to compare.

Action Steps:

Confirm that benchmark definitions and populations are genuinely comparable
Investigate contextual differences before interpreting gaps

11.34 Do Not Copy Another Organisation's KPIs Blindly

A KPI that works well elsewhere may not be appropriate for your organisation.

Different strategies, processes, customers, technologies, structures and objectives create different measurement requirements.

External examples should provide ideas rather than automatic answers.

Action Steps:

Use external KPIs as reference material rather than templates to copy
Test every proposed measure against your own objectives and performance questions

11.35 Connect KPIs to Objectives

Every important KPI should have a reason for existing.

The connection should be visible:

Objective → Measure → KPI → Target → Actual → Analysis → Action

If the link cannot be explained, the KPI should be challenged.

This prevents measurement from becoming disconnected from organisational purpose.

Action Steps:

Map every core KPI to one or more relevant objectives
Review KPIs that have no clear strategic or operational purpose

11.36 Connect Objectives to Action

Objectives should lead to activity and decisions.

If an objective is important but no initiative, process or management action supports it, the objective may exist only on paper.

Performance management becomes meaningful when objectives influence what the organisation actually does.

Action Steps:

Identify the initiatives and activities supporting important objectives
Monitor whether actions are contributing to expected outcomes

11.37 Track Actions to Completion

Performance reviews frequently produce actions.

The problem is that actions can disappear between meetings.

An action log should record:

Action
Owner
Due date
Status
Dependencies
Evidence of completion

Completion should be verified rather than assumed.

Action Steps:

Maintain a controlled performance action log
Review overdue and high-priority actions at performance forums

11.38 Measure Whether Actions Worked

Completing an action does not prove that the action solved the problem.

An action can be completed correctly and still produce little improvement.

Performance management should therefore measure effectiveness after implementation.

Action Steps:

Define the expected result for significant actions
Compare subsequent performance against the expected outcome

11.39 Do Not Create Reporting for Reporting's Sake

Reporting requires effort.

Data must be collected, processed, validated, analysed, formatted, reviewed and distributed.

Every report should therefore have a clear purpose.

If nobody uses a report to understand performance or make decisions, its continued existence should be questioned.

Action Steps:

Review the purpose and usage of recurring reports
Retire reports that no longer provide meaningful value

11.40 Automate Repetitive Work

Performance professionals should spend their time on analysis rather than repetitive manual administration wherever practical.

Automation can support:

Data collection
Calculations
Refreshes
Report generation
Alerts
Distribution
Data-quality checks

Automation should be controlled and tested.

Action Steps:

Identify repetitive performance activities suitable for automation
Validate automated outputs before relying on them operationally

11.41 Protect the Integrity of the Measurement System

A performance system must be trustworthy.

People should not manipulate measures to create a misleading appearance of success.

Potential problems include:

Changing definitions without governance
Selective reporting
Excluding difficult cases
Manipulating targets
Delaying records

Performance professionals should protect measurement integrity.

Action Steps:

Establish transparent definitions and governance controls
Investigate unexplained changes in measurement behaviour

11.42 Establish Strong Governance

Governance provides the structure through which performance is owned, reviewed and acted upon.

It should define:

Roles
Responsibilities
Decision rights
Escalation
KPI approval
Data ownership
Reporting standards
Review forums

Without governance, performance management can become inconsistent.

Action Steps:

Establish clear performance governance roles and decision rights
Document the rules governing KPI creation, review and retirement

11.43 Know the Difference Between Greenfield and Mature Environments

A greenfield environment is one where a new performance capability is being designed without having to preserve a large existing framework.

A mature environment already has processes, systems, KPIs, reports, stakeholders and historical practices.

The approach must therefore differ.

Greenfield work allows greater design freedom.

Mature environments require greater attention to transition, dependencies and organisational change.

Action Steps:

Assess whether the environment is greenfield, mature or somewhere between
Adapt the implementation approach to the existing level of capability

11.44 Do Not Assume Mature Means Effective

An organisation may have sophisticated dashboards, hundreds of KPIs and established reporting cycles while still struggling to make effective decisions.

Maturity should not be confused with effectiveness.

A mature system may still contain obsolete measures, poor data or weak accountability.

Always assess whether the system produces useful outcomes.

Action Steps:

Evaluate performance capability based on evidence rather than age or complexity
Test whether performance information actually influences decisions

11.45 Assess Performance Maturity

Performance maturity assessment helps organisations understand their current capability.

A useful model can examine:

Strategy
Governance
Leadership
Processes
Measurement
Data
Reporting
Technology
Culture

The objective is not simply to assign a level.

It is to identify capability gaps and determine what should improve next.

Action Steps:

Assess maturity across multiple performance dimensions
Convert identified gaps into prioritised improvement actions

11.46 Prioritise Before Transforming

Not every weakness needs immediate transformation.

Some problems may be minor.

Others may have significant consequences.

Prioritisation should consider factors such as importance, risk, effort, dependencies and expected improvement.

A focused improvement programme is often more manageable than attempting to change everything simultaneously.

Action Steps:

Rank improvement opportunities using transparent criteria
Sequence initiatives according to organisational need and capability

11.47 Design for Sustainability

A performance framework should continue working after the original project team has left.

This requires:

Clear ownership
Documented definitions
Repeatable processes
Appropriate technology
Governance
Training
Maintenance

A beautifully designed framework that cannot be maintained is not a successful performance solution.

Action Steps:

Design ownership and maintenance responsibilities before implementation
Ensure the organisation can operate the framework without excessive external support

11.48 Involve the People Who Use the Measures

Performance systems work better when the people who use them understand and contribute to their design.

Operational teams can explain:

What the data really means
Where process problems occur
Which measures are practical
Which indicators create unintended behaviour

Engagement improves both quality and adoption.

Action Steps:

Involve operational users during KPI and dashboard design
Test proposed measures with the people responsible for using them

11.49 Challenge Politely but Firmly

Performance professionals will sometimes encounter weak definitions, unreliable data, unrealistic targets or unsupported explanations.

The role requires professional challenge.

Challenge should be evidence-based rather than confrontational.

The objective is to improve the quality of organisational understanding.

Action Steps:

Challenge unsupported conclusions using evidence and clear questions
Focus discussions on performance facts, causes and possible actions

11.50 Make Performance Information Actionable

Information becomes valuable when it supports action.

A performance report should ideally make clear:

What happened?

Why does it matter?

What is causing it?

What should happen next?

Not every report needs to answer every question in equal detail but important exceptions should lead towards appropriate action.

Action Steps:

Link significant performance findings to explicit actions or decisions
Make ownership and next steps visible

11.51 Keep Improving the Measurement System

Performance measurement itself requires continuous improvement.

Strategies change.

Processes change.

Technology changes.

Customer expectations change.

Organisational structures change.

Measures that were appropriate previously may become less relevant.

The measurement system should therefore be periodically reviewed.

Action Steps:

Establish a regular review of the performance framework
Update measures when organisational needs or conditions change

11.52 Retire Measures That No Longer Matter

Removing a KPI can be as important as creating one.

An obsolete KPI creates unnecessary reporting effort and can distract attention from more important measures.

Possible reasons for retirement include:

Objective completed
Strategy changed
Measure duplicated
Data source retired
KPI no longer influences decisions

Measurement systems should have a deliberate retirement process.

Action Steps:

Review KPIs periodically against current objectives
Retire measures that no longer provide meaningful information

11.53 Think Like an Analyst and a Manager

An analyst asks:

What does the evidence show?

A manager asks:

What should we do about it?

Effective performance professionals need both perspectives.

Analysis without action can become academic.

Action without analysis can become poorly informed.

The strongest performance capability connects evidence with practical management decisions.

Action Steps:

Analyse performance rigorously before recommending action
Consider the management decision that the analysis needs to support

11.54 Think End-to-End

Performance rarely exists inside one isolated department.

Customer experience may depend on several processes.

Service quality may depend on technology, people and suppliers.

Project outcomes may depend on multiple organisational capabilities.

Thinking end-to-end helps reveal dependencies and prevents local optimisation from damaging overall performance.

Action Steps:

Map important performance chains across organisational boundaries
Investigate dependencies between teams, processes, systems and suppliers

11.55 Always Ask: “So What?”

This may be the most useful question in performance management.

A KPI changed.

So what?

A target was missed.

So what?

A dashboard shows a trend.

So what?

A new analysis identifies a correlation.

So what?

The question forces the performance professional to move beyond information towards significance and action.

It helps distinguish interesting information from useful information.

It also provides a simple test for almost every part of the performance system.

Why does this KPI matter?

Why does this variance matter?

Why does this trend matter?

Why does this report matter?

Why does this analysis matter?

What decision should follow?

The "So What?" test keeps performance management connected to organisational purpose.

Action Steps:

Ask “So what?” whenever a performance finding is presented
Continue until the significance, decision or required action is clear

11.56 The Complete Performance Professional Mindset

The 55 tips in this chapter can be condensed into a practical philosophy.

Start with purpose.

Understand the strategy.

Understand the operating model.

Identify the real questions.

Define meaningful objectives.

Select appropriate measures.

Create reliable KPIs.

Establish trustworthy data.

Analyse performance carefully.

Explain what the evidence means.

Challenge unsupported conclusions.

Connect information to decisions.

Connect decisions to actions.

Measure whether actions worked.

Improve the measurement system continuously.

The complete performance management cycle can therefore be expressed as:

Purpose → Strategy → Objectives → Questions → Measures → KPIs → Data → Analysis → Insight → Decision → Action → Outcome → Learning → Improvement

The performance professional sits across this entire chain.

The role is not simply to measure performance.

It is to help the organisation understand performance.

It is not simply to identify problems.

It is to help determine why they occur.

It is not simply to produce information.

It is to turn information into insight.

It is not simply to recommend action.

It is to help establish whether action produced the intended result.

And it is not simply to maintain a performance framework.

It is to ensure that the framework continues to support organisational learning and improvement.

The strongest performance professionals combine analytical discipline with practical judgement.

They understand data without becoming trapped by data.

They understand strategy without losing sight of operational reality.

They understand technology without assuming technology solves every problem.

They understand measurement without confusing measurement with performance itself.

Most importantly, they continually connect information to purpose.

That is the essence of effective corporate performance management.

This article was driven, managed and checked by the Author (drafted by AI).

#Musab #YouNeedMusab #HireTheBest #OpenToWork #Consultant #Expert #Available

Musab @ Work!