Improving Operational Performance Through Better Planning

Operational performance improves when plans connect strategic priorities with the work people do every day. A plan should help an organisation decide what matters, allocate resources, respond to changing demand and identify problems early. Without that connection, planning can become a reporting exercise rather than a practical tool for better decisions.

For organisations in England, the right approach depends on their sector, size, operating model and obligations. There is no single planning method that suits every business. The principles below provide a useful starting point for reviewing and strengthening an existing approach.

Start with clear priorities

Planning is more effective when leaders agree on a small number of operational priorities. These might include improving delivery reliability, reducing avoidable rework, managing costs or responding more consistently to customer needs. Priorities should be specific enough to guide decisions, but not so numerous that teams lose focus.

For each priority, clarify:

• The outcome the organisation wants to achieve
• The teams and processes that influence it
• The resources or decisions required
• How progress will be assessed
• Who is accountable for reviewing results

This makes it easier to identify conflicting objectives. For example, a team asked to increase output while also reducing overtime may need clearer assumptions about demand, capacity and service expectations.

Build plans around realistic demand and capacity

A plan is only useful if it reflects what the organisation can deliver. Compare expected demand with available people, skills, equipment, time and budget. Make assumptions visible, including uncertainty about volumes, delivery dates or resource availability.

Where demand is difficult to predict, use scenarios rather than relying on a single forecast. A core plan can set out the expected course of action, while alternative scenarios describe how the organisation might respond if conditions change. The aim is not to predict every disruption, but to agree in advance which signals would prompt a review and what options are available.

Capacity planning should also account for work that is easy to overlook, such as training, maintenance, approvals and improvement activity. If these are excluded, teams may appear to have more capacity than they actually do.

Connect plans to day-to-day processes

Operational plans should identify how work moves through the organisation, where decisions are made and where delays or errors can arise. Mapping a process from the perspective of the people who perform and receive the work can reveal unnecessary handovers, unclear responsibilities or repeated checks.

Involve frontline teams when reviewing processes. They can often explain why a procedure is difficult to follow, which exceptions occur regularly and what information is missing at key decision points. Changes should be tested on a manageable scale before being applied more widely, with clear criteria for deciding whether the change has helped.

Use measures that support decisions

Measures should help managers understand performance and choose an appropriate response. A balanced set may include indicators of outcomes, such as delivery or service quality, alongside operational measures that show how work is progressing.

For each measure, define what it means, where the information comes from, how often it is reviewed and who is responsible for acting on it. Avoid collecting data simply because it is available. Too many measures can obscure the issues that matter most, while inconsistent definitions can lead to misleading comparisons.

A measure should prompt a useful question. If performance changes, managers need to understand whether the cause is a shift in demand, a process issue, a resource constraint or another factor. Reviewing the context alongside the numbers helps avoid treating symptoms as causes.

Establish a practical review rhythm

Planning should be reviewed often enough to support timely decisions, but the frequency should suit the nature of the work. Regular operational reviews can focus on immediate delivery, emerging risks and decisions that require action. Longer-term reviews can consider whether priorities, assumptions and resource choices remain appropriate.

A productive review is not just a presentation of results. It should establish:

1. What was expected to happen
2. What actually happened
3. What explains the difference
4. What decision or action is needed
5. Who will take responsibility and by when

Keeping an action log and revisiting previous decisions helps make review meetings useful. Where an issue cannot be resolved at the current level, the route for escalation should be clear.

Make planning adaptable

Plans need enough stability to coordinate work and enough flexibility to respond to change. When assumptions shift, teams should know which parts of the plan can be adjusted and which require senior approval. This reduces confusion and makes it less likely that different teams will act on conflicting versions of the plan.

Documenting key assumptions and decisions also supports continuity when responsibilities change. It gives teams a shared reference point and makes it easier to explain why priorities or resources were revised.

Turn improvement into an ongoing practice

Better planning is not a one-off exercise. Organisations should periodically examine whether their planning process leads to clearer priorities, more realistic commitments and faster responses to operational problems. Feedback from managers and frontline staff can show where plans are useful and where they create unnecessary work.

Meridian Strategy Group can help organisations assess how planning connects to operational delivery, clarify decision-making responsibilities and develop a review process suited to their needs. The objective is not to produce more planning documents, but to make planning a practical part of improving performance.