Blog & Insights

How do you reduce key-person risk on a small IT team?

Find out what one person knows that nobody else does, get the parts that would stop the business written down and practiced by a second person, and change how work is assigned.

Find out exactly what that person knows that nobody else does. Get the parts that would stop the business written down and practiced by a second person. Then change how work is assigned so the situation does not build up again. On a small team you cannot make everyone interchangeable, so start with the systems the business cannot run without.

Why small teams end up here

It is rarely anyone’s mistake. A small IT team has roughly one person for each system, because that is what the budget covers. The most capable person gets the hardest problems, solves them, and becomes the only one who understands the solutions. Each year the gap between what they know and what everyone else knows gets wider, and nobody decided that it should.

The person in the middle of it usually knows. They are the one who gets called on vacation.

Step 1: List what only one person can do

Do this with the team, in an hour, on a whiteboard. For each system, ask who could handle it tomorrow if its usual owner were out for a month. Include the recurring jobs nobody thinks about: the month-end import, the certificate renewal, the script that runs on the first of the month. Include access as well, such as the one administrator account or the phone that receives the sign-in codes.

Which of your systems and processes depend on one person? is a checklist for this step.

Step 2: Rank the list by what would stop the business

You cannot fix all of it, so sort it. Put at the top anything where a failure stops orders, billing, payroll or production, and where recovery depends on one person being reachable. Put at the bottom the things that would be an annoyance for a week.

Work on the top few. A plan that covers everything tends not to get finished.

Step 3: Write down the minimum

Full documentation of an old system is a project most small teams never finish. Start with one page for each system at the top of the list.

  • How to get in: where it runs, which accounts, where the credentials are kept.
  • How to tell whether it is working.
  • How to restart it and how to restore it from backup.
  • What breaks most often and what fixes it.
  • Who to call: the vendor, the hosting provider, the person in the business who depends on it.

The quickest way to produce that page is to record the person doing the task and talking through it, then have someone else turn the recording into steps.

Step 4: Have a second person do it

A document nobody has used is untested. Have the second person do the task from the page while the first person watches and says nothing. Every time the first person has to speak, the page gains a line.

Then do it for real. The second person handles the next routine release, the next restore test and the next month-end job. When the first person takes a week off, do not call them. What goes wrong that week is your list for the following month.

Step 5: Put access in the company’s name

Knowledge is one half of the problem, and access is the other. Check each of these.

  • Administrator accounts are assigned to at least two people, and none is a personal account.
  • The domain registrar, the cloud accounts and the vendor portals are registered to a company address that more than one person can reach.
  • Passwords and keys are in a shared password manager.
  • Sign-in codes go to a device or a method that more than one person controls.
  • An emergency way in exists, has been tested, and is stored where the company can get to it.

Step 6: Change how work is assigned

Without this step, the same situation builds up again.

  • A second person reviews every change to a system that matters.
  • Routine tasks rotate. The person who did the release last time watches this time.
  • No new system goes live with one owner. Name two before it is built.
  • The page from step 3 is updated as part of the work, each time a task is done.

Horizontally Scaling Your Development Team covers the same idea for a codebase: how to build it so that new people can work in it.

When the one person is outside the company

Sometimes the only person who understands a system is a vendor, a freelancer or a former employee. Longshot Cameras is an example. In his review on Clutch, its founder, Clay Rhoden, says the company’s existing app had been developed by freelancers, and that our work with them began when it needed updates for a new version of the product.

If that is where you are, check two things now, while the relationship is good. The code and the accounts should be in the company’s name, and someone inside the company should be able to describe what the system does and where it runs.

When you cannot add a person

A second person does not have to be an employee. A partner who supports the system can be the second set of hands, provided they have done the work at least once and the access is already set up. The true cost of hiring your own developers goes through the trade-offs between hiring and using a firm.

Common questions

We cannot afford a second person for every system. What then? You do not need one for every system. Rank the systems by what would stop the business, and cover the top few. For the rest, a written page on how to get in and how to recover is far better than nothing.

How do I raise this without making the person feel threatened? Say what is true: the company depends on them too much, and that is unfair to them. They cannot take a real vacation. Sharing what they know is how that changes.

Is documentation enough? No. Documentation nobody has used is untested. The test is a second person doing the task from the document while the first person watches and says nothing.

What if the one person is a vendor? The steps are the same, with one addition. Make sure the code, the accounts and the credentials are in the company’s name, so that you can bring in someone else if you have to.

If the system at the top of your list is one that nobody else can read, a System Evaluation gives you an independent written account of it for a fixed fee.

Related service: Strategic IT Advisory

More like this, in your inbox. Subscribe for our latest thinking, resources, and events.

Get started

Want results like these?