Knowledge is more than stored information
A process document can specify a sequence, but experienced work involves knowing when the sequence fits, when to pause, and what evidence should change the path. This is not merely undocumented information. It is situated judgment developed through practice.
When that judgment remains attached to individuals, the organization depends on informal access: who is available, who remembers, and who knows whom to ask.
An infrastructure perspective
Calling expertise infrastructure changes the management question. Instead of asking only how to document what people know, leaders can ask how expertise is observed, validated, made accessible, and maintained over time.
The aim is not to strip expertise from people. It is to create stronger conditions for people to learn from one another while preserving context and accountability.
Design implications
Useful systems should retain links between a recommendation and the evidence behind it. They should represent uncertainty, make exceptions visible, and allow practitioners to challenge interpretations.
- Observe work in context
- Preserve evidence and provenance
- Separate candidate patterns from approved guidance
- Make revision part of normal operation
- Keep accountable people in the decision loop
Open questions
How much context is required before a pattern becomes responsibly reusable? Who should validate it? How can organizations prevent past success from hardening into future dogma? These questions are operational as much as technical.