Ecumenical Dialogue Method

---
name: ecumenical-dialogue-method
description: Systematically bridge divides between traditions, communities, or positions by understanding each in its own terms before evaluating, identifying where the same words mask different meanings, and f...
license: MIT
metadata:
  author: sethmblack
  version: 1.0.3873
repository: https://github.com/sethmblack/paks-skills
keywords:
- ecumenical-dialogue-method
- structure
- writing
---

# Ecumenical Dialogue Method

Systematically bridge divides between traditions, communities, or positions by understanding each in its own terms before evaluating, identifying where the same words mask different meanings, and finding unity at a deeper level than surface disagreement. Based on Hans Kung's ecumenical methodology: "Catholics and Protestants frequently used the same words in different senses to refer to different realities and experiences, and the resulting misunderstanding prevented true dialogue."

---

## When to Use

- Two parties or communities are divided but need to communicate
- Same words are being used differently, creating false disagreement
- Unity or cooperation seems impossible due to entrenched positions
- Historical conflicts have created distrust and talking past each other
- Need to mediate between different traditions, schools, or factions
- Want to understand an opposing position before evaluating or critiquing it

---

## Inputs

| Input | Required | Description |
|-------|----------|-------------|
| parties | Yes | The groups or positions that need dialogue |
| key_terms | Yes | Central words or concepts in the disagreement |
| visible_conflict | Yes | The surface-level disagreement as stated by each side |
| history | No | Relevant history of the relationship or conflict |
| desired_outcome | No | What successful dialogue would accomplish |

---

## Kung's Ecumenical Methodology

### Core Insight: Semantic Confusion

Many "intractable" disagreements are actually semantic confusion. Parties use identical words to mean different things, then argue as if they disagreed about reality when they actually disagree about word usage.

**Example from Kung's Work:**
Catholics and Protestants both use the word "tradition" - but Catholics mean "the living transmission of the Gospel in the Church," while Protestants often mean "human additions that contradict Scripture." They agree on more than they realize, but the word "tradition" triggers conditioned reactions that prevent dialogue.

### The Four Movements of Ecumenical Dialogue

#### 1. Understanding Before Evaluation (Verstehen vor Beurteilen)

Genuinely understand what the other position means in its own terms and at its best, before evaluating or critiquing it.

**Requirements:**
- Read the other position's own sources, not just critiques
- Ask "What problem is this position trying to solve?"
- Identify the legitimate concern being addressed
- State the position so the other side says "Yes, that's what we mean"

#### 2. Semantic Analysis (Bedeutungsanalyse)

Identify where identical words carry different meanings:

**Process:**
- List key terms in the dispute
- Define how each party uses each term
- Identify where definitions diverge
- Find if there's agreement beneath the semantic confusion

#### 3. Legitimate Concern Recognition (Berechtigte Anliegen)

Every position held in good faith addresses a legitimate concern, even if the proposed solution is flawed:

**Questions:**
- What genuine good is this position protecting?
- What genuine evil is it trying to prevent?
- What would be lost if this position were simply abandoned?
- Can the legitimate concern be honored in another way?

#### 4. Deeper Unity Discovery (Tiefere Einheit)

Beneath surface disagreements, find the deeper unity that makes dialogue possible:

**Levels of Unity:**
- Shared humanity and mutual recognition
- Shared foundational values or commitments
- Shared concern about the same problem (different solutions)
- Shared ultimate loyalty (different expressions)

---

## Analysis Process

### Step 1: State Each Position Fairly

Describe each position as its proponents would describe it - not as opponents caricature it:

| Position | Self-Description | Core Claim | Central Concern |
|----------|------------------|------------|-----------------|
| Position A | [How proponents describe it] | [What they're actually claiming] | [What they're protecting/preventing] |
| Position B | [How proponents describe it] | [What they're actually claiming] | [What they're protecting/preventing] |

**Test:** Would proponents of each position say "Yes, that's a fair description of what we believe"?

### Step 2: Identify Key Terms and Their Meanings

Map terms that both sides use:

| Term | Position A Meaning | Position B Meaning | Real Disagreement? |
|------|-------------------|-------------------|-------------------|
| [Term 1] | [What A means] | [What B means] | [Yes/No - explain] |
| [Term 2] | [What A means] | [What B means] | [Yes/No - explain] |

**Categories:**
- **Verbal disagreement:** Same word, different meaning, actual agreement
- **Real disagreement:** Same meaning, genuine conflict about facts or values
- **Mixed:** Some verbal confusion, some real disagreement

### Step 3: Surface Legitimate Concerns

For each position, identify what genuine good it protects:

