In complex or chaotic domains, review schemas more frequently — unpredictability generates more anomalies
In complex or chaotic Cynefin domains, increase schema review frequency beyond what the pace layer suggests because unpredictability generates more frequent anomalies requiring evaluation.
Why This Is a Rule
Snowden's Cynefin framework distinguishes four domain types by their relationship between cause and effect. In obvious/complicated domains, cause-effect is clear (obvious) or discoverable (complicated) — schemas hold reliably and the pace-layer cadence is sufficient. In complex domains, cause-effect is only visible retrospectively — schemas drift faster because the environment produces emergent behaviors that no prediction could have anticipated. In chaotic domains, cause-effect is absent — schemas become obsolete almost immediately.
This means pace-layer cadences (Map review frequency to pace layer: weekly for fast-changing, annually for governance, anomaly-only for foundational) are insufficient for complex and chaotic domains. An infrastructure-layer schema in a complicated domain can be reviewed quarterly. The same schema in a complex domain needs monthly or biweekly review because the unpredictability generates anomalies faster than quarterly reviews can catch.
The Cynefin adjustment increases review frequency above the pace-layer base: whatever the pace layer suggests, complex domains need 2x frequency and chaotic domains need continuous monitoring.
When This Fires
- When operating in complex environments (startups, rapidly changing markets, novel technology adoption)
- When schemas that worked last month keep producing unexpected results
- During organizational change, market disruption, or technology transitions
- When the rate of anomalies exceeds what the current review cadence can process
Common Failure Mode
Applying stable-domain review cadences to complex domains: "Quarterly review worked at my last company." But your last company was operating in a complicated domain with discoverable cause-effect. Your current startup is in a complex domain with emergent cause-effect. The same cadence produces schema staleness because anomalies accumulate between reviews.
The Protocol
When determining review cadence: (1) Classify the domain using Cynefin: is cause-effect clear (obvious), discoverable (complicated), retrospective (complex), or absent (chaotic)? (2) Apply the multiplier: obvious/complicated → use pace-layer cadence as-is. Complex → double the review frequency. Chaotic → continuous monitoring with triggered reviews. (3) If your anomaly log (Accumulate anomalies on a running list — trigger schema review at the count threshold, not at each one) is filling faster than your review cadence can process → the domain is more complex than you classified it. Increase frequency.