Form
Polarity map (four-field diagram) as image or digital board plus markdown with polarity description, benefits per pole, risks of overemphasis, observable warning signs and balancing actions with owner and trigger.
RunsheetSystems Thinking
Polarity Mapping
ComplexityMedium
Time1-2 h
Participants3-12
FormatWorkshop
MaturityEstablished
01
Preparation
What needs to be ready before start
Materials
Whiteboard or Miro board with a four-field grid (two poles horizontally, Benefits at the top and Risks of overemphasis at the bottom); sticky notes in two colors for the two poles; markers; timer.
People / roles
One facilitator with polarity experience who defines poles cleanly and balances the discussion; three to twelve participants with a position on the tension; one scribe for warning signs and balancing actions.
Pre-read
Description of the tension in 2-3 sentences; previous attempts to solve it as a problem and why it returned; examples of both poles in daily work; affected stakeholders.
Time needed
1-2 h
Setup
Prepare a four-field grid, Pole A on the left, Pole B on the right. Benefits at the top, risks of overemphasis at the bottom. Rule: the tension is a polarity, not a problem. There is no single right end state.
02
Core question
The one question this method answers
Which poles are in a lasting tension, what benefits does each pole offer, and which warning signs and actions keep the pendulum in balance?
03
Flow
Marker: Phase
| Step | Duration | Action | Hint |
|---|---|---|---|
1Phase 1: Polarity instead of problem | 10-15 min | Check together whether the tension really is a polarity: both poles are needed, the tension is lasting, and there is no clearly right pole. If yes, name both poles. | If one pole is clearly preferred and the other is only a transitional workaround, it is a problem, not a polarity. Switch methods. |
2Phase 2: Benefits per pole | 20-25 min | Collect benefits per pole (upper left and upper right fields). Capture at least five per pole. Ground them in concrete examples. | If one pole receives far fewer benefits, the group is not balanced. Introduce a devil's-advocate role for the underrepresented pole. |
3Phase 3: Risks of overemphasis | 20-25 min | Ask for each pole: what happens if this pole is pursued alone and the other is neglected? Fill the lower quadrant per pole. Use examples from real incidents where this happened. | Risks of overemphasis are the real warning signs. They show when the pendulum has swung too far. |
4Phase 4: Formulate warning signs | 15-20 min | Define concrete, observable warning signs per pole (for example metrics, behavior patterns, mood) that indicate the pendulum has swung too far toward this pole. At least three per pole. | Warning signs must be measurable or clearly observable. "It feels wrong" is not a warning sign; "time-to-decision exceeds 14 days" is one. |
5Phase 5: Balancing actions | 15-20 min | Define one concrete action per warning sign that pulls toward the other pole. Name an owner and trigger for every action. | Actions are not executed all at once, but when a warning sign appears. The owner must be in a position to initiate the action. |
04
Artifact
What comes out at the end
Versioning / ownership
Create one entry per polarity with date. Whenever a balancing action is triggered, add an update section: warning sign, action, effect. The map remains a living document, not a one-off workshop output.
Tool alternatives
- Miro with polarity map template
- Whiteboard with photo export
- Notion page with one table per quadrant
- Confluence page in the strategy space
polarity-mapping-working-template.md
Compact working template for Polarity Mapping with context, input, output artifacts, and next step.
Polarity Mapping Canvas
Context
What is this method used for?
Core question
Which question should be answered at the end?
Input
Which data, observations, or materials are available?
Working area
- Area 1:
- Area 2:
- Area 3:
- Relationships / patterns:
Output artifacts
- Polarity Map:
- Warning Signs:
- Balance Actions:
Open questions
- ...
Next step
Owner, date, success signal.
05
Example output
Concrete filled scenario, fictional example
polarity-mapping-beispiel.md
Concrete filled scenario, fictional example
Polarity Map - Team Autonomy vs. Alignment (2026-05-18)
Polarity: Team autonomy vs. cross-team alignment.
Benefits of autonomy: Fast decisions, high motivation, closeness to context, ownership of outcomes, innovation.
Benefits of alignment: Consistent customer experience, less duplication, shared standards, economies of scale, easier mobility of people.
Risks of overemphasizing autonomy: Inconsistent UI, duplicated infrastructure, diverging roadmaps, knowledge silos.
Risks of overemphasizing alignment: Decision paralysis, many cross-team meetings, lack of ownership, innovation gets suffocated in the center.
Warning signs autonomy is too high: Three or more UI components for the same function, tickets between teams exceed 20/month, architecture review reports 3+ duplicates.
Warning signs alignment is too high: Time-to-decision in cross-team meetings exceeds 14 days, share of cross-team meetings in calendars exceeds 30%, engagement score below 6/10.
Balancing actions:
- At 3+ UI duplicates: convene design system review. Owner: @julia.
- When cross-team meeting share exceeds 30%: team API review. Owner: @marcus.
06
Pitfalls
Recognize symptoms and steer against them
Trap
The polarity is actually a problem
Symptom
One pole is clearly preferred; the other is treated as a transition or mistake.
What to do
Take Phase 1 seriously. If both poles are not permanently needed, it is a problem, not a polarity. Choose another method.
Trap
Unbalanced benefit collection
Symptom
One pole gets 12 benefits, the other 3. The map is distorted.
What to do
Use a devil's advocate for the underrepresented pole. If needed, repeat Phase 2 for that pole with different participants.
Trap
Warning signs are not observable
Symptom
Warning signs read "when it goes wrong" or "when it becomes too much".
What to do
Require a metric or clearly observable behavior for every warning sign. If it is not measurable, it is gut feeling rather than a warning sign.
Trap
Balancing actions without triggers
Symptom
Actions are kept as a list without a condition for when to use them.
What to do
Name a trigger for every action ("when warning sign X is reached"). Actions without triggers are either never applied or applied constantly, both wrong.
Trap
The method is used once and forgotten
Symptom
The map sits in Confluence, nobody revisits it, warning signs are missed.
What to do
Define a review cadence, for example quarterly. The owner is responsible for keeping warning-sign metrics visible on a dashboard.
07
Stop criteria
Done signals checkable in under a minute
The tension is actually a problem; one pole is clearly preferred.
The poles cannot be named clearly after 20 min; polarity is not recognizable.
Only one side is represented in the room, and the benefits of the other pole are not seen.
The workshop is scheduled for under 45 min, so the five phases cannot be run.
Warning signs remain consistently vague, so the map cannot be operationalized.
No person with leverage for balancing actions is present, so actions will dissipate.
Finished the runsheet?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.