Quality Improvement Zone

A measurement plan sets out what will be measured, why it is being measured, how data will be collected and how results will be displayed.

A measurement plan acts as a shared reference for the project team and helps create a reliable measurement system. By ensuring everyone collects, analyses and interprets data in a consistent way, it becomes easier to understand whether changes are leading to improvement.

A measurement plan should typically:

• contain a manageable family of measures, usually around 3-8 measures
• identify whether each measure is an outcome, process or balancing measure
• clearly describe the purpose of each measure within the project
• include clear operational definitions explaining exactly how each measure will be calculated
• outline how, when and by whom data will be collected
• specify how data will be analysed and displayed, for example using run charts or SPC charts

The purpose of measurement in improvement is not simply to report performance, but to support learning and guide decision-making. A measurement plan helps teams collect useful data consistently so they can understand whether changes are leading to improvement.

A measurement plan can help you:

• develop a shared understanding of project measures
• collect data consistently over time and across team members
• reduce variation introduced by inconsistent measurement methods
• support testing, implementation and decision-making
• understand whether changes are resulting in improvement
• communicate measurement approaches clearly to stakeholders

Without clear measurement plans, different people may collect or interpret data differently, making it difficult to determine whether changes in performance reflect genuine improvement or differences in measurement.

A measurement plan should be developed early in an improvement project and reviewed as learning emerges. The goal is to collect enough information to support learning and decision-making without creating unnecessary measurement burden.

1. Clarify the improvement aim

Start by reviewing your improvement aim. Consider what success would look like and how you will know whether improvement has occurred.

2. Identify outcome measures

Outcome measures tell you whether the project is achieving its aim and reflect the performance of the system from the perspective of those who experience it.

Ask yourself:

• What are we ultimately trying to improve?
• How will we know whether we have achieved our aim?

3. Identify process measures

Use your driver diagram and understanding of the system to identify measures that will tell you whether key processes are being carried out as intended.

Ask yourself:

• What needs to happen reliably to achieve the aim?
• How will we know whether the changes are occurring as intended?

4. Identify balancing measures

Consider any unintended consequences that could arise from the improvement work and identify measures to monitor these.

Ask yourself:

• Could the changes create problems elsewhere in the system?
• What would we need to monitor to identify this?

5. Develop operational definitions

For each measure, create a clear operational definition that is understood by everyone involved in data collection and analysis. This should include:

• exactly what is being measured
• how the measure is calculated
• definitions of key terms
• numerator and denominator where applicable
• inclusion and exclusion criteria

Clear operational definitions help ensure measures are collected consistently and reduce variation introduced by differing interpretations.

6. Plan data collection

Decide:

• how data will be collected
• who will collect it
• how often it will be collected
• whether sampling will be used
• where data will be stored

Consider at this stage how the data will be analysed so that all necessary information is collected in the correct format.

7. Decide how data will be displayed

For each measure, decide how results will be analysed and displayed. In most improvement projects this will involve:

• run charts
• SPC charts

Planning this in advance helps ensure data is collected in a way that supports meaningful analysis and learning.

8. Review and use the plan

Share the completed measurement plan with the wider project team and use it as an ongoing reference document. Review it regularly to ensure measures remain relevant and data continues to be collected consistently.

As the project develops, the measurement plan may need to be updated to reflect new learning or changes in the improvement approach.

Tips for effective measurement

• Focus on collecting data that will support learning and decision-making
• Keep measurement proportionate and avoid collecting data that is unlikely to be used
• Measure what is useful, not simply what is easy to collect
• Collecting more data does not necessarily lead to more learning. Focus on the minimum amount of data needed to inform improvement
• Revisit measures regularly as your understanding of the system evolves