Design early warning indicators for polarity drift — monitor each pole's characteristic downsides to trigger course-correction
Design early warning indicators for polarity drift by identifying the characteristic downsides of each pole, then monitor for those downsides to trigger course-correction before crisis.
Why This Is a Rule
Barry Johnson's polarity management framework identifies tensions that can't be resolved (Apply the problem-vs-polarity test — if new information can't make one side permanently win, manage the oscillation instead) — only managed through healthy oscillation between poles. The critical operational challenge is detecting when you've drifted too far toward one pole before the downsides become a crisis. Early warning indicators solve this by mapping each pole's characteristic dysfunction and monitoring for it.
Every polarity has a predictable failure pattern. The "autonomy" pole, over-focused, produces silos, inconsistency, and duplicated effort. The "alignment" pole, over-focused, produces bureaucracy, slow decisions, and stifled initiative. If you know these characteristic downsides in advance, you can watch for early signals: "We're seeing three teams build the same thing independently" triggers a shift toward alignment. "Approval processes are blocking all initiative" triggers a shift toward autonomy.
Without early warning indicators, polarity management is reactive — you oscillate only after one pole's downsides have become a crisis. With indicators, management becomes proactive — you correct before the crisis, maintaining a tighter oscillation around the healthy center.
When This Fires
- After identifying a tension as a polarity rather than a solvable problem (Apply the problem-vs-polarity test — if new information can't make one side permanently win, manage the oscillation instead)
- 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.