Dialogic Leadership: Reframing Polarities in Teams

Dialogic leadership can help a team examine a recurring tension without turning every conversation into a contest between two departments. The work is to understand what each position protects, distinguish facts from assumptions, and make a practical decision while keeping the interdependence visible.

William Isaacs’ work on dialogue emphasizes listening, respecting, suspending assumptions, and voicing what matters. Polarity mapping is a related way to examine interdependent needs, often associated with Barry Johnson. These are distinct contributions. Neither means that every conflict is a polarity or that a team can replace necessary decisions with endless conversation.

A decision to make or a tension to manage?

The same issue may contain both a decision and a continuing tension. A product release needs a launch decision now and a continuing way to monitor delivery speed and service quality.

Notice the quality of the conversation

A team can sound collaborative while repeating fixed positions. Sales argues for speed, product argues for quality, and each person listens mainly for something to rebut. A facilitator can slow the pattern by asking participants to describe their reasoning and what they fear losing.

Suspending an assumption means making it available for examination, not pretending to have no view. A sales leader might say: “I assume delaying the release will put the renewal at risk. Here is the customer message behind that view.” A product leader can then discuss the evidence rather than respond to a claim that engineering simply does not care about revenue.

Do not rank participants as occupants of a higher or lower conversational field. Frameworks can help the facilitator notice a pattern, but labeling a person “stuck in debate” may reproduce the very defensiveness you are trying to address. Describe observable behavior and invite a useful change. The companion guide to suspending reactive judgment develops this listening practice.

Use conversational roles without fixing people into types

David Kantor’s four-player model distinguishes conversational actions such as moving, following, opposing, and bystanding. Isaacs discusses this work in the dialogue tradition. A useful practical question is whether the conversation has room for proposing, supporting, challenging, and noticing the process.

A team that proposes endlessly but never commits may need a clear decision. A team that follows immediately may need a genuine challenge. Someone noticing that two proposals rely on different definitions can be making an important contribution even when they are not advocating either option.

Treat these as actions people can take, not identities or personality scores. Invite an absent perspective without assigning it to a reluctant person. A quiet participant might prefer a written observation before speaking, and a senior leader may need to hold back long enough for others to contribute.

• Propose: put a possible direction on the table.
• Support: help clarify or develop a direction.
• Challenge: surface risks, contradictions, or an alternative.
• Observe: name a pattern or assumption the group may be missing.

An example: speed and reliability in a product decision

The following fictional exchange shows a facilitator connecting two concerns without forcing agreement about the release date.

Sales leader: We have to release next month. Waiting is not an option.

Product leader: That is exactly how we create support problems.

Facilitator: Before deciding the date, could each of you name what you are trying to protect?

Sales leader: Customer confidence and the renewal. We made a commitment.

Product leader: Customer confidence too. A failure in the first week would damage it.

Facilitator: You both name confidence, with different risks. What evidence do we have about the commitment and the likely failure?

Sales leader: The customer needs a working export feature, not every feature on the roadmap.

Product leader: Then we can assess a smaller release. We need to validate the export volume first.

Facilitator: Who will check that evidence, by when, and who makes the final launch decision?

The dialogue has clarified a possible option and a missing fact. It has not proven that every speed-quality conflict can be resolved through a smaller release. The useful result is a more specific question, a responsible owner, and an explicit decision path.

Facilitate a bounded conversation about a recurring tension

1. Define the issue and authority. State what the team can decide, what is fixed, and who will make the decision if agreement is incomplete.
2. Name the two needs in neutral language. Use terms participants recognize, such as consistency and local flexibility. Avoid framing one side as sensible and the other as selfish.
3. Explore benefits and overuse. Ask what each side makes possible and what happens when the team pursues it while neglecting the other.
4. Examine assumptions and evidence. Invite examples, exceptions, and information still needed. Make uncertainty visible.
5. Choose actions and indicators. Agree a small practical change and early signs that the balance is becoming unhelpful.
6. Close with a decision and review point. Record responsibility, unresolved questions, and the date for revisiting the pattern.

Dialogue needs enough time for inquiry and enough structure for action. A ninety-minute offsite cannot guarantee a new team culture, particularly where incentives or authority continue to reward one-sided behavior.

A simple polarity worksheet

These entries are illustrations, not a verdict on the team. Ask participants to revise them using their own situation. A team may discover that the apparent polarity is partly a resource constraint or a disagreement about the customer’s needs. Let the worksheet reveal a better question rather than forcing every detail into four boxes.

Choose indicators the group can observe. “Too much speed” is vague; “the same customer-impacting issue recurs in three releases” is clearer. Avoid using the indicators as weapons against a department. Agree how the team will respond when a warning sign appears.

Make participation possible across power differences

