FactoryWhere the number lives / Leadership and planning
Leadership and planning
You ask a question and wait a week. Two people in the room give two numbers for the same thing and both are right.
Days to answer a management question. Agreed in writing, before anything is built.
What this looks like from the inside.
If three or more of these are true, there is almost certainly a number here worth chasing.
- 01The customer count is different in every system and nobody will defend one of them.
- 02Board packs are assembled by hand from four sources over several days.
- 03A definition changes and nothing computed under the old one remains traceable.
- 04Regional numbers cannot be compared because each region computes them differently.
- 05Nobody can answer a follow-up question without going away and coming back.
The number we would agree first.
Days from a management question to an answer everyone accepts, on one versioned set of definitions. Or the number of reported metrics with a written definition and a named owner.
It sounds soft and is not. It is the number that decides whether every other number in the business can be trusted.
An entity resolution sample across two of your systems, showing the duplicate customer count and what it has been hiding.
5 plays that move it.
Each is built from the same nine patterns and reads the same memory. The first is priced as a pilot. Every one after it runs on a memory that already exists.
- ManagementManagement cockpit
- ManagementDefinitions layer
- ManagementEntity resolution and customer master
- ManagementForecast against actual
- ManagementBoard pack assembly
A number in this function we have already moved.
Success story / Regional distributionSingapore ran the region. It could not see two of the countries it ran.
A regional headquarters with distributors in six markets reported one number to the group and had confidence in three of them. The two largest gaps were the two fastest-growing markets.
Read the success story