Five stages, in this order, every time.
Why we do it this way
The floor knows where the opportunity is long before the report does.
A report gives you the number. It does not tell you that one district manager has built a Monday call the rest of the region should copy, that eleven stores found a better reset than the planogram intended, or that three assistant managers are ready for more than they have been given. That is where the next gain is, and the people doing the work can usually point straight at it.
So we start on the floor. Every engagement begins with the operator's read, not the deck. The analytics come second, and they get built to answer what the floor already told us.
The sequence is the method, and the order is what makes the gain hold. Diagnosis earns the right to announce anything.
Weeks on the floor tracing every miss to its operational root, before a single change is announced. We talk to the people doing the work, not just the people reporting on it.
Leadership almost always knows the symptom already. The value is in tracing it to the behavior underneath, and that work only happens in stores.Reporting gets rebuilt around the two or three operational drivers the diagnosis surfaced, with store, district, region, and executive views that agree with each other. Power BI, Kronos, Workday, SAP, Salesforce, and hard Excel modeling, used in whatever combination the business already runs on.
There is a difference between a dashboard and a decision. The test of a good dashboard is whether a store manager changes what they do on Tuesday because of it.The weekly rhythm that makes a fix stick: what gets reviewed, by whom, in what order, and what happens when it slips. Communication, recognition, and accountability are designed as a system, not left to personality.
Recognition is engineered, not improvised. People repeat what gets celebrated, so we make celebration specific and public.Anything a leader does the same way every week becomes tooling: performance communication, financial review, investigation documentation. AI carries the drafting and the pattern-spotting. People keep every decision that affects a person's job.
Measure first, workflow second, software last. The pilots that stick are the ones with a named owner and a workflow that existed before the software did.The team runs it without us, and we prove that before the engagement closes. The goal is an operation that keeps climbing on its own strength, with the credit sitting where it belongs.
The measure is simple: what still works ninety days after we go.