Dialogue process using IBIS, Shared Display, and Active Listening. Dialogue Mapping™ is a radically inclusive facilitation process that creates a diagram or 'map' (cf mind-map) that captures and connects participants' comments as a meeting conversation unfolds. It is especially effective with highly complex or “Wicked” problems that are wrought with both social and technical complexity, as well as a sometimes maddening inability to move forward in a meaningful and cost effective way. Dialogue Mapping™ creates forward progress in situations that have been stuck; it clears the way for robust decisions that last. It is effective because it works with the non-linear way humans really think, communicate, and make decisions.

crummy examples/case studies:

• http://cognexus.org/id26_m.htm#_dialog_mapping_reflections_on_an
• http://cognexus.org/id26_m.htm#the_dialog_mapping_experience

Compendium is key tool currently available.

book by Jeff Conklin ISBN:0470017686

Eugene Eric Kim article from 2001.

• and bits from 2004 on how he used it then.

2026: seeking case study

me: I'd like to read a detailed case study involving a topic I can understand and relate to, with enough detail to confirm the process works, focusing more on improved accuracy of understanding than "satisfaction with engagement".

GoogleGemini:

The following case study details a large public dialogue mapping session addressing a complex urban development problem: re-routing a high-traffic regional freight trucking lane away from a downtown core while preserving local business access. This scenario perfectly illustrates how the Issue-Based Information System (IBIS) structure explicitly forces a crowd out of rhetorical posturing and into a measurable, shared structural model—directly improving the accuracy of mutual understanding rather than just letting people vent.

📋 Case Overview: The "Byway 40" Congestion Project

• The Problem: Byway 40, a narrow four-lane arterial road, passes directly through a dense, historic downtown commercial district. Commuter traffic, pedestrian foot traffic, and heavy industrial freight trucks share the same space, resulting in accidents, structural damage to historic buildings from vibrations, and severe gridlock.
• The Stakes: High conflict. Trucking companies want fast transit; local retailers want foot-traffic safety but fear losing delivery access; historical preservationists want a total truck ban; residents want quiet streets.
• The Format: A 4-hour public dialogue session with 120 active participants, structured into 10 multi-stakeholder table pods, managed by 10 table mappers and 1 Master Facilitator/Synthesizer.

🛠️ Step 1: Establishing the Root Question (The Ground Truth)

Traditional public forums usually begin with an evaluation of a pre-baked proposal (e.g., "Should we build the North Bypass?"), which forces people into immediate "Yes" or "No" camps. The mapping session instead launched with a neutral, generative root question at the center of the screen:

❓ Root Question: How can we minimize the negative impacts of heavy freight transit through downtown while maintaining the economic vitality of local businesses?

By phrasing the root issue as a question that balances the friction points (safety/vibrations vs. economic access), every stakeholder could see their fundamental concern validated as a core element of the problem statement before a single argument was made.

🔬 Step 2: The Deconstruction (How Accuracy Trumps Rhetoric)

During the open-floor portion of the session, a resident stood up and delivered a highly emotional, five-minute monologue about a near-miss accident involving a delivery truck and a child, concluding that "all commercial trucks should be permanently banned from the city limits." In a standard town hall, this would trigger an angry counter-defense from a local grocery store owner about losing inventory, turning the room into an unresolvable ideological battle. The dialogue mapper, however, listened to the monologue and extracted its structural cognitive elements, mapping them live onto the screen:

• ❓ Sub-Question: What restrictions should be placed on freight truck traffic downtown?
• 💡 Idea A: Impose a total ban on all commercial trucks within the downtown perimeter.
  • ➕ Pro: Eliminates the safety risk to pedestrians on narrow sidewalks.
    • ➕ Pro: Halts structural vibration damage to historic facades.

The mapper then turned to the resident and asked: "Does this map accurately represent the logical structure of your argument?" The resident looked at the screen, saw their point visually secured, and sat down.

The Accuracy Shift

Because the resident’s argument was now cleanly captured on the board, the local grocery owner did not need to attack the resident's character or narrative. Instead, the business owner was naturally guided by the layout to address the Idea node directly, introducing a structural constraint:

• 💡 Idea A: Impose a total ban on all commercial trucks within the downtown perimeter.
• ➖ Con: Prevents inventory deliveries to 45 downtown retail and grocery businesses that lack rear alleyway access.
  • ➖ Con: Violates state highway funding regulations for Byway 40, risking a $4M annual infrastructure grant.

Why this improved accuracy: The crowd instantly shifted from an ideological battle ("Safety vs. Corporate Greed") to a structural problem-solving exercise. Everyone in the room now shared a highly precise, accurate understanding of why a total ban was structurally problematic, regardless of how they felt about it emotionally.

🔄 Step 3: Resolving Hidden Contradictions (The "Delivery" Breakthrough)

As the table pods mapped deeper into the issue, an apparent gridlock emerged: the logistics companies insisted they needed 24/7 route access, while residents insisted on peace and quiet. By mapping the specific rationale behind these claims, the session revealed a critical piece of misaligned data:

• ❓ Sub-Question: When should deliveries be permitted?
• 💡 Idea B: Restrict deliveries to nighttime hours (10:00 PM – 6:00 AM).
  • ➕ Pro: Removes heavy trucks from daytime commuter and pedestrian peak hours.
    • ➖ Con (from Residents): Creates disruptive noise pollution during sleeping hours.
    • ➖ Con (from Logistics Providers): Requires retail staff to be present overnight to accept deliveries, spiking labor costs.

Seeing this map, a logistics manager realized a vital distinction: "We don't actually need big 18-wheelers downtown at night. We just need to get the inventory from our regional hubs to the stores." This insight immediately opened up a completely new, targeted path on the map that bypassed the old gridlock:

• 💡 Idea C: Establish a "Micro-Consolidation Hub" outside the city center where 18-wheelers drop cargo, which is then brought downtown via quiet, low-profile electric delivery vans during daytime off-peak hours.
• ➕ Pro: Maintains freight efficiency for regional logistics.
  • ➕ Pro: Preserves daytime pedestrian safety and avoids nighttime noise.
  • ❓ New Sub-Question: Who will fund the real estate and operational costs of the micro-consolidation hub?

📊 The Outcome: Shared Mental Models vs. Group Aggreement

At the conclusion of the 4-hour session, the group had not completely voted on a final layout or signed a contract. However, they achieved a high-fidelity shared mental model of the problem landscape. The final mapped artifact provided explicit clarity on three fronts:

1. Elimination of Strawman Arguments: It became impossible for any group to pretend their opponents were simply being "unreasonable." The structural costs (the state funding rules, the lack of back alleys, the warehouse operational hours) were laid bare as objective facts on the canvas.
2. Explicit Information Gaps: The map clearly marked where the conversation could go no further without hard data. For instance, the node “Who funds the consolidation hub?” stood out as a critical open question, which allowed the city council to immediately commission a hyper-focused financial feasibility study rather than wasting time on vague public feedback surveys.
3. Accuracy in Next Steps: When the city planning department took the results to draft an official ordinance, they didn't just have a stack of messy comment cards saying "fix traffic." They possessed a deeply detailed, interconnected map detailing exactly how 15 different proposed solutions interacted with 40 distinct operational constraints.

source? https://medium.com/@paulculmsee/innovations-in-decision-making-on-a-major-infrastructure-project-35625d590dcd