The 70% Expert Blind Spot

Priya Nair

So, Jordan, I was reviewing this training deck we got from one of our top software engineers, and, uh, under "how to troubleshoot a server crash," step three is literally, "Use your intuition to isolate the root cause." Intuition. Like, just magic it into existence, right?

Jordan Avery

Ah, the classic "magic step." I- I see this all the time. You ask an expert, "Hey, how do you do your job?" and they give you this beautifully polished, high-level summary that is completely useless to a beginner. It's like asking a master chef how to bake bread, and they just say, "Oh, you know, you just feel the dough."

Priya Nair

Yes! Exactly. And it's not because they're trying to hide secrets. It's this cognitive thing called automaticity. Once you do something a thousand times, your brain literally moves those skills from your conscious mind to the background, like background processing on a computer. You- you don't think about the clutch when you drive, you just drive.

Jordan Avery

Right, it's totally automated. And there is actual, hard science behind why this happens. There's this landmark research by Richard E. Clark and David Feldon on Cognitive Task Analysis. And they found that experts omit approximately 70% of the decisions and crucial steps they make when they describe how to perform a complex task. 70%, Priya!

Priya Nair

Wait, seven-zero? Like, seventy percent of the actual recipe is just... left out of the explanation?

Jordan Avery

Yes, 70%! Their unassisted self-reports are just fundamentally full of holes. So when we, as L&D folks, schedule a standard 60-minute Zoom call and ask them to "make a few slides on best practices," we are basically asking them to describe a movie when they've forgotten 70% of the scenes.

Priya Nair

Ugh, it's so true. And you know, we try to solve this by job shadowing. We think, "Oh, I'll just sit next to them and watch them work." But- but here's the catch... shadowing only captures physical actions. It doesn't capture the silent, split-second decisions happening inside their head. Like, if a senior salesperson looks at a prospect's LinkedIn profile and instantly decides *not* to pitch them a certain product... you don't see the mental "if-then" rule. You just see them click "close window."

Jordan Avery

Ooh, that is such a great distinction. The physical act is clicking "close," but the cognitive work was the invisible sorting of environmental cues. So, instead of asking "What do you do?" we have to start asking, "What did you notice right there, and how did you decide?"

Jordan Avery

So, how do we actually get to that hidden 70% without doing some massive, multi-month academic research study? I've been experimenting with this ultra-lightweight, three-prompt framework. You can do it in 15 minutes.

Priya Nair

Fifteen minutes? Okay, I'm skeptical, but... lay it on me. What's prompt one?

Jordan Avery

Okay, prompt one is what I call the "Messy Case" Hook. Never ask, "What is your standard process?" Instead, you say: "Tell me about a specific, high-stakes client or technical issue that went totally off the rails in the last 30 days."

Priya Nair

Ah, because that triggers episodic memory! They aren't pulling from a generic, clean script in their head; they're picturing that stressful Tuesday afternoon when the database was melting.

Jordan Avery

Exactly! It makes it real. Then, once they start telling the story, you hit them with prompt two: the "Invisible Cue" Probe. You ask: "At the exact second you decided to change your approach, what precise clue on that screen, or in that email, did you notice that a junior teammate would have completely missed?"

Priya Nair

Oh, I love that. "What did you notice that a junior would miss." That forces them to contrast their brain's library of patterns against someone who doesn't have them yet. It isolates the actual trigger.

Jordan Avery

Exactly. And then the third one, to map out the guardrails, is the "Decoy Option" Test. You ask: "What was the most obvious alternative action you could have taken right there, and how did you know it was a trap?"

Priya Nair

Oh, that's clever. Because beginners always fall for the obvious, superficial solution. Let's... let's actually roleplay this. Let's say we're interviewing a senior Customer Success Manager. The scenario is: a massive client is angry about a software bug and threatening to cancel their account. Jordan, if you ask them for "best practices" the old way, what do they say?

Jordan Avery

Oh, they'd say, "Well, Priya, you want to apologize sincerely, open a priority-one ticket with engineering, and maybe offer a service credit to keep them happy."

Priya Nair

Right, super generic. It sounds like a customer service robot. But now, let's use the three prompts. I'm the SME. Ask me prompt one.

Jordan Avery

Okay. "Priya, tell me about a customer situation that was absolute chaos recently."

Priya Nair

Uh, okay, yeah. Two weeks ago, the VP of marketing at our biggest retail account sent this scathing email. Their automated email campaigns had failed overnight. They were screaming, threatening to pull their entire contract by Friday.

Jordan Avery

Okay, now prompt two: "At the exact second you read that email, what did you notice that a junior CSM would have missed?"

Priya Nair

Hmm. Well... a junior CSM would have focused on the technical error code they pasted. But I noticed a line where the VP said, 'This is blocking our quarterly review presentation.' That was the clue. I realized she didn't actually care about the technical root cause right then. She was panicked because she had to present to her CEO in four hours, and she had no data visual to show him. She was terrified of looking bad in front of her boss.

Jordan Avery

Boom! There's the hidden 70%. Okay, prompt three: "What was the obvious decoy option there, and why didn't you do it?"

Priya Nair

Right, the decoy was opening that high-priority ticket with engineering and waiting for an update. If I did that, it would have taken three hours just to get a diagnostic, and she would have gone into her meeting empty-handed and furious. Instead, I bypassed the technical queue entirely. I- I went into our system, manually pulled their raw data, and hand-drew a PowerPoint slide with mock-up charts of their campaign performance so she had a visual ready for her CEO. We fixed the bug the next day, but that slide is what saved the account.

Jordan Avery

Look at that! That is gold. That is the difference between a training manual that says "apologize and file a ticket" and a training manual that teaches people how to actually save a multi-million dollar account by managing the stakeholder's internal anxiety.

Priya Nair

It's a completely different level of performance. And it took us, what, two minutes to get that out of my head just now?

Jordan Avery

Exactly. So, here is this week's experiment for everyone listening. If you have a meeting scheduled this week to write a standard training document or review a deck with an expert... cancel it. Or, well, don't cancel it, but hijack it. Take just 15 minutes, record the call, and run these three prompts. The "Messy Case" Hook, the "Invisible Cue" Probe, and the "Decoy Option" Test. Transcribe it, pull out those "if-then" rules, and build a one-page job aid based on what they *actually* do.

Priya Nair

I love that. It's fast, it's practical, and it actually bridges that 70% gap. Let's stop training people on the polished theory and start training them on the real, messy decisions. Alright, that's our quick take for today. Let us know if you try the 15-minute audit. Talk to you next time.

Jordan Avery

See ya.