How do I apply the idea that unintended consequences of system changes?

The most direct way to practice is through a focused exercise: Before implementing your next system change, conduct a pre-mortem for unintended consequences. Write down the intended change and the intended consequence. Then systematically ask five questions: (1) Who else is affected by this change besides the intended target? What will they do differently? (2) What workarounds might people create to avoid the new constraint? (3) What positive behavior might this change accidentally discourage? (4) What negative behavior might this change accidentally encourage? (5) If this change succeeds completely at its intended goal, what new problem might the success create? For each answer, design a monitoring mechanism — a metric or observation that would detect the unintended consequence early enough to respond.

Common pitfall: Using the risk of unintended consequences as an argument against system change. Every system change has unintended consequences — but so does maintaining the current system. The status quo produces its own consequences, which are often severe but invisible because they are familiar. The failure mode is asymmetric risk assessment: treating potential unintended consequences of a proposed change as deal-breakers while ignoring the actual ongoing consequences of the current system. The correct comparison is not 'proposed change with its risks versus no change with no risks' — it is 'proposed change with its risks versus current system with its costs.'

This practice connects to Phase 84 (Systemic Change) — building it as a repeatable habit compounds over time.