Observation:
Solutions to recurring problems are often shared informally between engineers and teams.
Even when a solution has already been validated and clearly explained, it is not always applied when the same problem reappears.
In one case, a known solution was documented and shared after a previous incident. When the issue occurred again, alternative approaches were attempted first, while the validated solution was kept as a fallback.
Pattern:
Knowledge that is not institutionalized tends to be deferred, even when it is known and trusted.
Implication:
The existence of a solution does not guarantee its use.
When knowledge remains informal or loosely shared, it competes with exploration, personal reasoning and alternative approaches.
For knowledge to consistently influence outcomes, it must be embedded into systems, processes or shared artifacts, rather than relying on individual memory or intention.
Over time, this leads to repeated effort and avoidable incidents (FN-0018).
Part of the Field Notes series documenting operational patterns observed in real-world platform architectures.