Your team knows where to find the files. They can follow the steps, use the templates, and complete the routine parts of the work without you.

Then something changes.

A client asks for an exception or two priorities conflict. Perhaps some information does not quite fit an usual pattern or a decision carries more risk than expected.

When any of those things happen, the work stops, and the questions comes back to you. You answer it quickly and the matter is handled in a manner of minutes. The answer feels obvious enough that you may wonder why they could not reach the same conclusion themselves.

Then it happens again.

From the outside, this looks like a delegation problem. Perhaps the team needs more confidence. Maybe the process needs another checklist or you need to let go.

Any of those explanations may be partly true. They still leave one important question unanswered:

Why can capable people follow a process and still fail to get the same results as you…the expert?

The answer may be hiding inside what experience has done to your thinking.

The process was never the whole job

Most processes describe what can be observed.

• Open this file.

• Review these fields.

• Compare the information.

• Choose an option.

• Send the response.

That description can be accurate and still be incomplete. It records the sequence of actions while leaving out the judgment that governs them.

The missing knowledge often lives inside words that appear perfectly clear to the person who wrote the process:

• Review.

• Assess.

• Determine.

• Use your judgment.

Each word contains a decision that has already been compressed.

What should the person look for?
Which details matter?
What combination of signals changes the meaning of the case?
When should the usual rule be followed, and when should it be set aside?
What makes one exception reasonable and another dangerous?

The document tells someone to make the decision. It does not necessarily reveal what makes the decision make sense.

This is the procedure-judgment gap:

the distance between performing the visible steps of the work and interpreting the conditions that determine what should happen next.

Your team may know the procedure while the judgment remains in your head.

Experience changes what you see

Expertise does more than add information to memory. Over time, it changes how information is organized and what becomes perceptible.

Classic studies of chess expertise found that skilled players did not simply remember more individual pieces. They perceived meaningful configurations. What appeared to a beginner as separate details appeared to an expert as a familiar pattern (Chase & Simon, 1973).

Researchers also found a similar difference in physics. When experts and novices reviewed the same problems, novices tended to group them by visible features, such as springs or inclined planes. Experts grouped them by the deeper principles required to solve them (Chi, Feltovich, & Glaser, 1981).

Both groups saw the same information. They did not see the same problem.

With enough relevant practice and useful feedback, experience builds connections among cues, patterns, expectations, and possible responses. An expert can encounter a situation and rapidly retrieve what matters without deliberately reconstructing every lesson that produced the judgment (Ericsson & Kintsch, 1995; Kahneman & Klein, 2009).

Studies of experienced fireground commanders offer a vivid example. These leaders often did not compare several options one by one. They recognized a familiar type of situation, noticed the cues that mattered, identified a plausible response, and mentally tested whether it would work (Klein, Calderwood, & Clinton-Cirocco, 1986).

What looks like intuition from the outside can contain years of accumulated pattern recognition.

This is cognitive compression.

Many observations, mistakes, exceptions, and feedback loops have been reorganized into a faster form of judgment. The compression is part of what makes expertise valuable. It allows you to respond to complexity without treating every situation as entirely new.

It also creates a transfer problem.

You experience the conclusion. The person learning from you needs access to at least some of the distinctions that produced it.

What becomes obvious becomes difficult to explain

Once knowledge has been compressed, experts can underestimate how much a less experienced person will need in order to learn what is being taught.

In one set of studies, people with more expertise were worse at predicting how long novices would need to complete a task. Knowing how to do the task made it harder to reconstruct the experience of someone who did not yet know (Hinds, 1999).

This does not mean experts are incapable of teaching. It means expertise can distort the expert’s estimate of what requires explanation. The effect becomes even more interesting when we look at the explanations themselves.

In a study that used an electronic circuit task, experts gave instructions that focused more on advanced ideas and general principles. Beginners gave more specific, step-by-step details. (Hinds, 1999).

Novices who learned from beginners performed better on the same task and reported fewer problems with the instructions. Yet beginners who learned from experts performed better when they had to transfer what they learned to a different task in the same domain (Hinds, Patterson, & Pfeffer, 2001).

This finding adds an important layer to the usual explanation of the expert blind spot. The experts were not poor at explaining. Their instructions helped learners understand principles they could apply in new situations. The beginners provided concrete details that made it easier to repeat the task in front of them.