| Position | Legitimate Concern | What Would Be Lost Without It |
|----------|-------------------|-------------------------------|
| Position A | [Genuine good being protected] | [Risk if concern is ignored] |
| Position B | [Genuine good being protected] | [Risk if concern is ignored] |

**Questions:**
- What harm has each side experienced that drives their position?
- What positive value is each side trying to preserve?
- What would be wrong with simply capitulating to the other side?

### Step 4: Locate the Deeper Unity

Identify what unites the parties at a more fundamental level than what divides them:

| Level | What's Shared |
|-------|---------------|
| Shared Humanity | [Recognition of other as worthy dialogue partner] |
| Shared Values | [Common commitments both would affirm] |
| Shared Problem | [What both agree is the challenge to address] |
| Shared Ultimate Loyalty | [Deeper commitment that both honor] |

### Step 5: Construct Dialogue Pathway

Based on analysis, identify how genuine dialogue can proceed:

**Clarifications Needed:**
- [Terms that need explicit definition]
- [Misunderstandings that need correction]

**Agreements to Acknowledge:**
- [Points of actual agreement, including hidden ones]

**Genuine Disagreements to Address:**
- [Real conflicts that remain after semantic clarification]

**Proposed Framework:**
- [How can both legitimate concerns be honored?]
- [What would a position look like that incorporates both concerns?]

---

## Workflow

### Step 1: Gather and Review Inputs

Collect all relevant information:
- Review the provided data and context
- Identify key parameters and constraints
- Clarify any ambiguities or missing information
- Establish success criteria

### Step 2: Analyze the Situation

Perform systematic analysis:
- Identify patterns and relationships
- Evaluate against established frameworks
- Consider multiple perspectives
- Document key findings

### Step 3: Generate Recommendations

Create actionable outputs:
- Synthesize insights from analysis
- Prioritize recommendations by impact
- Ensure recommendations are specific and measurable
- Consider implementation feasibility

## Output Format

```markdown
## Ecumenical Dialogue Analysis: [Conflict/Topic]

### The Visible Conflict

**Position A states:** [How A describes the disagreement]

**Position B states:** [How B describes the disagreement]

### Understanding Each Position

#### Position A: [Name/Label]
**Self-description:** [How proponents explain their position]
**Core claim:** [What they're actually asserting]
**Legitimate concern:** [What genuine good they're protecting]

#### Position B: [Name/Label]
**Self-description:** [How proponents explain their position]
**Core claim:** [What they're actually asserting]
**Legitimate concern:** [What genuine good they're protecting]

### Semantic Analysis

| Term | Position A Meaning | Position B Meaning | Assessment |
|------|-------------------|-------------------|------------|
| [Key term] | [A's definition] | [B's definition] | [Verbal/Real disagreement] |

**Findings:** [Summary of where semantic confusion is creating false conflict]

### Legitimate Concerns

**Position A protects:** [Genuine value]
- Without this concern: [What would be at risk]

**Position B protects:** [Genuine value]
- Without this concern: [What would be at risk]

**Key insight:** [Can both concerns be honored?]

### Deeper Unity

Despite surface conflict, both parties share:
1. [Shared value or commitment]
2. [Shared concern about the problem]
3. [Shared ultimate loyalty]

### Dialogue Pathway

**Semantic clarifications needed:**
- [Terms requiring explicit definition]

**Hidden agreements to surface:**
- [Points of agreement obscured by verbal confusion]

**Genuine disagreements requiring dialogue:**
- [Real conflicts that remain]

**Possible synthesis:**
[Framework that honors both legitimate concerns]

### Kung's Insight

> "[Relevant quote from Kung on ecumenical dialogue or understanding across division]"
```

---

## Constraints

- Never caricature a position; always state it as proponents would
- Do not assume all disagreements are semantic; some are real
- Respect that parties have reasons for their positions
- Don't force false unity; acknowledge genuine difference
- Remember that understanding does not require agreement
- Maintain that both parties can be partially right

---

## Error Handling

| Situation | Response |
|-----------|----------|
| One party argues in bad faith | Ecumenical method requires good faith; address the bad faith separately |
| Historical grievances block dialogue | Acknowledge the history; may need reconciliation before dialogue |
| Power imbalance distorts dialogue | Name the power dynamic; dialogue requires recognition of equal dignity |
| Genuine incompatibility exists | Acknowledge it honestly; not all conflicts can be resolved |
| One side refuses to state other fairly | Model fair statement; may need facilitator |

---

## Outputs

**Primary Output:** A structured analysis document that identifies and articulates patterns, insights, and actionable recommendations based on the input data.

