Store-First, Why the Shop Floor Knows Before the Boardroom Does

There's a particular kind of meeting I've sat through more times than I can count, and I suspect you have too. Somebody senior stands up with a plan for a piece of technology that's going to transform the business. There are diagrams. There's a rollout timetable. There's usually a phrase like "estate-wide from day one," said with real conviction, as though conviction alone has ever been enough to make three hundred tired shift managers change how they work on a Friday night.

I used to sit in those meetings and nod along, because that's what you did. It took me an embarrassingly long time to notice the pattern hiding underneath all of them. The plans I trusted most were the ones that started in a single store, with a single manager, who had a real problem and got a real answer to it within days rather than quarters. I think about this now as something close to a law, even though it sounds almost too simple to deserve the word.

A tool that helps somebody get through their shift more easily has a much better chance of being used without constant reminders. If it doesn't help, executive sponsorship can only take it so far. Stores don't adopt technology because leadership asked nicely. They adopt technology because it makes Tuesday less painful than it was on Monday.

So the first question I now ask, before anything else, is deliberately small. Not "how do we roll this out across the estate," but "will one store notice the difference this week?" If the honest answer is no, I stop and rethink, because everything that follows a weak first answer tends to be weak as well.

There's a kind of humility in this that I didn't expect to enjoy as much as I do. Building for one store first means accepting that you might be wrong about the whole thing before you've spent very much finding out. It means a manager can look at what you've built and say, quite bluntly, "that's not how we do it here," and instead of that being a setback, it's the entire point of doing it this way. You'd rather hear it in week one from one store than in month nine from thirty of them.

What I've noticed, again and again, is that the stores themselves become the best advocates you could ever hope for, and they do it without being asked. A tool that helps starts travelling on its own. A manager mentions it to a colleague at a regional call.

Someone asks if their site can have it too. That request, arriving unprompted, tells you more about whether something is working than any dashboard ever will. Executive endorsement should follow evidence, not replace it. It's not that leadership doesn't matter. It matters enormously, later, when you need air cover to scale something that's already proven itself where it counts. But leadership belief is not the same as operational truth, and confusing the two is, in my experience, where most well-intentioned transformation programmes start to go wrong long before anyone notices. So when people ask me where these builds usually begin, the honest answer disappoints some of them slightly. It begins on a shop floor, with one tired person, and a question that has nothing to do with technology at all, what would make your day easier tomorrow?

There is another reason I like starting in one store. It forces the conversation away from averages. Estate-wide data is useful, but averages have a wonderful ability to smooth away the exact bit of reality you need to understand. In one restaurant you can stand beside the manager, watch the workaround happen and ask why. You can see the queue form, hear the apology and notice the bit of paper that never appears in the process map.

That proximity changes the tone of the work. People are less likely to give you the answer they think head office wants when you are standing beside them at the moment the problem occurs. They show you the shortcut. They tell you which field they ignore. They point at the thing everyone knows is broken. I have learned more from those slightly embarrassed 'we actually do it like this' conversations than from most formal requirements sessions I have attended.