A junior participant may remain silent because a senior colleague has already declared the answer. Inviting them to be courageous does not remove that consequence. Give people time to think independently, collect written views where appropriate, and ask the senior leader to listen before responding.

For asynchronous work, post the decision question, relevant facts, and the deadline. Ask people to distinguish observations, interpretations, and proposals. Summarize areas of agreement and the actual remaining dispute before the decision-maker acts. A long message thread is not automatically a dialogue.

Where the conflict includes bullying, discrimination, or retaliation, use the appropriate organizational process. A facilitated polarity conversation should not make an affected person responsible for balancing the benefit of misconduct against its harm. Dialogue can support understanding while accountability remains necessary.

In Coachful, a team resource or program can hold the agreed worksheet and follow-up actions when appropriate to the engagement. Keep personal coaching reflections separate from the shared team record. Record what the group agreed, not a speculative psychological explanation of each participant.

Sources and practical limits

Foundational reading includes William Isaacs’ Dialogue and the Art of Thinking Together, David Kantor’s work on conversational actions, and Barry Johnson’s work on polarity management. Academic discussion of the dialogue tradition appears in Negotiation Journal. The worksheet here is an illustrative coaching aid, not a standardized assessment.

Decide when to stop exploring and make the decision

A team can use the language of dialogue to postpone an uncomfortable choice. Before the conversation, agree what would count as enough understanding to decide. That may include a small set of facts, the main risks, the available options, and the views of the people accountable for implementation.

In the product-release example, the team can identify the export feature the customer actually needs, the evidence required to assess its reliability, and the person authorized to approve the launch. Once that evidence is available, the decision-maker should decide. More rounds of personal reflection may not improve the choice.

If the deadline arrives with incomplete information, state the uncertainty and use the agreed decision rule. A decision under uncertainty can still be responsible. Record what would trigger a review so the group does not have to pretend the choice is permanently correct.

After the decision, distinguish commitment to implementation from agreement with every assumption. A participant can say, “I still see the risk differently, and I will carry out the agreed plan while monitoring the indicator we named.” That preserves useful disagreement without reopening the entire discussion in every subsequent meeting.

Revisit the polarity when conditions change

A balance that worked for a small team may become unsuitable as the organization grows. Local flexibility may initially support quick customer responses; later, inconsistent decisions may create confusion. Do not treat the original worksheet as a permanent answer. Use it to notice when the benefits and costs have changed.

Schedule a review around a meaningful event, such as the next two releases or the first month of a revised process. Ask which indicators appeared and whether the response was useful. Invite the people affected by implementation, not only those who attended the original leadership conversation.

If one department repeatedly absorbs the cost of the chosen balance, examine workload and incentives. A polarity map can make interdependence visible, but it does not make an unfair allocation fair. The next step may be changing resources or authority rather than asking the same people to become more appreciative of the tension.

Prepare the facilitator’s closing summary

End with a short summary that participants can correct: the decision made, the needs it seeks to serve, the main uncertainty, the owner, and the review condition. Read it aloud or show it in writing. Ask whether it accurately reflects the discussion, rather than asking only whether everyone is happy.

For example: “We will assess the smaller release against the agreed export requirement. Product will report the reliability evidence on Thursday. Sales will confirm the customer commitment. The launch owner will decide on Friday. If the essential check fails, the launch date will be reconsidered.” This summary turns a broad tension into coordinated work.

Keep unresolved dissent visible where relevant. Recording a disagreement fairly can help the group return to it with new evidence, rather than treating it as a personal obstacle that should have disappeared during the offsite.

Frequently asked questions

How is a polarity different from a problem?

A polarity involves interdependent needs that remain relevant over time, such as consistency and flexibility. A problem may require a specific decision or correction. Check the situation rather than assuming every disagreement has two equally necessary sides.

Why do teams repeat the same debate?

They may have different information, incentives, assumptions, or authority. Explore those conditions. Do not diagnose the cause solely from a conversational framework or assume that better listening removes all structural conflict.

How can a quieter participant contribute?

Offer thinking time, written input, clear turn-taking, and an invitation that allows passing. Address senior behavior and consequences for dissent. Do not treat silence as lack of insight or force personal disclosure.

Can dialogue work asynchronously?

Some inquiry can happen in writing when the question, evidence, participation expectations, and decision deadline are clear. Complex or emotionally charged misunderstandings may still benefit from a facilitated live conversation.

What does suspending certainty mean?

It means holding your view in a way that others can examine: naming assumptions, sharing evidence, and remaining open to revision. It does not require abandoning standards, expertise, or the responsibility to decide.

Reframing is useful when it helps a team see the issue more accurately and choose a better next action. Keep the conversation connected to evidence, authority, and the work the team must actually do.