Loading lessons
Preparing the next section of the lesson graph.
47 published lessons with this tag.
A note that captures exactly one idea can be understood without its original context, linked to any argument, and recombined indefinitely — a note that captures two ideas can do none of these things reliably.
Every distinct idea needs a unique, stable address — without one, you cannot reference it, link to it, or build on it reliably.
The smallest useful unit is the level of decomposition where each piece carries independent meaning — small enough to be precise, large enough to be self-contained.
A precise name converts a fuzzy intuition into a findable, retrievable, composable object — and the act of naming changes what you can think.
An atomic note should carry enough context to be understood without its original source.
You choose how finely to decompose based on your purpose — not on some inherent "correct" level of detail. The same material supports different grain sizes for different uses.
A well-formed question is as valuable an atom as a well-formed answer.
When you write the same idea twice you have not yet named the pattern they share.
Ideas evolve. Your system should let you see how any atom changed over time — not just what you believe now, but what you believed before and why it shifted.
A single inbox that you process regularly prevents thoughts from being trapped in random places. The inbox is not storage — it is a waystation. Everything enters. Nothing stays.
Processing means deciding what to do with each item — organizing is a later step. Conflating the two creates systems that look tidy but never get worked.
Record why an idea matters and what triggered it not just the idea itself.
New captures go to a hot inbox — only processed items move to permanent storage. The separation protects both speed of capture and integrity of storage.
Different types of information decay at different rates. Some knowledge stays relevant for centuries. Some is obsolete by lunch. Knowing which is which changes what you pay attention to.
Each piece of signal you accumulate makes the next piece more valuable — noise does the opposite.
Information separated from its context becomes ambiguous or misleading.
Cognitive offloading works only when it is habitual. Externalization practiced daily compounds into an extended mind. Externalization practiced occasionally produces scattered artifacts that never cohere into infrastructure.
What you learn but do not write down you will learn again and again. The act of writing about what you learned is not documentation — it is a second act of learning that encodes deeper than the first.
Document your process for managing knowledge — not just the knowledge itself. Your system should be explicit enough that you could rebuild it from documentation alone.
When everything important is externalized — every decision, reasoning chain, emotion, goal, assumption, commitment, priority, mental model, blocker, energy pattern, learning, feedback signal, failure, progress marker, thinking condition, and system design — you gain complete cognitive freedom. The mind that holds nothing becomes the mind that can do anything.
A schema is a mental model that has been externalized, named, and structured so it can be examined, tested, and improved — turning invisible cognitive habit into visible cognitive infrastructure.
Individual atoms of knowledge become powerful when linked into a navigable structure.
Periodically review and clean your graph — remove dead links and add missing connections.
Writing about how different parts of your knowledge connect promotes integration. The act of articulating connections between ideas you already hold — in writing, where the structure must be made explicit — forces your cognitive system to do the linking work that passive familiarity never demands. Integration does not happen by having many schemas. It happens by writing the sentences that explain how they relate.
Set aside time specifically to look for connections between your schemas. Integration does not happen automatically — the connections between what you know in one domain and what you know in another remain invisible until you deliberately sit down and look for them. A periodic integration review is a scheduled appointment with your own knowledge system, dedicated not to learning anything new but to finding the links, tensions, and structural parallels between what you already know.
Written agent descriptions can be reviewed refined and shared.
A well-written document delegates explanation, alignment, and decision context to the future.
Build a collection of proven workflows you can deploy when needed.
Input processing storage retrieval and output form a complete information pipeline.
Taking notes while reading or listening forces active processing.
Set expiration dates on time-sensitive information so it does not clutter your system.
Combining information from multiple sources produces insights no single source contains.
Define how you share processed information with others efficiently.
When overwhelmed declare information bankruptcy and start fresh with curated sources.
Store completed outputs in a findable archive for future reference.
Keep your reviews in a searchable archive — patterns become visible across time.
Your complete set of tools should work together as a coherent system.
Document your tool configurations and workflows so you can recreate your setup.
When you cannot get the information you need to proceed the information flow is the constraint.
Keep a log of what you tried and what happened for future reference.
Maintain a list of behavioral experiments you want to run.
Writing down what you know preserves it for people you will never meet.
A team is smarter than any individual member — but only if it knows who knows what. Transactive memory systems are the meta-knowledge infrastructure that makes collective expertise navigable.
Documentation, shared notes, and knowledge bases are the team's externalized memory. Without designed memory systems, teams lose institutional knowledge through turnover, forget hard-won lessons, and repeatedly solve problems they have already solved.
Every organization has a knowledge graph — a network of expertise, institutional memory, relationships, and documented information that its schemas operate on. Mapping this graph reveals where knowledge is concentrated, where it is fragile (held by a single person), where it is redundant, and where critical gaps exist. The knowledge graph is to the organization what working memory is to the individual: the substrate that schemas operate on.
When people leave organizations, their schemas often leave with them — the tacit knowledge of why systems were designed a certain way, how processes actually work (versus how they are documented), and who to call when things break. This knowledge loss is invisible until the moment the knowledge is needed and no one has it. Organizations that do not actively externalize critical knowledge are always one resignation away from a knowledge crisis.
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.