People need both types of guidance.

They need clear instructions that help them take action and an explanation of the thinking behind those instructions so they can adjust when the situation changes.

When either type is missing, learners receive only part of the expert’s knowledge.

Step-by-step instructions can teach someone to follow a process without knowing how to make decisions.

A general framework can help someone understand the bigger picture without knowing exactly what to do. Independent performance requires a clear connection between the two.

Why asking, “How do you do this?” rarely solves the problem

When organizations realize that important knowledge lives inside one person, they often respond by asking the expert to write down everything they know to train others. The request sounds reasonable. It also assumes that expertise is stored as a complete explanation waiting to be retrieved.

Often, it is not.

Research on verbal reports shows that people cannot always reconstruct the mental processes that produced a judgment after the fact. A retrospective explanation may contain an accurate conclusion while leaving out some of the cues that actually shaped the decision (Nisbett & Wilson, 1977).

That limitation is easy to overstate. Experts are not locked out of their own minds. Research also shows that well-designed concurrent verbalization can recover information that a person is actively attending to while performing a task (Ericsson & Simon, 1980).

The method matters.

“Tell me how you do your job” invites a polished summary.

“Take me back to a difficult case.

• What did you notice first?

• What did you expect to happen?

• Which detail changed your interpretation?

• What option did you reject?

• What would a less experienced person have missed?”

  invites access to the judgment.

Cognitive task analysis uses questions like these to surface cues, decisions, goals, exceptions, and sensemaking that ordinary process documentation tends to miss.

Meta-analytic research has found that training built from this kind of systematic elicitation can improve learning and performance across domains (Tofel-Grehl & Feldon, 2013). A later meta-analysis in surgery found improvements in both procedural knowledge and technical performance when training included the cognitive skills behind the procedure (Edwards et al., 2021).

The knowledge is often retrievable, but retrieval requires more than asking the expert for steps.

How judgment gaps becomes a business bottleneck

A process moves smoothly while conditions remain familiar. The moment uncertainty enters, the hidden structure of the work becomes visible.

The team encounters a case that does not match the documented example. They can see the difference, but they do not know whether the difference matters. They lack the cue that tells them how to interpret it, the threshold that signals risk, or the principle that helps them choose between competing priorities.

So they escalate.

You resolve the case. The work continues. Because your answer solves the immediate problem, nobody stops to extract the judgment that made the answer possible.

The next unusual case returns to you too.

Over time, the organization builds a reliable route around its missing knowledge. Instead of making the judgment transferable, it makes the expert accessible.

That arrangement can feel efficient for a long time. Asking you is faster than reconstructing how you think. Your speed disguises the cost of the dependency.

The cost becomes easier to see as the business grows.

• More clients create more exceptions.

• More employees create more questions.

• More offerings create more points at which someone must interpret, prioritize, or adapt.

The documented process distributes activity, while the unresolved judgment keeps decision authority concentrated. Eventually, your attention becomes the capacity limit of the system.

This is the deeper reason some delegation efforts fail. The task was handed over. The authority may even have been handed over, too. The interpretive structure needed to use that authority was not.

The team is not necessarily dependent because its members lack initiative. They may be responding rationally to a system that asks them to make decisions without giving them access to the basis on which good decisions are judged.

The bottleneck is a condition, not an inevitable consequence of expertise

The research does not establish that expertise automatically produces a business bottleneck. It also does not support treating every centralized decision as a failure to delegate.

• Some decisions belong with the founder or senior expert because they carry legal, ethical, strategic, or financial consequences.

• Some team members still need practice.

• Some environments change too quickly for yesterday’s patterns to remain reliable.

Experience itself produces trustworthy intuition only when people have had sufficient exposure to valid patterns and useful feedback (Kahneman & Klein, 2009).

Expertise becomes a bottleneck when several conditions converge:

• important judgment is concentrated in one person,

• the cues and decision tests behind that judgment are absent from the surrounding system,

• other people lack the practice and feedback needed to rebuild them, and

• uncertainty is repeatedly routed back to the same expert.

What your team needs from you

If your team can follow the process but the important decisions still return to you, another procedure may not be the first thing they need.

They may need the structure beneath the procedure. They need to know:

• which cues deserve attention;

• what those cues mean in combination;

• which conditions make the standard response unsafe or ineffective;

