Canonical problem patterns
Business systems rarely fail randomly.
Across industries and tools, the same structural problems appear again and again. Not as bugs. Not as user mistakes. But as recurring failure modes that emerge when structure, meaning, rules, or processing drift out of alignment with reality.
Each pattern links to a dedicated article in this folder.
Each pattern also connects back to one or more structural lenses:
How to use this page
You can use this index in three ways:
- Recognition — identify what you are experiencing
- Orientation — understand how problems relate structurally
- Navigation — jump directly to the canonical article
Patterns frequently reinforce one another. They are distinct, but rarely isolated.
The patterns
1. Semantic drift (multiple truths)
When the same concept exists in multiple places but no longer means the same thing everywhere.
Reports disagree even though field names match. Integrations succeed technically, but decisions conflict.
Touches lenses:
Information, Integration
2. Model vs reality mismatch
When the system structure does not reflect how the business actually works.
Users adapt to the model instead of the model reflecting reality.
Touches lenses:
Information, Interaction
3. Rigid structure disguised as flexibility
When systems appear configurable but collapse under real variation.
Options multiply, but the underlying assumption remains fixed.
Touches lenses:
Information
4. Patchwork integration (manual glue)
When humans and exports compensate for missing structural connections.
Spreadsheets and manual reconciliation become the invisible glue between systems.
Touches lenses:
Information, Integration
5. Shadow systems via duplication
When copies of data become unofficial systems of record.
Exports harden into parallel realities.
Touches lenses:
Integration
6. Loss of trust in the system
When users stop trusting outputs because things feel inconsistent or wrong.
Manual validation becomes routine.
Touches lenses:
Information, Interaction
7. Information exists but can’t be assembled
When data is present but locked behind fixed views.
The system knows the answer, but users cannot form it.
Touches lenses:
Interaction
8. Human compensation
When people perform invisible work to keep the system functioning.
Effort replaces structural enforcement.
Touches lenses:
Interaction, Rules
9. Rules live outside the system
When policies exist but are not structurally enforced.
Compliance depends on attention rather than structure.
Touches lenses:
Rules
10. Automation collapses on exceptions
When automation works only in the happy path.
Reality deviates, and automation stops.
Touches lenses:
Rules, Processing
11. Cascading side effects
When a small change triggers unexpected consequences elsewhere.
Hidden dependencies amplify local adjustments.
Touches lenses:
Information, Processing
12. Threshold effects (hidden limits)
When behavior changes suddenly after crossing a boundary.
Everything appears stable — until it isn’t.
Touches lenses:
Processing