Insights · Workplace guidance · 5 minute read

When consistency earns trust and when it protects mediocrity

How to keep the promises customers rely on while giving employees the authority to challenge a routine, test a better method, and stop a bad idea.

By Vitaver Staffing · Published

A field service company promises to call each customer before a technician arrives. A dispatcher keeps that promise for ten years. Customers trust her. The company also requires her to copy every confirmed appointment from the scheduling system onto a whiteboard. She does that faithfully for ten years, too. One morning she asks, “Who would miss the board if I stopped updating it?” Her manager realizes he has praised both habits as examples of the same virtue. Only one is a promise to a customer. The other needs a reason to exist.

There is a grain of truth in the jab that consistency is the last refuge of the mediocre. Repeat an activity long enough and “I followed the procedure” can become a defense against almost any result. But repetition is also how a craftsperson gets good and a customer learns whom to trust. The management question is precise: What are people entitled to count on, and who has the authority to try a better way of delivering it?

Find out what the old routine knows

The dispatcher wants to take down the board. Before approving that, the manager asks her to watch a shift change. At four o’clock the outgoing dispatcher circles two appointments on the board. Both customers must unlock a gate. The incoming dispatcher sees the circles and makes the calls. The scheduling system has the addresses and appointment times, but the gate instructions are buried in separate notes. The old routine carries knowledge its defenders have never explained and its critics have never seen.

That discovery improves the proposal. The team can remove a duplicate entry if the receiving dispatcher can still identify the calls that matter. Asking a veteran what would break gives experience its due. Asking for a demonstration gives a newcomer a fair chance to challenge a tradition. Neither person wins the argument by seniority.

Give people authority proportionate to the risk

A manager who demands approval for every small variation teaches employees to wait. A manager who says “break the rules” and walks away leaves employees to guess whose promises they can spend. Make the boundary explicit. The dispatcher can rearrange her own preparation steps today. Changing how two shifts hand over work needs agreement from both shift leads. Dropping a customer notification or bypassing a required safety check is outside her authority. An employee who thinks a safeguard is obsolete can challenge it with the person accountable for it while the safeguard remains in effect.

Now give the dispatcher an actual decision, a little time and a defined downside. For the next three afternoon handoffs, she may use a flagged list from the scheduling system on one route. The shift lead will check it against the board before dispatch. The prediction is that the incoming dispatcher can find every gate call and that staff spend less time entering the same information twice. Record the usual handoff time first. If either version misses a gate instruction, use the verified list and investigate that day. A short period of duplicate work buys a comparison; give it an end date so the experiment does not become one more permanent chore. This resembles the Institute for Healthcare Improvement’s small-scale test method, which asks teams to make a prediction and compare it with what actually happens. IHI test worksheet.

What the leader does after a miss sets the culture

Imagine the second handoff fails. A relief dispatcher cannot see the flag because her account has different permissions. The check catches it before a driver leaves. The manager’s first question matters. “Who authorized this?” would be a curious response from the person who authorized it. A better one is, “Which assumption did we get wrong, and does anyone else work with those permissions?” Thank the relief dispatcher for reporting the problem. Let the proposer explain what happened. Decide whether a permissions fix and another test are worth the effort.

Be equally clear about accountability. A candid report of a failed prediction deserves a different response from concealing a missed call or expanding the trial beyond the agreed route. Employees watch which behavior earns praise, which draws correction and whether the same rules apply to the manager’s favorite idea. A leader who wants calculated risk has to accept a disappointing result when employees exercised sound judgment within the agreed limits.

Be willing to keep the old way, too

On review day, let the person receiving the handoff demonstrate the result. If the flagged list works for regular and relief staff and saves enough effort to justify the change, the operations manager can adopt it, teach it and retire the board. If the board remains faster and more reliable, keep it and record why. The dispatcher still made a contribution: the company now knows which detail protects the customer and can teach it to the next hire. A quota for new ideas or discarded procedures would give the team a reason to hide that finding.

This draws on the Mission First and Signal vs. Noise practices from The Vitaver Playbook. At your next review, pick one routine people defend with “we always do it this way.” Ask the newest employee what it costs, the most experienced employee what it protects, and the person receiving the work what must come through intact. Then make a decision. Trust grows when employees can predict that leadership will keep its word, listen to inconvenient evidence and change its own mind when the evidence warrants it.

Questions for discussion

  1. Which routine on your team protects something a newcomer might overlook?
  2. Which experiment could an employee authorize without asking you first?
← All Insights