Insights · Workplace guidance · 5 minute read

How fast should a team change when the business can’t wait?

Set the pace of change by weighing the cost of delay, testing the hardest handoff, and giving people room to learn while the business keeps running.

By Vitaver Staffing · Published

On Monday a support manager announces a new ticket system. On Tuesday she sends a revised escalation chart. On Wednesday a dashboard appears, ranking tickets by a different definition of urgency. By Friday an experienced technician has three versions of the instructions open and a customer waiting on the phone. He asks his supervisor to make a decision he used to make himself. From the manager’s desk, it looks as though he has lost initiative. From his desk, waiting is the only choice that won’t break somebody’s rule.

Should the business slow down for him? First find out what he is waiting for. More practice might help him learn a new screen. No amount of practice will resolve two contradictory instructions. A manager who calls both problems “resistance to change” will pick the wrong speed for both.

Give the deadline and the learning curve separate answers

Suppose the old ticket system goes offline at the end of the month. The company cannot postpone Friday’s shutdown by asking people how ready they feel. It can decide which changes must happen by Friday. Every shift must be able to receive an urgent ticket, name its owner and hand it to the next shift. The new dashboard and revised performance ratings can wait. The operations manager tells the team, “On Friday we change where tickets are recorded. Your escalation authority stays the same. I’ve withdrawn Tuesday’s chart. Here is the one instruction that applies.”

That last sentence does more for morale than a fifth message asking everyone to stay positive. It restores the technician’s ability to act. When introducing a change, name one responsibility people can put down. Retire an old report, cancel a low-value meeting or assign coverage while someone practices. If leadership keeps every old obligation and adds training on top, the price of the rollout comes out of somebody’s evening or a customer’s service.

Listen for what the change puts at risk for the person doing it

An experienced dispatcher may understand the new screen perfectly and still dread using it. Under the old system she knew how to recover a misrouted call. Under the new one, her first mistake may be visible to the whole department before she knows how to correct it. Another employee may be worried that the dashboard is a prelude to eliminating his role. A demonstration answers neither concern.

Ask privately, “Which part could you do on your own tomorrow? Where would you hesitate, and what do you think would happen if you got it wrong?” Give the dispatcher a practice case that goes wrong on purpose and let her recover it. Tell the other employee what has been decided about roles, what remains open, who decides and when he will hear more. If you do not know, say so and keep the appointment to update him. The UK Health and Safety Executive’s guidance on organizational change emphasizes timely explanations, consultation, training and a known timetable. Those are useful disciplines for a manager planning a rollout. HSE guidance on managing change.

Does the slowest learner set the pace?

Only when the next step depends on a task that person alone must perform and nobody else can safely cover it. Even then, the constraint is an uncovered responsibility. Labeling the employee “slow” tells you little. Suppose nine day-shift staff pass a demonstration, but the sole night dispatcher cannot transfer an urgent ticket to the on-call engineer. Ninety percent completion is a poor reason to go live unassisted at midnight. Pair the dispatcher with someone qualified, test the handoff together, and let the day shift proceed if its work can run independently. If the handoff still fails with an expert at the keyboard, fix the process.

The reverse mistake is to let the most enthusiastic user set everybody’s pace. A volunteer who designed the workflow and knows whom to call is a poor stand-in for someone using it alone on Saturday. Give an ordinary user a realistic case, include one exception, and watch whether the receiving person can pick up the work. The Institute for Healthcare Improvement describes testing changes on a small scale and under different conditions before making them permanent. The same reasoning helps a service team discover what its Friday demonstration missed. IHI guidance on implementing changes.

Make a decision the business can afford

At the first review, look at missed handoffs, repeat corrections, after-hours cleanup and the questions still waiting for a manager. Then ask one question the numbers won’t answer: “What are you doing by hand to make these results look normal?” A team can keep its dashboard green for a week by quietly carrying an unsustainable load. Thank the person who shows you the workaround and act on what it reveals.

This applies the Mission First practice from The Vitaver Playbook. A business sometimes cannot wait for universal confidence. It can still protect the customer, give people a fair chance to master the next task and refuse to waste their attention on three changes when only one is urgent. The leader’s job is to decide which one that is.

Questions for discussion

  1. Which part of the proposed change actually has a fixed deadline?
  2. What work could you stop so people can practice the critical handoff?
← All Insights