operations

Key Person Risk in Small Business: Protect What Your Team Knows

Every small shop leans on one person who knows the prices, suppliers, and clients. Here is a practical way to spot key person risk and spread that knowledge across the team.

Published

Visit askconstella.com
Share
X Facebook WhatsApp Email

Most small businesses have someone who holds it all together. She answers the phone, knows the markups, remembers which supplier has the part, and can recall what you promised a client last spring. That is a strength until she is on vacation, out sick, or gone. This is key person risk, and for a small team it is one of the easiest operational risks to overlook.

What key person risk looks like day to day

You rarely notice it until something stalls. Look for these signs:

  • Teammates text one person for answers that should be easy to find.
  • Quotes wait when that person is out.
  • Prices, discounts, and supplier terms live in a personal inbox, a notebook, or someone's memory.
  • Client promises are known by one person only.

In the source story, the one person is called Sarah. Your own shop has its own version, and the cost shows up as delays, repeated questions, and interrupted time off.

Why it costs more than it seems

McKinsey found that knowledge workers spend nearly 20% of their week looking for information or tracking down the colleague who has it. In a small team, that search time falls on your most experienced people, and it pulls them away from the work only they can do.

A simple audit: what would stop if she left tomorrow?

Before choosing any tool, map the knowledge. Ask each person to list what only they know. Then sort the answers:

Knowledge typeExampleWhere it should live
PricingLabor rates, discounts, markupsShared price lists
SuppliersWho to call for parts, what they chargeShared supplier notes
ClientsPast jobs, promises madeShared client notes and quotes

Anything that lives in only one head or inbox is your risk list.

Moving from one person's memory to a shared one

The goal is not to replace your best people. It is to let the whole team ask questions of the same material. A shared project that holds price lists, quotes, supplier updates, and notes lets a colleague get an answer without interrupting anyone.

The example from the original story shows how this works. When Priya needs the weekend emergency rate, she asks the shared project and gets $165 an hour, two-hour minimum, with the source attached. No text to someone on the beach. You can read the full scenario in the original post on what happens when a key employee quits.

Handling a departure cleanly

When someone leaves for good, you want two things: their access ends, and their contributions stay. With a shared project, you open your team and remove the person. Their access is gone, while what they added to shared projects stays with the business.

A low-effort way to start

  1. Pick one shared project.
  2. Add the folder your go-to person already uses.
  3. Invite the team to start asking questions there.

There is nothing to migrate, so you are not planning a big rollout. You can see how Constella supports small businesses and try it free, on the web or with the Chrome extension.

The takeaway

People leave, take vacations, and get sick. A resilient small business assumes that and keeps its know-how where everyone can reach it. Start before the resignation letter arrives.