Shared metrics need shared operating definitions

A shared metric is an agreement about the work. When teams use the same word for different operating conditions, combining their figures in a dashboard can create an appearance of alignment while preserving the disagreement underneath. The enterprise needs a definition people can apply consistently at the point of decision.

Material readiness is a useful example. Procurement may consider an item secured when a supplier confirms delivery. A warehouse may report it available after receipt. Production may need it identified, inspected, correctly configured, and present at the required location. Each view serves a purpose, but the views describe different states.

Define the condition behind the number

I would begin by identifying the decision the measure supports. If a team is deciding whether to release work, readiness should reflect the conditions needed to begin that work responsibly. The definition must be agreed by the functions that create and consume the information. Otherwise, one team will continue to translate another team’s number before it can act.

The measure also needs a clear unit and time boundary. Does it describe individual items, complete kits, or work orders? Is it a current state or a forecast for a future date? Which version of the requirement is being assessed? These details can change the meaning of a result without changing its label.

Consider an illustrative kit containing several items. A high percentage of available items can conceal one missing component that prevents the build. An item-level measure may still be useful for analysing shortages, while a complete-kit measure supports a different decision. The organisation should preserve both meanings rather than force one number to answer every question.

Assign ownership for the transitions

A definition becomes operational when someone is responsible for recording each change in state. Receipt, inspection, release, allocation, and movement may involve different roles and systems. The team needs to know which record governs the decision and how disagreements are corrected. Information ownership is part of the process design.

Timing matters as well. A physically completed transaction that remains unrecorded can leave the next team acting on an outdated view. The reporting discussion should therefore examine the delay between an event and its representation in the shared record. A polished dashboard cannot compensate for a process that updates the underlying facts unpredictably.

The metric should lead to a defined response. A readiness gap may require a revised plan, an authorised substitution, a supplier action, or a decision to defer work. The review needs the people who can make those choices. Otherwise, the meeting produces another request for updates while the constraint remains unchanged.

Use disagreement as design evidence

When functions dispute a number, the first task is to identify the basis of the disagreement. They may be using different definitions, timing, scope, or records. Resolving that issue improves the measurement system. Treating every dispute as reluctance to be accountable can discourage the information the enterprise needs to correct its view.

I would pilot a shared definition in one operating area and review real exceptions. Ask whether the measure helps teams anticipate problems and make better commitments. Refine the definition where it creates confusion, while controlling changes so that comparisons remain understandable over time.

Shared measures are useful when they give interdependent teams a common basis for action. The leadership work is to establish that agreement and maintain the process behind it. The dashboard then becomes a representation of a coherent operating decision.