Before Standardising a Successful Site, Identify What Its Team Is Compensating For
The highest-performing location becomes the model for the rest of the group. Its routines are documented, its manager presents at the away day and other sites are told to adopt the same approach. Then performance fails to travel.
One possible explanation is that leadership copied the visible routine without understanding the invisible compensation behind it.
Success can contain an unsustainable workaround
A strong manager may spend evenings reconciling conflicting systems. An experienced employee may remember information that never reaches the handover. A team may preserve service by routinely absorbing work the rota did not anticipate.
The customer sees a dependable experience. The organisation sees a successful site. Neither view reveals the full cost unless someone asks how the result is achieved.
Do not discredit the team’s skill. Their ingenuity may be exactly what kept the business working. The next task is to distinguish useful judgement from a burden that should be removed.
Observe the difficult day
A carefully prepared site visit can show the process at its best. Spend time with the team during a normal demanding period and ask what changes when staffing, demand or resources vary.
Follow the information as well as the activity. Where do employees obtain the facts they need? What do they check twice? Which decisions wait for one person? What work happens outside the formal process?
Compare the documented method with the actual method. The gap may reveal obsolete instructions, an unnecessarily awkward system or a local improvement worth adopting. Each calls for a different response.
Transfer the conditions for performance
If a practice depends on a particular skill, teach and assess that skill. If it depends on access to information, provide that access. If it succeeds because the site has a different customer mix, identify where the method is relevant rather than imposing it universally.
A useful transfer brief explains the intended outcome, essential conditions, permitted adaptations and evidence of success. It should also name what the receiving site will stop doing to make room for the change.
Test with one other location before presenting the practice as a group standard. Observe whether the result improves and whether the work becomes easier or merely moves elsewhere.
Reward the discovery, not the hero dependency
When a workaround becomes visible, avoid penalising the person who revealed it. Otherwise the organisation teaches staff to conceal the operational truth.
Recognise the contribution, remove the unnecessary burden and capture the learning. A successful site should become a source of better system design, not an excuse to expect everyone else to work indefinitely beyond the plan.
Q Branch’s people and operations approach examines how capability and working conditions combine. Before copying your strongest location, ask its team what they do that the official process does not acknowledge. The answer may explain both its success and the risk in trying to reproduce it unchanged.
Representative photograph: Unsplash.






Comments