Integration · Change that lasts

When the Person Who Knows Your Automated Process Is Out

By Editorial Team··Updated ·2 min. read

If the one person who knows your automated process is out, it keeps running until the first error. Then it snags. You can spread that knowledge in two weeks: name a stand-in, write a one-page summary and run through one fault together.

How can you tell your process depends on a single person?

Ask one question: who knows what to do when the process sends an error message? If the honest answer is "one person", your process depends on that one head.

Take a typical case. An enquiry arrives by email, and the process enters the appointment, sends the confirmation and reminds both sides. It has run cleanly for months. That's exactly why nobody on your team has learned where to look when something goes wrong.

That person is often you. You helped set up the process, you know its exceptions, and every question lands on your desk. It feels like control. In fact it's a bottleneck, and it has your name on it.

What happens when the person in charge is sick or quits?

The process keeps running until the first fault. Then the error message lands with someone who can't read it, or in an inbox nobody checks.

Do the math. The person in charge is out for two weeks. On day three a password changes, and the process stops entering appointments. Until they're back, your customers get no confirmation. They notice before you do.

You're thinking: then I'll just give them a quick call. That works as long as the person can be reached and remembers. When someone is out, you can't count on either. Illness delays your knowledge. A resignation walks out the door with it.

How do you spread the knowledge in two weeks?

You do it in three steps: you name a stand-in, write a short description and run through a fault together once. For a process that's already running, that's all it takes.

In week one, you name someone who already touches the process day to day, say the colleague who sees the appointments. Together you write one page with three answers. What triggers the process? What happens next, and in what order? How does she spot a fault, and who does she call then? The detailed write-up from your preparation (Why You Want to Clean Up Your Data Before You Automate Anything) stays as it is. Your stand-in needs the short version for when it counts.

In week two, you run through a fault together. Your stand-in leads and you stay quiet. Every question she has to ask you goes onto the page afterwards.

You're done when she spots the fault without you and knows the next move.

Change lasts when it doesn't depend on any one person. For your process, that means it belongs to the business, not to one head. For you, it means handing over knowledge that has given you security until now. If this step is harder for you than the writing, the lever lies with you, not with the process. That's exactly where the challenge comes in: four days, your first step in Become → Do → Have, at impruvement.com/challenge.

Frequently Asked Questions

Ask who knows what to do when the process sends an error message. If the honest answer is one person, your process depends on that one head.

All articles on Integration · back to the Blog

Also available as Markdown.