Quality drops every time the senior tech is off

The senior tech takes a week off. By day two, a quality check comes back wrong. By day three, a customer is asking questions. The team did not stop caring. They ran the check the way they remembered it, and each person's version was slightly different.

Pain: Quality drops every time the senior tech is off.

The check exists in someone's head. When that person is available, outcomes are consistent. When they are not, each team member runs their own version of it, and variation creeps in. This is Process Consistency Risk. It stays invisible right up until a key person is absent.

It is easy to diagnose as a people problem. It is not.

The team are not underperforming.

The process is under documented.

Fix: Make the check a checklist, not a person.

A documented checklist does not replace the senior tech's expertise. It captures it once and makes it transferable. The check runs the same way whether it is the senior tech, a new hire, or anyone else on the team. Quality stops being a function of availability and starts being a function of the process.

That is a significant shift.

It means holidays, sickness, and staff changes no longer carry quality risk.

It also means new team members can run the check correctly from day one, without needing to shadow the right person first.

If you want to understand how this type of risk connects to the wider picture of operational consistency in your business, our operational design approach is a good place to start.

Which quality check in your operation is a person, not a process?

This post is part of the Friday Fix series at Simpleris Insights. Each Friday, one operational problem and one concrete fix.