Go through three lists: your systems, the processes people run from memory, and the access only one person holds. For each item, ask who could do it tomorrow if the usual person were out for a month. Mark every item where the answer is nobody. Those marks are the list you work from.
Do the first pass with the IT team, then take the second list to each department head. The processes are usually the surprise, because IT often does not know they exist.
Systems
- Who can release a change to it? If one person does every release, a fix waits for that person.
- Who can restart it and restore it from backup? Recovery is the task you least want to learn during an outage.
- Who knows what it is connected to? Integrations and file transfers are where a change in one system breaks another.
- Who knows what runs on a schedule? Nightly jobs and monthly imports are easy to forget until one stops.
- Who built it, and are they still here? A former employee, a freelancer or a vendor may be the only one who ever understood it.
- Where is the code, and has anyone else ever built it from that copy? Code that only runs from one laptop belongs to that laptop.
- Who understands the reports that come out of it? The logic behind a number is often known to one analyst.
- Which spreadsheets, macros and small databases does the business run on? These are systems too, and each usually has one author.
- Which tools did someone build with an AI coding tool? They work, and nobody else has read them.
Processes people run from memory
- The month-end close. Ask for the steps in order. If they are written nowhere, they are in one person’s head.
- Pricing and quoting. The rules an experienced estimator applies are often in no system.
- Payroll and commissions. The exceptions are what one person remembers.
- Customer or vendor setup. Ask who knows every field that has to be filled in and why.
- Reports assembled by hand. If a report is built from exports every week, one person knows which exports and what to fix in them.
- Tasks done once a year. Renewals, year-end filings and annual price updates are forgotten between occasions by everyone except the person who did them last.
- The person everyone asks. In every department there is someone people go to when the system does something odd. Write down what they get asked.
Access only one person holds
- Administrator accounts. Every system that matters should have at least two.
- The domain registrar and DNS. If the company’s domain is registered to one person’s email address, that person controls the company’s email and website.
- Cloud and hosting accounts. Check who the account owner is. It is often whoever signed up first.
- Vendor portals and license keys. Renewals and support requests go through whoever holds the login.
- Banking, payment and payroll administration. These are usually outside IT, and usually held by one person.
- Sign-in codes. If the codes go to one person’s phone, that phone is a single point of failure.
- Passwords kept in someone’s head or their own notes. They belong in a password manager the company controls.
- Keys and certificates. Signing certificates, API keys and backup encryption keys expire or go missing with the person who created them.
How to run it
- Give the three lists to the IT team and fill in a name beside each item. Where the same name appears alone many times, you have found the concentration.
- Take the second list to each department head and ask them to add what is missing.
- For each item with one name, ask what would happen if it could not be done for a week.
- Sort by that answer.
Knowing your own process matters for more than cover. When Dunkin & Associates replaced a system that dated from the 1990s, its EVP of Operations, Doak Dunkin, wrote in his review on Clutch that a client has to understand its own business process first, because the team doing the work is only as good as the information it is given. A process that lives in one person’s head is hard to cover for, and it is just as hard to improve or replace.
What to do with the list
Start with the few items that would stop the business. For each one, get the minimum written down and have a second person do the task once. How do you reduce key-person risk on a small IT team? goes through the steps.
Some items will turn out to be signs of something larger. A business that runs on one person’s spreadsheet may have outgrown its tools: Signs You Have Outgrown Your Software covers how to tell.
Common questions
How long does this take? The first pass is a meeting with the IT team and a conversation with each department head. It is a list, and it does not need to be complete to be useful.
Who should run it? The IT leader, for the systems and the access. The processes need the head of each department, because IT often does not know they exist.
What do we do with the list? Rank it by what would stop the business, and start with the top few. Get each one written down and practiced by a second person.
Should we tell the people whose names are on it? Yes, and first. They already know. Most of them would like to be able to take a vacation without their phone.
If a system on the list is one that nobody else can read, a System Evaluation gives you an independent written account of it for a fixed fee.