How to Reduce Key-Person Dependency: Find the Risky Work and Standardize It, Judgment Calls Included

What Is Key-Person Dependency? 3 Causes and 4 Risks

Key-person dependency is when only one particular person knows how a task is done and what criteria its decisions rest on, and that knowledge hasn't been passed to anyone else. The biggest risk: on the day that person is out, the work stops. (In Japan this is called zokujinka — literally, work that has become "attached to a person.")

The opposite is standardization. What you keep is the skill

There's no official dictionary antonym, but the word most often used for the opposite state is "standardization": anyone can do the work with the same steps and the same criteria. You don't need to get rid of a veteran's deep expertise. The problem is that the criteria and the steps exist only in their head.

The 3 causes of key-person dependency

Fujitsu Learning Media, a Japanese corporate training provider, groups the causes into the three below. We've added where this article addresses each one.

The 4 risks of leaving it alone

• Work stops when they're out. For example, at a company with one bookkeeper, if that person is off for two weeks, the month-end close and invoicing slip
• Quality and pricing vary depending on who does the work
• "We have to ask so-and-so" waits pile up
• Handovers rely on word of mouth and on-the-job training, so new hires take longer to get up to speed

Minami

Process improvement lead

At our company, only Manager B can set prices on quotes. But Manager B is great at the job — is that really a bad thing?

Spark

DrillSpark consultant

Manager B isn't the problem. The problem is that the "yardstick" for those decisions lives only in B's head. Reducing key-person dependency means leaving the skill where it is and getting just the yardstick out where others can see it.

A 7-Point Checklist for Spotting Risky Work

Don't try to fix every task at once. Score tasks against seven points, and pick the one that ticks the most boxes. You're looking for three things: only one person can do it, it stops when they're out, and the judgment lives in their head.

The 7-point key-person dependency checklist

From here on, take Company A as an example: a 15-person metal fabrication shop. It sends out 40 quotes a month, and Manager B, a veteran sales manager two years from the company's mandatory retirement age (common at Japanese firms), sets the machining cost and discount on every one of them.

How to set priorities

Among the tasks with the most ticks, put the ones that fit both 1 and 2, and also 4, at the top. They stop when the person is out, and they contain judgment you can't hand over just by copying the steps.

Worked example: scoring Company A's 5 tasks

The month-end close also scores high, but its steps are fixed — they just aren't written down — and it involves few checkpoint-4 judgment calls, so it comes after quotes. If you don't have a task list yet, build one first using the steps in "How to Do a Work Inventory" so nothing slips through the scoring.

4 Tips for Writing Unwritten Judgment as Flowchart "Branches"

Rather than burying a veteran's judgment in a written procedure, write it as a question in a diamond (a branch) on a process flowchart. Then everyone can see where the decision happens and what it's based on. This is the work of moving judgment out of someone's head (tacit knowledge) into diagrams and tables (explicit knowledge).

Tip 1: Rephrase each judgment as a yes/no question

"Charge more for the hard ones" doesn't tell you what makes a job hard. Turn it into the question "Is this a difficult machining job?" and the answer splits into Yes and No, which drops straight into a branch on the diagram. Here's how Company A's quoting judgments look once rewritten (the numbers are Company A's own examples).

Figure 1 turns the first two into a diagram. Anyone can work out material cost from the unit price list, but at a glance you can see that Manager B's judgment came in at two points: the machining cost and the discount.

Rewrite this for your own work and send it, and the AI drafts a flowchart with the branches in place. The trick is to phrase each judgment as "decide whether X (if Y, then Z)."

Tip 2: Draw the line with a number or a clear condition

Words like "difficult" or "regular" mean different things to different people. Attach a number or a clear condition to each branch question — plate over 3 mm thick, 3 or more orders in the past year. If you can't settle on a number yet, set a provisional value based on recent decisions, then check it against the next quotes and adjust. For example, once you decide that "regular" means "number of orders in the past year," every salesperson will reach the same answer.

Tip 3: Write in an exception exit and "who to ask when unsure"

You don't need to cover every order with a condition. For orders that fit none of them, keep an arrow that says "send to Manager B." Standardize the common judgments and let the expert handle the rare ones. Drawing that line also makes the expert less likely to feel their job is being taken away.

Count how many cases go to the exception exit each month. When the same reason keeps coming up, add it to the diagram as a new condition.

Tip 4: When the criteria get detailed, split them into a lower level

When the conditions multiply and no longer fit on one page, move the contents of a branch into its own diagram. Figure 2 pulls out just the inside of Figure 1's "Difficult machining job?" branch. The surcharge rates are Company A's own examples.

