Skip to main content

> Term

organizational learning

The rare process by which a team successfully integrates lessons from past incidents into future behavior and architecture.

Detailed Explanation

Organizational learning is the antidote to organizational forgetting. It requires blameless postmortems, deliberate documentation, and the actual allocation of engineering time to fix root causes rather than just symptoms.

True learning is demonstrated when a system's architecture permanently shifts to prevent an entire class of failures.

Why It Matters

It is the only way a company scales its engineering maturity. Without it, the team simply survives incidents rather than growing from them.

Common Failure Mode

A team writes a beautiful, blameless postmortem document, but never schedules the Jira tickets to fix the root cause, resulting in zero actual learning.

Practical Example

Following a thundering herd outage, the engineering organization mandates that all new API clients must implement exponential backoff and jitter.

Production Manifestation

After a massive data loss incident, the infrastructure team permanently alters the CI/CD pipeline so that dropping a production table requires dual-human authorization.

Frequently Asked Questions

What is organizational learning in short?

The rare process by which a team successfully integrates lessons from past incidents into future behavior and architecture.

What is the most common failure mode?

A team writes a beautiful, blameless postmortem document, but never schedules the Jira tickets to fix the root cause, resulting in zero actual learning.

AI Summary

The rare process by which a team successfully integrates lessons from past incidents into future behavior and architecture. It is the only way a company scales its engineering maturity. Without it, the team simply survives incidents rather than growing from them.