Design early warning indicators for polarity drift…

When This Fires

• After identifying a tension as a polarity rather than a solvable problem (Apply the problem-vs-polarity test — if new information…)
• During organizational design when building management systems for known tensions
• When a team keeps swinging between extremes — they need structured oscillation, not more willpower
• During personal practice management when balancing competing priorities (depth vs. breadth, speed vs. quality)

Common Failure Mode

Monitoring only one pole's downsides. If you only watch for signs of too much autonomy (silos, inconsistency), you'll over-correct toward alignment every time and never notice when alignment becomes bureaucratic. Both poles need indicators. The healthy state is when neither pole's downsides are triggering — you're in the productive center.

The Protocol

(1) For a known polarity (e.g., autonomy vs. alignment), map each pole's positive results when attended to and negative results when over-focused. (2) For each negative result, design a specific, observable early warning indicator — not "things feel bureaucratic" but "average approval time exceeds 3 days" or "more than 2 teams request exceptions to the same process in one month." (3) Set monitoring cadence: weekly check of indicators for high-stakes polarities, monthly for lower-stakes ones. (4) When an indicator triggers, shift attention toward the opposite pole — not abandoning the current pole, but rebalancing. (5) Review and refine indicators quarterly as you learn what actually predicts drift in your specific context.