Capturing Judgment, Not Just Steps: How to Make Expertise Transferable
Your SOPs document what to do. They rarely capture when and why. Here's how to make tacit expertise explicit and transferable.
The Missing Layer
Your SOPs tell people what to do. Step one, step two, step three. Clear enough.
But your best performers aren't just following steps. They're making judgment calls. When to escalate. How to read a client's tone. Which exception applies to which situation. What "good enough" looks like for this particular case.
This judgment layer is rarely documented. It lives in people's heads, built from years of pattern recognition and experience. It's the tribal knowledge that makes experts expert.
The common belief is that judgment can't be taught. You have to experience it. You have to "put in the years."
That's mostly wrong.
What Judgment Actually Is
Judgment isn't mystical. It's pattern recognition applied to novel situations.
When an experienced professional encounters a new case, they're not reasoning from first principles. They're matching the situation against patterns they've seen before. "This reminds me of that time when..." "This has the characteristics of the kind of situation where..."
These patterns feel like intuition, but they were learned. They accumulated through exposure to many situations over time. The expert's brain stores them implicitly, which is why experts often struggle to articulate their own judgment.
But patterns that were learned can be taught. You just have to make the implicit explicit.
From Tacit to Explicit
The first step is extraction. Getting the patterns out of experts' heads in a form that can be taught.
This requires asking the right questions. Not "what do you do?" but "when do you know that you should do X instead of Y?" Not "what's the process?" but "tell me about a time when you didn't follow the standard process, and why."
The magic is in the "when" and "why," not the "what." The "what" is already in your SOPs. The "when" and "why" are the judgment layer that differentiates experts from novices.
Scenario-Based Transfer
Once you've extracted judgment patterns, they need to be transferred. Documentation alone won't do it. People don't develop judgment from reading bullet points.
Scenarios work. "A client says X. You notice Y. What do you do?"
Good scenarios put learners in situations that require judgment, not just procedural knowledge. They present the kind of ambiguous, contextual situations that experts navigate intuitively.
The scenario forces the learner to reason through the situation. The feedback shows them how an expert would reason through it. Over time, the learner develops their own pattern library.
This is why testing beats sharing. Judgment develops through active reasoning, not passive absorption.
Decision Trees for Complex Calls
Some judgment calls are complex enough to benefit from explicit decision trees. Not rigid scripts, but structured frameworks that capture the key considerations.
"If A and B are true, consider X. If A and not B, consider Y. Watch out for Z, which changes everything."
Decision trees make reasoning visible. They translate intuitive judgment into a learnable structure. Junior staff can use them as training wheels. Over time, the framework becomes internalized and automatic.
The best decision trees come from reverse-engineering expert decisions. Ask experts to walk through real cases. Document the branch points. Capture what triggered each decision. Codify the pattern.
The Calibration Problem
One challenge in transferring judgment is calibration. Even if you teach the right patterns, people apply them inconsistently.
Two people can learn the same framework and reach different conclusions in the same situation. Their interpretation of "moderate risk" or "complex client" differs. Their threshold for escalation differs.
Calibration requires comparison. People need to see how their judgment compares to others', especially to experts. "Here's what you decided. Here's what the senior partner decided. Here's why the difference."
This isn't about right and wrong. It's about building shared understanding of standards. Over time, the team's judgment calibrates around common norms.
Judgment and Reinforcement
Like other knowledge, judgment decays without reinforcement. Patterns that aren't exercised fade from memory.
Spaced repetition applies to judgment as much as to procedural knowledge. Regular scenario-based questions keep judgment patterns fresh. They also surface drift, catching cases where individual interpretations have wandered from firm standards.
This is especially important for infrequent situations. The judgment for common scenarios stays sharp through daily practice. The judgment for rare-but-important scenarios needs explicit reinforcement because natural exposure doesn't provide enough reps.
The Expertise Multiplication Effect
When judgment stays locked in experts' heads, the firm can only scale as fast as it can create experts through experience. That takes years.
When judgment is made explicit and teachable, junior staff develop judgment faster. They still need experience, but they're not starting from zero. They have frameworks. They have patterns. They have exposure to how experts think.
This creates leverage. The firm's expertise isn't bottlenecked on the availability of senior people. Junior staff handle more independently. Seniors focus on the situations that genuinely require their level of judgment.
Starting the Process
Extracting judgment isn't easy, but it's not as hard as it seems.
Start with the decisions that matter most. The judgment calls that affect quality, compliance, or client relationships.
Find the experts who make those decisions well. Interview them. Not about what they do, but about how they think.
Build scenarios from real situations. Test them with junior staff. See where judgment diverges from expert norms. Refine the scenarios based on what you learn.
Reinforce regularly. Keep the judgment patterns active in memory.
This is exactly what Codex is designed for: turning the expertise in your senior people's heads into institutional capability that the whole team can access and develop.
The belief that judgment can't be taught is comforting for experts but limiting for firms. Judgment can be taught. It just requires making the implicit explicit, then reinforcing it over time.