The Org Memory

Every chapter of The Org Memory with its printed epigraph, what you can do afterwards, and the moment it is built for.

1. Introduction

   The Cost of Institutional Amnesia

   What you can do afterwards

   You will run a forgetting audit, fill every field for one knowledge item, and name the three highest-cost pieces of knowledge that left with the last departure.

   Use this chapter when

   A key person or founding team has left, been laid off, or restructured into a new role, and the next team cannot answer "why did we do this?"

2. Chapter 1

   Acquire at the Source — and at the Exit

   Acquiring institutional knowledge after the fact, or after the person has left, is too late and too incomplete. Full context exists once: while the decision is being made. Unstated knowledge is reachable once: before the person walks out the door. Acquisition must happen at both ends of a tenure.

   What you can do afterwards

   You will build the six-field source template and the five-field exit protocol, then run them on the next material decision and the next departure.

   Use this chapter when

   Decisions are being made in rooms and threads that produce no durable record, or people are leaving with the only copy of the rationale in their head.

3. Chapter 2

   Retain What Matters Through Turnover

   Storing everything creates a swamp that no one can find anything in. Retention in a company that turns over must be designed for the moment after the original architect leaves, not for the moment the original architect is in the room. Storage is not retention. Retention is design for the next team, in the next quarter, after the next cycle of churn.

   What you can do afterwards

   You will design the retention standard for your three most critical pieces of institutional knowledge, apply the five properties to one artifact end to end, and gate the result with the durability test.

   Use this chapter when

   The team is about to enter a cycle of growth or turnover, or a system's rationale is held by a small number of people.

4. Chapter 3

   Curate Ruthlessly — Across Cycles

   In a company that turns over, everything staying forever is how institutional knowledge becomes unusable. Ruthless curation keeps the memory alive and trustworthy through every cycle: prune what is no longer true, update what has changed, and preserve the history of what was true and why. The swamp is not a storage problem. It is a maintenance problem that gets worse with every departure.

   What you can do afterwards

   You will run the curation pattern on one no-longer-true artifact, install the 90-minute quarterly pass, and give your five most-used artifacts an owner and a "last verified" date.

   Use this chapter when

   The institutional memory contains rules, exceptions, or decisions that no longer match the current organization, or that the current team follows without verifying.

5. Chapter 4

   History and Provenance — Through the People Who Leave

   What you can do afterwards

   You will create versioned artifacts with the full human chain for your three most important in-force decisions, repair one broken chain retroactively, and test the result with a new joiner.

   Use this chapter when

   A past decision is being referenced and the current team cannot explain the rationale, or the team that made it is no longer in the room.

6. Chapter 5

   Index for Retrieval — For the Team That Comes Next

   In a company that turns over, an institutional memory that cannot be queried at the moment of need is not a memory. Indexing that surfaces the right context to the next team, after the next departure, is the only retrieval that earns its place. The knowledge is only as good as the moment it appears for the people who were not in the original room.

   What you can do afterwards

   You will design the retrieval path for your three most critical artifacts. You will build the alias layer that maps day-one vocabulary to artifact language, then run the 60-second test with a real new joiner.

   Use this chapter when

   A new joiner asks "how do we do this?" and the answer exists somewhere, or the team follows an outdated artifact because the right one is not findable.

7. Chapter 6

   Verify Before Use — Especially After the Last Departure

   In a company that turns over, trust is not a retrieval strategy. The artifact the previous team wrote gets followed by the next team, in a changed world, on the authority of a wiki that never checks itself. Verification is the gate between finding an artifact and betting the institution on it.

   What you can do afterwards

   You will run the five-step verification protocol on the three highest-stakes artifacts your team currently follows. You will install the institutional defense test with a new joiner and log the first use decisions the next team will inherit.

   Use this chapter when

   The current team follows artifacts written by people who have left, or a high-stakes decision is about to rest on a page nobody has checked since the last restructure.

8. Chapter 7

   Evolve the Memory — Across Cycles, With the People Who Are Still Here

   What you can do afterwards

   You will give your five most-used artifacts a full evolution plan each: trigger, owning role, cadence, role-reassignment clause, with the first review ninety days out.

   Use this chapter when

   The memory no longer matches the current organization or market, or the post-mortem culture keeps naming the same institutional cause across cycles.

9. Chapter 8

   Agent-Augmented Memory — For the Team That Has to Defend What the Agent Decided

   What you can do afterwards

   You will audit your highest-stakes agent use case and design its memory layer. The bar: a new joiner reconstructs a 90-day-old agent decision, context and rationale included, without rerunning the model.

   Use this chapter when

   An agent makes or informs decisions the company must defend in the next cycle, and the current team cannot explain a specific output, or the verifying human has left.

10. Chapter 9

    The Cost of Forgetting, Especially What Walks Out the Door

    In a company that turns over, the cost of repeated mistakes, slow re-onboarding, and lost context is real, recurring, and measurable. Quantifying the last cycle of turnover turns "we should probably remember that" into a balance-sheet line. The number is what lets the memory work survive the next quarter's pressure to cut exactly the work that prevents the next reconstruction.

    What you can do afterwards

    You will price the three most expensive forgetting events of the last 24 months, at least one tied to turnover. Then you will put the number in the room where the next similar decision gets made.

    Use this chapter when

    The team keeps paying for the same classes of mistake and reconstruction, and the memory work has no budget line to defend itself with.

11. Chapter 10

    Institutional Memory as a Moat That Survives the People

    What you can do afterwards

    You will run the moat audit on your institutional memory. You will name where it compounds, where it leaks, and the one investment that widens the gap next quarter.

    Use this chapter when

    Leadership treats the memory work as a cost center, or a competitor just hired three of your engineers and the team is asking what the company still has.

12. Chapter 11

    Onboarding and Offboarding Knowledge — The Two Halves of the Same Handoff

    In a company that turns over, knowledge that walks out with departing humans, or that new humans must rediscover, is not institutional memory. Lifecycle design is required at every entry and every exit, and the two are the same handoff running in opposite directions. The memory survives the people who carry it, in both directions, or it does not survive at all.

    What you can do afterwards

    You will design the exit protocol and the entry protocol as two halves of one handoff. You will pre-commit the compressed-exit playbook, then run both halves on the next notice and the next joiner.

    Use this chapter when

    A joiner is arriving in an emptied role, a departure is coming with two weeks or two hours of notice, or a restructure is moving knowledge between roles.

13. Chapter 12

    Building Your Institutional Memory Protocol

    Every project feels new and every mistake feels original until the company has a living protocol. Eleven pages, two standing safeguards, three rituals: the assembly that turns tribal knowledge into institutional intelligence that survives the people who built it.

    What you can do afterwards

    You will write version one of your institutional memory protocol, one page for every component, safeguards and rituals included. You will put the first weekly standup on the calendar.

    Use this chapter when

    The company is entering another cycle of turnover, the post-mortems keep naming the same cause, or the memory work needs to defend itself in the next budget meeting.

14. Conclusion

    The Company That Remembers

    An institutional memory is sustainable organizational intelligence: the company remembering and learning better than any individual, across every cycle of turnover. The book ends where the practice begins.

    What you can do afterwards

    You will write your institutional memory commitment in one sentence, name the role that owns the protocol across the next cycle, and put the first 90-day review on the calendar.

    Use this chapter when

    The company has paid the amnesia tax more than once and you are ready to make the protocol the default instead of the exception.