An operator described pulling numbers from the systems where the business actually worked and copying them into the software used for the weekly meeting.
Another leader questioned the measures themselves. When a number went off track, the team had little to discuss. Was it tracking something useful?
These are different responsibilities: maintaining reliable information and choosing information that helps the team make decisions. A useful operating system needs to support both.
For the COO, preparing a scorecard can involve gathering updates and resolving competing definitions. The number should help the team act or confirm that something important is on track.
Settle the source, calculation, update time and person responsible for each measure. For example, if one report counts “weekly sales” through Friday and another through Sunday, pick one and write it down. Make a missing update visible, so the team knows what it is still waiting for.
In Worker, the Scorecard sits in one place with the plan, goals, to-dos and issues. An AI worker can help prepare the weekly meeting and chase missing numbers before it starts. The team can then look into a meaningful change and decide who should respond.
At your next scorecard review, ask two questions about each number: how is it maintained, and what decision or condition does it inform? The answers may show a collection job to support, a definition to fix or a measure that belongs in another meeting. Then the meeting can begin with what the numbers mean for the business.
