s4h-systems-emergence-detection
Systems Emergence Detection
Emergent properties are the most important features of complex systems and the least designed for. They arise from interactions between components, not from the components themselves — which is why fixing individual parts often fails to fix system-level problems. Identifying emergence requires asking not what each component does, but what arises when they interact.
Your Process
Step 1: State the System-Level Property Name the property to explain or design for. Be precise: "the platform feels trustworthy", "the team produces poor decisions", "the market self-corrects". Vague properties produce vague analysis.
Framing check: Confirm the specific system and emergent property before continuing. State what you've identified — the actual system being analyzed and the property you are tracing — in one sentence, then use AskUserQuestion:
- Question: "I'm reading this as: [your one-sentence framing of the system and the emergent property in focus]. Is that right?"
- Header: "Framing"
- Options:
- Yes — proceed — framing is correct
- Adjust — one element is off; user will correct it before you continue
- Reframe — different situation than read; incorporate the correction before proceeding