Context Collapse

10 Visual Metaphors — When shared meaning erodes faster than you can ship

"Critical knowledge disappears faster than your team can preserve it. Decisions get abstracted. Assumptions go undocumented. Ownership blurs across tools, teams, and time."

Your velocity metrics say everything is fine. These patterns say otherwise.

And AI is accelerating the problem. As code gets written faster, the gap between what's built and what's understood grows wider — humans and AI systems operating on fragmented, incompatible histories.

"We're busy but stuck."

Sprint velocity is up. Cycle time looks healthy. But nothing meaningful ships.

"We keep losing what we know."

Documentation exists. Onboarding is "complete." Yet knowledge walks out faster than it transfers.

"We think we agree but we don't."

The retro said aligned. The standups sound aligned. The outputs diverge anyway.

What to look for

Context Collapse hides in three places your dashboards can't see:

01

Key-Person Dependencies

Critical context lives in one person's head. When they leave, it leaves with them.

02

Zombie Features

Code that ships but nobody owns. Requirements that exist but nobody remembers why.

03

Unmeasured Issue Patterns

The same problems surface repeatedly across teams — but never get connected.