• where the decision boundaries sit;

• what tradeoffs govern the choice;

• what a good outcome looks like;

• when escalation is appropriate; and

• how feedback will help them refine their judgment.

This is the part of expertise that a checklist rarely captures on its own.

The next time someone brings you a decision you thought you had already delegated, pay attention to the difference between the documented case and the case in front of you.

Before you give the answer, ask yourself:

What am I noticing that tells me what to do?

Then make that distinction visible.

Your answer may solve this case. The distinction can help someone solve the next one without you.

That is the point at which expertise stops being a private source of speed and starts becoming shared capacity.

Subscribe now

Share Untrap Your Expertise™

When you’re ready, here are three ways I can help.

1. Learn the concepts.
Subscribe to Untrap Your Expertise for practical insights on making expertise visible, transferable, and repeatable.

2. Build the capability.
Upgrade to the paid tier for implementation guides, toolkits, prompts, and practical frameworks you can apply immediately.

3. Solve the problem together.
If your organization or expert-led business is struggling with inconsistent results because critical expertise stays trapped inside people’s heads, explore the Expertise Translation Sprint or Advisory. Schedule a consultation here.

References

Butticè, V., Colombo, M. G., & Rovelli, P. (2024). Venture capital and the delegation of decision authority in startups: An exploratory study. Journal of Industrial and Business Economics, 51(4), 893–923. https://doi.org/10.1007/s40812-024-00313-4

Chase, W. G., & Simon, H. A. (1973). Perception in chess. Cognitive Psychology, 4(1), 55–81. https://doi.org/10.1016/0010-0285(73)90004-2

Chi, M. T. H., Feltovich, P. J., & Glaser, R. (1981). Categorization and representation of physics problems by experts and novices. Cognitive Science, 5(2), 121–152. https://doi.org/10.1207/s15516709cog0502_2

Connelly, C. E., Zweig, D., Webster, J., & Trougakos, J. P. (2012). Knowledge hiding in organizations. Journal of Organizational Behavior, 33(1), 64–88. https://doi.org/10.1002/job.737

Edwards, T. C., Coombs, A. W., Szyszka, B., Logishetty, K., & Cobb, J. P. (2021). Cognitive task analysis-based training in surgery: A meta-analysis. BJS Open, 5(6), zrab122. https://doi.org/10.1093/bjsopen/zrab122

Ericsson, K. A., & Kintsch, W. (1995). Long-term working memory. Psychological Review, 102(2), 211–245. https://doi.org/10.1037/0033-295X.102.2.211

Ericsson, K. A., & Simon, H. A. (1980). Verbal reports as data. Psychological Review, 87(3), 215–251. https://doi.org/10.1037/0033-295X.87.3.215

Hinds, P. J. (1999). The curse of expertise: The effects of expertise and debiasing methods on predictions of novice performance. Journal of Experimental Psychology: Applied, 5(2), 205–221. https://doi.org/10.1037/1076-898X.5.2.205

Hinds, P. J., Patterson, M., & Pfeffer, J. (2001). Bothered by abstraction: The effect of expertise on knowledge transfer and subsequent novice performance. Journal of Applied Psychology, 86(6), 1232–1243. https://doi.org/10.1037/0021-9010.86.6.1232

Kahneman, D., & Klein, G. (2009). Conditions for intuitive expertise: A failure to disagree. American Psychologist, 64(6), 515–526. https://doi.org/10.1037/a0016755

Klein, G. A., Calderwood, R., & Clinton-Cirocco, A. (1986). Rapid decision making on the fire ground. Proceedings of the Human Factors Society Annual Meeting, 30(6), 576–580. https://doi.org/10.1177/154193128603000616

Nisbett, R. E., & Wilson, T. D. (1977). Telling more than we can know: Verbal reports on mental processes. Psychological Review, 84(3), 231–259. https://doi.org/10.1037/0033-295X.84.3.231

Peng, H. (2013). Why and when do people hide knowledge? Journal of Knowledge Management, 17(3), 398–415. https://doi.org/10.1108/JKM-12-2012-0380

Tofel-Grehl, C., & Feldon, D. F. (2013). Cognitive task analysis-based training: A meta-analysis of studies. Journal of Cognitive Engineering and Decision Making, 7(3), 293–304. https://doi.org/10.1177/1555343412474821