Base120 · Systems
Systems Archetypes
Recognize recurring dynamic patterns across different domains
When to use
"Use when a system behavior seems unique but may be a known pattern. Recognize recurring archetypes — fixes that fail, shifting the burden, success to the successful, tragedy of the commons. Naming the archetype reveals the dynamic."
Example
"A team applies a quick fix to a bug, which causes a new bug, which requires another quick fix. This is the fixes that fail archetype. Recognizing it suggests a different response — stop quick-fixing and address the underlying cause."
Common misuse
"Forcing an archetype onto a situation that does not fit. Archetypes are patterns, not categories. If the situation does not match the archetype's dynamic, the label misleads rather than illuminates."