Without a baseline captured before anything changes, every later number is contested. This is the cheapest thirty days in the engagement and the one most often compressed.
Ontology lock. Teams want to keep refining indicators. Locked and imperfect beats open and elegant — the learning loop corrects it from here.
Not the readiness report. The first time a frontline leader acts on a nudge, sees it work, and tells another leader without being asked.
Scale, stop, or re-scope — on the floor’s own numbers, with finance in the room. A roadmap built on anything softer does not survive the next budget cycle.
Data access from day one, agreed in writing. It is the one thing that determines whether 120 days is enough. Everything else — tooling, stack, model choice — is negotiable and swappable. This is not.
Owns the programs the intelligence reinforces, and curates the ontology once it is built.
Carries the assessment surface and the people-side mandate across functions.
Owns the outcome being measured. Process director and associate director run the weekly loop.
Technology hosts and secures; finance validates the number at the day-120 read-out.