In DrillSpark, you can create a lower level (a sub-process) inside a diagram and drill down into it. Use Figure 1 above to grasp the flow and Figure 2 below to check the detailed criteria.

Minami

Process improvement lead

Easy to say "write the conditions as numbers," but all Manager B ever says is "you can tell just by looking"...

Spark

DrillSpark consultant

Lay out the three most recent jobs and ask, "Why did this one get a surcharge?" — that's how "you can tell by looking" turns into words. I'll cover how to ask in the next section.

5 Ways to Draw Judgment Out of a Busy Veteran

Instead of asking the busy expert to "write it all down," split the work into a few short 30-minute interviews and have them correct a draft diagram that someone else prepared. That way you capture their judgment without stopping their work.

Method 1: Split it into three 30-minute sessions

Give each session its own theme: the first covers the flow of the work, the second the decision points, the third the exceptions and the conditions for turning work down. Try to cover everything in one sitting and it gets postponed for lack of a big enough block of time. Thirty minutes is easy to fit into the calendar even in busy periods. A 15-minute interview per person is enough just to build a task list (see "How to Do a Work Inventory"), but getting at the substance of someone's judgment takes about this much time.

Method 2: Don't start from a blank page — have them correct a draft

From the notes of the first session, the interviewer drafts the diagram first. It can be hand-drawn, or you can give the notes to an AI and have it draft a flowchart. When people talk about "using AI to reduce key-person dependency," this drafting is usually where AI actually helps. But the expert must always check that the judgment in it is correct.

For the expert, too, marking up mistakes in red is far easier than writing on a blank page. A correction like "No, actually I check with the plant manager before deciding" becomes a branch condition as-is.

Method 3: Lay out three recent real cases and ask

Ask a veteran "How do you decide?" and sometimes all they can say is "you can tell by looking." Put three of last month's quotes side by side and ask, "What's the difference between the one you added a surcharge to and the one you didn't?" and the criteria come out in words.

Method 4: Also ask what they don't do, and who they turn to when unsure

Judgment includes conditions for turning work down, not just for taking it on. Ask where they draw lines such as "this material goes to a subcontractor" or "we don't accept this lead time," and who they consult when unsure, and you can draw the exception exits into the diagram. Just changing how you ask makes the answers far more concrete.

Method 5: Make the expert the "owner of the criteria" to protect their standing

If the reluctance comes from "being the only one who can do it is how I'm valued," redefine the role. Make Manager B the person who sets and revises the criteria, and agree that changing the criteria requires B's sign-off. Rather than taking the work away, B's name stays on it as the owner of the criteria.

At Company A, for example, D from general affairs interviewed Manager B three times for 30 minutes each — 90 minutes in total. D compared last month's 12 quotes three at a time and wrote out four conditions for surcharges and discounts. All B had to do was mark up D's draft diagram in red.

Minami

Process improvement lead

I'm worried Manager B will think we're trying to take their job away, so it's hard to even ask...

Spark

DrillSpark consultant

You're not taking it away — you're making them "the one who sets the criteria." Agree that any change to the criteria needs B's OK, and their position actually becomes clearer.

Process Standardization in 5 Steps

Process standardization runs in five steps: pick one task → diagram the flow and branches → have the expert correct it → have someone else actually do the work from the diagram alone → decide the owner of the criteria and the update rules. Keep adding whatever made people stall in step 4, and the diagram gets finished.

What is process standardization?

Process standardization means getting to a state where anyone who does the work follows the same steps and criteria and gets the same result. Reducing key-person dependency is, in effect, carrying out this standardization starting with the riskiest work.

The 5 steps

1. Pick one risky task: start with the task that came out on top in the 7-point checklist
2. Diagram the flow and branches: in 30-minute interviews, rewrite each judgment as a question and a condition
3. Have the expert check and correct the diagram: ask them to confirm the numbers in the conditions and the exception exits
4. Have someone else actually do the work from the diagram alone: mark wherever they stall, and add the missing judgment
5. Decide the owner of the criteria and the update rules: who changes the criteria, and who updates the diagram and when

As Figure 3 shows, the stand-in test and the additions won't necessarily be done in one pass. Expect to go around a few times; not aiming for a perfect diagram on the first try is the key to not giving up halfway.

The "stand-in test": have someone else try it from the diagram alone

Step 4 is the surest way to check the quality of a diagram. When the expert reads it, they fill in the unwritten judgment in their head, so they don't notice the gaps. When someone who doesn't know the work tries it from the diagram alone, they're guaranteed to stall wherever something is missing.

