A really good quarter feels like a win. Results are high, participants satisfied, the statistics look good for the next report. The question rarely asked in the middle of the celebration is why it went so well that time, and whether it can be done again.
Without shared routines, the answer is often unclear. Maybe it was a particularly strong group of participants that period. Maybe it was one employee’s extra effort. Maybe it was several things that happened to coincide. If no one knows for sure, it becomes harder to judge what can actually be repeated, instead of just hoping for the same outcome again.
Shared routines mean the way of working doesn’t depend on who happens to be in the room. Every case is handled according to the same basic structure, regardless of which employee is driving it. That’s not the same as suppressing individual judgment. The core components of the way of working are standardized, while professional judgment and individual adaptation remain where they’re useful. The routine is a stable foundation that judgment can build on, rather than every employee inventing their own system from scratch.
A common scenario is an organization where the execution of one and the same step, for example how an assessment is done or how often follow-up happens, varies significantly between employees without anyone having decided it should be that way. No single variant is factually wrong, but without a shared minimum, it becomes hard to know which execution actually contributed to a given result. (What happens when one employee’s knowledge is never shared with the rest of the team is covered in [article 15].)
Building shared routines requires someone actively capturing what works with the best employees, and making it available to everyone else. It’s work that rarely feels urgent. There’s always something more pressing to deal with, a difficult case, a staffing issue, a report that’s due. The routine-building gets pushed back, again and again, until a key person leaves and the gap suddenly becomes costly.
The hard part isn’t understanding the value of shared routines. Most managers grasp it immediately when the question is put to them directly. The hard part is actually setting aside time to build them, in a day-to-day reality where everything else feels more important right now, and then keeping the routines alive year after year, not just during the first enthusiastic month.
The organizations that succeed are rarely the ones that once wrote their routines down in a document. They’re the ones that made following up on the routines a natural part of everyday work, with someone carrying responsibility for making sure they’re actually followed, long after the document was finished. Getting there on your own, in the middle of everything else already competing for time, is harder than it sounds.
Many managers hesitate to build shared routines out of fear it will stifle what makes the best employees good. That’s an understandable concern, but it often rests on a misunderstanding. A shared foundation doesn’t remove room for experience and judgment. It ensures everyone else also gets a chance to build their own skill from the same stable starting point, instead of everyone having to reinvent everything from scratch.
A good way to start is not trying to capture everything at once. Choose one specific, defined step in the work, the one that varies most between employees today, and work through a simple model for just that step: define what should be shared, apply it day to day, follow up that it actually happens, learn from what works and adjust what doesn’t. Once that routine is in place, move on to the next step. One big, all-encompassing routine document written all at once risks becoming too heavy for anyone to keep alive in practice.
Standardize what needs to be shared. At the same time, make clear where professional judgment should be used.
It’s also an investment that only pays off afterward. The period spent building the routines costs time that could have gone elsewhere, while the payoff, more stable results and less vulnerability, shows most clearly much later, often only the day a key person actually leaves and the organization still manages without losing momentum.
There’s also a kind of reassurance in shared routines that’s rarely highlighted. Participants meet a more even quality regardless of which employee they get, which in turn strengthens trust in the whole organization, not just in individual go-getters. (How a structured onboarding gets new employees into the shared way of working faster is covered in [article 13].)