Critical knowledge lives in chat and memory
Important operational or architectural knowledge exists mainly in people's heads or scattered chat history.
- Where you see this
distributed teamsfast-growing orgsincident-heavy environments
- Not necessarily a problem when
- the topic is genuinely ephemeral and low-risk
- Often mistaken for
- our team is small, so we do not need durable memory
- Time horizon
- medium-term
- Best placed to act
tech leadengineering manager
The signal
What you would actually notice
Institutional memory becomes fragile, onboarding slows, and incidents become harder to resolve.
Field observation
Questions are answered from memory, and prior decisions are rediscovered through private history rather than shared artifacts.
Also observed
- I think we decided that in Slack.
- It is somewhere in Teams.
- I remember why we did this, but it is not written down.
Primary reading
What it usually indicates
Most likely underlying patterns when this signal shows up. Not a diagnosis, a starting hypothesis.
Usually indicates
Most likely underlying patterns when this signal shows up.
- weak documentation habits
- high delivery pressure crowding out knowledge capture
- culture that values speed over durable memory
Stakes
Why it matters
Institutional memory becomes fragile, onboarding slows, and incidents become harder to resolve.
Inspection
What to check next
Deliberate steps to confirm or disconfirm the primary reading above. Not a checklist. An order of inspection.
- runbooks
- ADRs
- handover docs
- doc trust patterns
Diagnostic questions
Questions to ask the team, or yourself, before concluding anything.
- What decisions would we lose if key people left?
- Which operational steps are recoverable without direct human recall?
- Are docs missing, stale, or ignored?
Progression
Under the signal
Where this pattern tends to come from, what's holding it up, and where it goes if nothing changes.
Leading indicators
What tends to show up first.
- onboarding depends heavily on shadowing
- same questions recur
- people search chat before looking for docs because docs are not trusted
Common root causes
What is usually sitting under the signal.
- underinvestment in documentation
- hero culture
- weak ownership of memory artifacts
Likely consequences
What happens if nothing changes.
- slow onboarding
- repeat mistakes
- incident confusion
- hero dependency
Look-alikes
Not what it looks like
Patterns that can be mistaken for this signal, and 'fix' attempts that make it worse.
- our team is small, so we do not need durable memory
Anti-patterns when responding
Responses that feel sensible and usually make the underlying pattern worse.
- assuming chat history is good enough as system memory
- writing docs after every crisis and never maintaining them
Context
Context and ownership
Where this signal surfaces, who sees it first, who can actually act, and how much runway there usually is before escalation.
Where it shows up
- distributed teams
- fast-growing orgs
- incident-heavy environments
Who sees it first
Before it escalates.
- new joiners
- incident responders
- engineering manager
Who can move on it
Not always the same as who notices it.
- tech lead
- engineering manager
medium-term
How much runway there usually is before the signal hardens into the underlying pattern.
AI impact
AI effects on this signal
How AI-assisted and AI-driven workflows tend to amplify or hide this signal.
AI amplifies
Ways AI tooling tends to make this signal louder or more common.
- AI can summarize chat history, which helps temporarily, but also reduces pressure to create authoritative shared artifacts.
AI masks
Ways AI tooling tends to hide this signal, so it keeps growing under the surface.
- Summaries can make fragmented memory look organized without fixing source truth.
Relationships
Connected signals
Related failure modes, decisions behind the signal, response playbooks, and neighboring red flags.