↑
← All articles

Operational delivery

Give each metric a decision it can change.

Connect every important measure to a named decision, an accountable owner and a practical response when it moves.

A hypothetical operations team opens its weekly dashboard and sees that response time has worsened for the third week. The chart is clear. The meeting still ends without a decision because nobody has agreed what the measure should change. A useful metric does more than describe the business. It gives an authorised person enough context to choose a response. Before adding another chart, define the decision the measure is meant to support.

Start with the decision, not the data

Write the practical question first. It might be whether to add temporary capacity, change a service promise, investigate a process step or leave the current plan in place. Then identify the smallest set of measures needed to answer it.

This keeps the dashboard focused on action rather than availability. A value can be accurate and still be unhelpful if the team cannot explain why it matters, what choice it informs or who is authorised to make that choice.

Define the point that deserves attention

Agree what kind of movement should prompt a review. Use a meaningful condition rather than colouring every small variation red or green. The condition might combine scale, duration and customer impact: for example, a response time outside the agreed range for two consecutive weeks, affecting a particular service group.

Record the comparison behind the condition. Seasonal patterns, a changed definition or an incomplete data feed can alter the meaning of a result. The owner should be able to see whether the measure is comparable before treating it as evidence for action.

  • What decision could this measure change?
  • Which movement should trigger a review?
  • Who checks the context and data quality?
  • Who can approve the response?

Put the response beside the signal

When a measure crosses its agreed condition, show the owner, review date and next step beside it. That next step may be an investigation rather than an immediate operational change. Make the distinction visible so a warning is not mistaken for a completed decision.

In the hypothetical response-time example, the service owner might compare demand, staffing and the age of open work before proposing a temporary capacity change. The dashboard should link that analysis to the decision record rather than leave the meeting to reconstruct it from memory.

Retire measures that no longer earn attention

Review measures periodically. If nobody uses one to make a decision, decide whether it supports a regulatory, contractual or operational need that should be stated explicitly. Otherwise, remove it from the main view or move it to supporting analysis.

Also check whether the measure creates the behaviour you intended. A faster response is not helpful if work is closed prematurely or customers must contact you again. Pair speed with a suitable quality or outcome check where the decision could shift effort in the wrong direction.

Rethink's ongoing senior advice, scoped by agreement, can help turn reporting into clearer operational choices and follow-through.

Discuss ongoing senior advice →

Work with Rethink

Discuss your
project.

Talk to Rethink