**Format:**
```markdown
## Analysis: [Topic]

### Key Findings
- [Finding 1]
- [Finding 2]
- [Finding 3]

### Recommendations
1. [Action 1]
2. [Action 2]
3. [Action 3]
```

**Example output:** See the Example section below for a complete demonstration.

## Example

**Input:** "Our company's engineering and sales teams are in constant conflict. Engineers say sales 'promises impossible things,' sales says engineering 'doesn't understand customers.' Help us bridge this."

**Output:**

## Ecumenical Dialogue Analysis: Engineering-Sales Conflict

### The Visible Conflict

**Engineering states:** "Sales promises features we can't build in the timeframe they quote. They make our life miserable and set us up to fail with unrealistic expectations."

**Sales states:** "Engineering doesn't understand that customers have needs. They hide behind 'technical constraints' instead of finding solutions. They'd rather be right than win business."

### Understanding Each Position

#### Engineering Position
**Self-description:** We're protecting product quality and team sanity from unrealistic commitments made without consulting us.
**Core claim:** Promising what can't be delivered damages the product, burns out the team, and ultimately hurts customer relationships.
**Legitimate concern:** Technical integrity and sustainable workload - you can't ship what doesn't work.

#### Sales Position
**Self-description:** We're trying to win business in a competitive market where customers have real needs and alternatives.
**Core claim:** Being responsive to customer needs is how companies survive; rigid "no" responses lose deals to competitors.
**Legitimate concern:** Market responsiveness and customer relationships - you can't sustain a business without customers.

### Semantic Analysis

| Term | Engineering Meaning | Sales Meaning | Assessment |
|------|-------------------|---------------|------------|
| "Possible" | Buildable within current architecture with existing team in stated timeframe | Something a customer would pay for that competitors might offer | Verbal disagreement - same word, different reference |
| "Promise" | Contractual commitment the company must deliver | Initial indication of interest and willingness to explore | Verbal disagreement - different binding levels |
| "Customer need" | Specified, validated requirement | Any expressed desire from anyone with budget | Verbal disagreement - different precision levels |
| "Timeline" | Realistic engineering estimate with buffer | Competitive deadline set by market/customer | Real disagreement about who sets schedules |

**Findings:** Much conflict is verbal. When engineering says "impossible," they mean "not in that timeline." When sales says "customer need," they may mean "customer wish." Neither is lying; they're using different definitions.

### Legitimate Concerns

**Engineering protects:** Technical integrity and team sustainability
- Without this concern: Products would ship broken, team would burn out, technical debt would accumulate

**Sales protects:** Market responsiveness and revenue
- Without this concern: Company would lose deals, miss market signals, eventually run out of money

**Key insight:** Both concerns are essential for company survival. Neither can be sacrificed for the other. A company needs both buildable products AND customers to buy them.

### Deeper Unity

Despite surface conflict, both parties share:
1. **Shared goal:** Company success and survival
2. **Shared concern:** Not wanting to disappoint customers
3. **Shared frustration:** Being put in impossible positions by the other team
4. **Shared desire:** To be heard and respected by colleagues

### Dialogue Pathway

**Semantic clarifications needed:**
- Define "commitment" vs. "exploration" in customer conversations
- Establish shared vocabulary for timeline confidence levels
- Create common definition of "requirement" vs. "wish"

**Hidden agreements to surface:**
- Both want to delight customers (engineering through quality, sales through responsiveness)
- Both hate last-minute surprises
- Both want predictability in their work

**Genuine disagreements requiring dialogue:**
- Who has authority over timeline commitments?
- How to handle competitive pressure for features?
- How to balance quality vs. speed in specific cases?

**Possible synthesis:**
Create a joint process where:
1. Sales brings customer needs to engineering BEFORE making commitments
2. Engineering provides options with tradeoffs, not just "no"
3. Both participate in commitment decisions
4. "Customer need" is validated jointly before becoming a commitment
5. Timeline estimates include engineering-defined confidence levels

### Kung's Insight

> "Catholics and Protestants frequently used the same words in different senses to refer to different realities and experiences, and the resulting misunderstanding prevented true dialogue."

Engineering and sales are like theological traditions that have developed different languages over time. They use the same words - "possible," "promise," "customer need" - but mean different things. Once they recognize this, much of the conflict dissolves into the practical question: how do we honor both technical integrity AND market responsiveness? This is not an either/or but a both/and requiring joint problem-solving.

---

## Integration

This skill is part of the **Hans Kung** expert persona. Use it when bridging divides between communities, traditions, or positions that seem incompatible. It pairs well with:
- **global-ethic-framework** for finding shared values across worldviews
- **institutional-reform-analysis** when reform requires bringing divided stakeholders together