Matvey Zakharov
RU

One employee is “irreplaceable”

Critical processes or knowledge exist with one person only: nobody backs them up, no standard is written down, and nobody else can see their state. The company is vulnerable to resignation, illness, or poor performance.

Pull out the senior operator

The critical processes of production, 12 in all, as a tower; each block names who runs it and who backs him up. Pull out operator 6: before, the blocks that rest on him alone fall (7); after, every block has a backup and the tower stands.

Before
CuttingOperator 7backup: 9
LaminationOperator 8backup: 10
PackingOperator 10backup: 11
Ink stockOperator 9backup: 7
Machine scheduleOperator 11backup: 8
Fell: 7
Machine setupno backup
Colour profilesno backup
Paper ordersno backup
Pricing complex jobsno backup
Machine servicingno backup
Special materialsno backup
Complex filesno backup
After
Machine setupOperator 6backup: 8
CuttingOperator 7backup: 9
Colour profilesOperator 6backup: 9
LaminationOperator 8backup: 10
Paper ordersOperator 6backup: 7
PackingOperator 10backup: 11
Pricing complex jobsOperator 6backup: 8
Ink stockOperator 9backup: 7
Machine servicingOperator 6backup: 10
Machine scheduleOperator 11backup: 8
Special materialsOperator 6backup: 9
Complex filesOperator 6backup: 7

The baton while he was away

Orders that needed one of his processes while he was away this year, and how many waited until he was back. Waited: 75 of 75 before, 0 after.

Before
Vacation, working days: 10
Operator 6nobody
Nobody to take the baton. Orders that waited for him: 54 of 54
Illness, working days: 4
Operator 6nobody
Nobody to take the baton. Orders that waited for him: 21 of 21
After
Vacation, working days: 10
Operator 6backups
The backups took the baton. Orders: 54; waited for him: 0
Illness, working days: 4
Operator 6backups
The backups took the baton. Orders: 21; waited for him: 0
SOLUTION

Key-person dependency reduction

  1. From your task records and messengers, I list the critical processes and knowledge, who runs each, and which rest on one person only.
  2. Each of those gets a written standard and a named backup, who runs it regularly so that the backup is real.
  3. The state of each critical process is visible to others: what is in progress and what comes next. When one starts resting on one person again, you see it.

What an engagement produces

  • A map of critical processes and knowledge, by person
  • A written standard for each process that rests on one person
  • A named backup for every critical process, with regular practice
  • The state of each critical process, visible to the team
  • Setup in your tools, or oversight if you set it up yourself

Rules, thresholds, scripts and automation logic are engagement deliverables and are not published here.

Find out whether this is actually your constraint.

Explore another problem