The Sovereign Restaurant — Blog Series - Post 4: The 70/30 Rule

I want you to imagine the Tuesday morning of a good Area Manager. Not a bad one — a genuinely capable, experienced operator who knows their sites, knows their people, and has good instincts about what's working and what isn't.

They are at their desk by 7:30. By 9am they have pulled last week's labour report for six sites, identified three variances they need to investigate, sent a message to the two GMs who haven't submitted their weekly summaries, started reconciling this Tuesday's opening numbers against last Tuesday's, and begun building the slide they need for Thursday's ops review.

They have not yet spoken to a single human being about the actual state of their business.

By 11am they are in a call reconciling a food cost discrepancy that turns out to be a data entry error. By 2pm they are in a car driving to the site with the worst variance, which they could have identified at 8am if the data had surfaced it automatically rather than requiring two hours of manual retrieval to locate.

The coaching conversation they need to have with the GM of that site — the one about the kitchen culture that is technically hitting its numbers but quietly burning through people — happens at 4:30pm, forty-five minutes before they need to leave, when both parties are tired and the conversation gets half the attention it deserves.

This is not a failure of the Area Manager. It is the structural reality of managing multi-site operations in an industry that has never seriously invested in its information architecture. The data exists. It is in the POS, the scheduling tool, the supplier invoices, the waste logs. But it exists in formats that require a human to retrieve, reconcile, and repackage before it can be used.

That reconciliation work — the 70% — is consuming the majority of a highly experienced, highly paid person's working week. And it is the least valuable thing they do.

The 30% is the work that actually compounds. The coaching conversation. The culture read. The judgment call about the junior manager who is ready for more responsibility before anyone else has noticed. The honest conversation with a site that is performing adequately on paper and deteriorating in reality.

That work requires presence, relational authority, and the kind of contextual intelligence that no inference layer will replicate. It is also the work that retains teams, builds culture, and creates the operational resilience that shows up in performance over years rather than weeks.

The argument is simple: automate the retrieval and you get the 30% back.

But I want to be direct about what that actually means organisationally, because the clean version of this argument leaves something important out.

When you remove the 70%, you find out quickly who has the commercial intuition and who was using the retrieval work as a shield. The spreadsheets are not just inefficiency. For a meaningful number of Area Managers, they are a way of being visibly busy that defers the harder, more exposed work of actual performance leadership.

This is not a technology project with a change management workstream attached. It is, in part, an organisational reckoning. Some people in the Area Manager role will make the transition from report-runner to commercial leader. Some will not. That has HR implications that need to be planned for honestly before the system goes in, not managed reactively after it does.

The 30% is recoverable. Getting there is not painless.

Part four of the Sovereign Restaurant series. Full white paper available [here].