At Company A, for example, E, a junior salesperson, prepared three quotes using only Figures 1 and 2 and compared them with the amounts Manager B had set. The one that was off came down to a judgment missing from the diagram: "for customer-supplied material (orders where the customer provides the material), leave out the material cost." They added that judgment as a branch and tried again.

Decide the pass mark in advance, too. Company A set it as "all three quotes within 3% of Manager B's amount." Without a pass mark, there's no telling how much to add before you're done, and diagramming drags on forever.

Dividing the roles: diagram, criteria table, and manual

Try to cram everything into one document and all of it becomes hard to read. Giving each thing its own home also makes it clear where to make the fix when the criteria change.

How to write the manual itself is covered in "How to Write a Work Manual." For branches and send-backs, it's easier to get started if you look at a finished example first and follow its lead.

3 Mechanisms That Make Standardization Stick

Even with a diagram in hand, if the backup never gets a chance to actually do the work, and there's no rule that the diagram gets updated when the criteria change, the diagram gradually drifts from reality and you slide back into key-person dependency. Here are the three mechanisms that make it stick.

Mechanism 1: Use a skills matrix to show that at least 2 people can do it

A skills matrix is a grid of tasks against people, with a symbol showing how far each person can go. Here we use a common Japanese notation: ◎ means can do it alone, ○ means can do it with the diagram, and △ means currently learning. For Company A, it looks like this.

Quote preparation has E at ○, but discount decisions on large deals are still Manager B alone. For the month-end close, too, C is the only ◎, and D is still learning. Any row with only one ◎ or ○ is a candidate for the next round of standardization.

Write the rules for changing the symbols under the table as well. For example, give ○ once someone passes the stand-in test and ◎ once they handle the live work on their own, and review the matrix every three months. Then the marks won't vary depending on who fills them in.

Mechanism 2: Have the backup handle the live work once a month

Reading a diagram doesn't make anyone good at the work. Let the backup handle live quotes at least once a month, with Manager B moving to a checking role. Job rotation, where people swap assignments regularly, and cross-training, where one person learns several tasks, follow the same idea.

At Company A, for example, they decided that E handles the first five quotes each month and Manager B only checks the amounts. Wherever E hesitates gets added to the diagram that same day. Every time it's used on live work, the diagram gets a little closer to reality.

Mechanism 3: A criteria change isn't done until the diagram is updated

If the discount cap changes but the diagram stays the same, anyone who follows it will get it wrong. Define a "change" as including the update: once the criteria owner gives the OK, the numbers in the branch are fixed that same day. Also decide who makes the fix and when the diagram gets reviewed (every six months, for example), and it's much less likely to be neglected.

Minami

Process improvement lead

I have a feeling nobody will be looking at the diagrams we make six months from now...

Spark

DrillSpark consultant

A diagram nobody looks at just isn't part of the work yet. Set one day a month when the backup uses it on live work, and you'll catch the outdated parts right away.

4 Common Mistakes in Reducing Key-Person Dependency, and How to Avoid Them

Most failures come down to four things: doing everything at once, writing the steps but not the judgment, leaving the expert out, and never updating what you built. Each is prevented by the same habits: one task at a time, judgment included, with the expert, and with a named person to keep it current.

Mistake 1: Trying to standardize every task at once

Try to diagram every task in the company at the same time and there won't be enough interview time; everything stalls halfway. Finish the one task that came out on top in the checklist, and move on only after it passes the stand-in test.

Mistake 2: Writing the steps but not the judgment

Even if you list the steps — calculate material cost → calculate machining cost → send — without writing how the machining cost is decided, people end up asking the veteran anyway. Write each judgment down to the branch question and the numbers in its conditions, and route anything that doesn't fit to the exception exit.

Mistake 3: Building it without the expert

If others build it on their own because the expert is busy, the conditions end up different from reality, or the expert feels it was decided behind their back and stops cooperating. Keep the interviews short to protect their time, and have them make the final corrections.

Mistake 4: Treating it as done once it's built

If you stop once the diagram exists, it stays unchanged even as the criteria change, and before long nobody looks at it. Set the backup's live-work day and the rule that criteria changes include updating the diagram, together.

Summary: Start by Picking One Risky Task and Diagramming It

Reducing key-person dependency isn't about averaging out a veteran's skill. It's about moving the yardstick for their decisions into diagrams and tables so others can make the same calls. You don't have to do it all at once; you can start by picking one risky task.

Start by choosing one task with the checklist and writing out your interview notes in plain language. Hand them to DrillSpark and the AI drafts a flowchart, which you can refine in conversation with the AI. Then show the finished diagram to the expert and have them confirm the branch conditions. There's a free plan, and no credit card is required.

Start by diagramming one task, all the way down to its decision points.

Related Templates

Related Guides

FAQ