When What the Organisation Learned Leaves With People

← Playbooks

Playbook · Recurring loss of context · Organisations × Psychology

Some organisations get smarter over time and some only accumulate individuals who did. This is a way to examine which one you are, and where context is actually being lost.

This is reusable guidance, not a record of what happened and not a procedure. It is a starting point for a situation that recurs in different forms — useful while its conditions hold, and worth abandoning where they do not.

The situation

Projects re-learn what earlier projects already established. Reasoning behind past decisions cannot be recovered, so it is reconstructed or re-argued. When experienced people leave, the organisation loses more than their tasks.

The question

Where does understanding accumulate here — in people, in documents, or nowhere in particular?

Conditions

What needs to be true, or examined, before this approach applies.

• The same questions are being answered more than once by different people.
• There is genuine appetite to maintain something, not just to create it.
• Someone can own a small number of living documents rather than a library.
• Existing documentation is stale rather than absent — a different problem with a different fix.

Signals

What is worth paying attention to.

• What a capable new joiner cannot find out without asking someone.
• Whether past decisions are recoverable with their reasoning, or only as outcomes.
• How much of the current model of the customer or system exists only in conversation.
• What broke, or nearly broke, the last time someone senior left.

Decisions

What may need to be decided, and by whom.

• Which few things are worth holding centrally, and which are genuinely disposable.
• Who maintains them, and what happens when that person is unavailable.
• Whether updating them is part of doing work or an activity after it.
• What is deliberately not written down, and why.

A first useful move

Pick the one question the organisation answers repeatedly and write the current answer down, with the date and the reasoning. One maintained document is worth more than a documentation initiative.

Not yet

Do not buy a knowledge platform, and do not run a documentation programme. Tooling does not create the habit of maintenance, and volume makes staleness harder to detect.

The trade-off

Written context makes reasoning inspectable, which also makes it contestable. Some organisations find that written positions become harder to change than unwritten ones, because revising them looks like reversing.

Assumptions

What this rests on, and what would change it.

What informed this

Conceptual synthesis, supported by observation in environments where context loss was visible. This is reasoning about a pattern rather than a measured finding.

What would change this approach

This changes if the organisation is small and stable enough that shared memory genuinely works, if regulation already forces documentation, or if the real problem is that written material exists and nobody trusts it. Distrusted documentation is a credibility problem, not a capture problem.

Where this stops being useful

It says nothing about which knowledge is worth keeping in a specific domain, and it does not help where the constraint is that people will not write, which is usually about incentives rather than method.

Related

Related reading

Industry

• Enterprise SaaS
• BFSI
• Healthcare
• Government

Knowledge · Architecture

• Keeping the reasoning outside the tools that produced it
• Separating decision cadence from delivery execution

Evidence · Observed Situation

• When unrelated frustrations turned out to share one structural cause
• When routine decisions were being escalated because no system carried the context

The situations linked above informed this guidance. They do not establish that it transfers to another environment — that remains a question about the specific organisation.

Knowledge →Work with Cralgo →