Explicit knowledge versus tacit judgment
Explicit knowledge can be stated and stored: product facts, stages, rules, and definitions. Tacit judgment appears in use: sensing that an objection is misdiagnosed, recognizing who really influences a decision, or knowing that a technically correct answer is badly timed.
The goal is not to convert every intuition into a rigid rule. It is to make important judgment visible enough to examine and teach.
What to observe
Focus on moments with ambiguity or choice. Useful examples include buyer signals, objection diagnosis, timing, stakeholder mapping, and qualification judgment. Capture what the rep noticed before asking them to explain why.
How to elicit the reasoning
Replay the moment and ask what changed, what alternatives were considered, what risk the rep was trying to avoid, and what would have produced a different response. Concrete recall is more useful than abstract advice.
Compare the explanation with the conversation and with other cases. Experts can rationalize after the fact, so self-report should be evidence—not the only source of truth.
How to structure and validate it
Write the candidate skill as context → signal → decision → action → expected effect → exceptions. Review it with multiple experienced people and with examples where the same action did not work.
Implementation checklist
Begin with one recurring situation and a small review group. Preserve links to source evidence, assign an owner, and define when new evidence should trigger revision.
Sources and further reading
External sources support the general learning, knowledge, governance, or research-method concepts used above. WinPattern-specific models are presented as frameworks and interpretations.
A Dynamic Theory of Organizational Knowledge CreationOrganization ScienceFoundational theory on the relationship between tacit and explicit knowledge in organizations.