Design knowledge systems around knowledge flow (ensuring
Design knowledge systems around knowledge flow (ensuring knowledge reaches those who need it when they need it) rather than knowledge storage volume.
Why This Is a Principle
This is a principle derived from Open-Loop Cognitive Cost (Zeigarnik) (unresolved cognitive commitments consume working memory until externalized to a trusted system), Knowledge that exists only in tacit form degrades without (knowledge that exists only in tacit form degrades), and Information and attention have an inverse relationship: a (information wealth creates attention poverty). It prescribes HOW to design knowledge systems - focusing on flow rather than accumulation - which is actionable guidance that follows from these axioms but is not itself foundational.
Source Lessons
Organizational knowledge management
Systems for capturing, storing, and distributing organizational knowledge. Every organization generates knowledge — through its projects, its experiments, its mistakes, its customer interactions, and its daily operations. Most of this knowledge lives in the heads of individual employees and walks out the door when they leave. Organizational knowledge management is the infrastructure that captures this knowledge, stores it in accessible forms, and distributes it to the people who need it. In self-directing organizations, knowledge management is especially critical: when decisions are distributed, every decision-maker needs access to the organization's accumulated knowledge — not just their own experience.
Culture is infrastructure not decoration
Culture operates like organizational infrastructure — the invisible systems (plumbing, wiring, foundations) that determine how the building actually functions. Like physical infrastructure, culture is invisible when working correctly, catastrophically visible when it fails, expensive to retrofit, and impossible to bolt on after the structure is built. Organizations that treat culture as decoration (something to display) rather than infrastructure (something to engineer) consistently underinvest in it — and pay the costs in coordination failures, talent attrition, and strategic misalignment.
Distributed decision-making
Moving decisions to the people closest to the information improves both speed and quality. Centralized decision-making creates a fundamental information problem: the person with the authority to decide is not the person with the best information about the situation. Every level of hierarchy that a decision must traverse adds delay (the decision waits in someone's queue), distortion (the information is simplified or filtered as it moves upward), and distance (the decision-maker lacks the contextual nuance that the person closest to the situation possesses). Distributed decision-making solves this problem by moving authority to where the information already is — but it requires infrastructure to maintain coordination.
Transparency as organizational infrastructure
When information flows freely, coordination happens naturally. Transparency is not a virtue — it is an infrastructure. In hierarchical organizations, information is a source of power: managers control information flow and use their information advantage to justify their decision-making authority. In self-directing organizations, information is a coordination mechanism: when everyone has access to the same information, local decisions naturally align because they are based on the same reality. Transparency does not mean broadcasting everything to everyone — it means ensuring that decision-relevant information is accessible to the people making decisions.