Give the room one KPI pack, with a forecast on the same number
The monthly pack is assembled by hand from three extracts and a side spreadsheet. The same KPI means different things in finance, operations and the product team. The forecast lives somewhere else, exceptions arrive as Slack messages, and the meeting spends its time debating the number instead of deciding what to do. Nobody owns the definition, so every cycle starts again.
Sit with the people who use the pack, not only the people who produce it. Agree metric contracts — definition, grain, owner and quality rule — for the measures the room will actually use. Automate the operating view from trusted data, put a short forecast and exception list on the same grain, and attach a named review cadence so challenge and next action have a place to live.
- Decision map and KPI / metric contracts
- Automated operating pack from the contracted grain
- Forecast and exception view on the same number
- Named review cadence, owners and next-action rule
The recurring discussion starts from one owned number. Exceptions and a next action are explicit, and the forecast is no longer a separate artefact the room has to reconcile.