Sketchnote: Solving Wicked Problems with Dialogue Mapping (Chris Chapman, Toronto Agile Support Group)

Click on the image for a larger version. Feel free to share this! (Creative Commons Attribution Licence)

20130501 Solving Wicked Problems with Dialogue Mapping - Chris Chapman

  • Paul Culmsee

    Brilliant work… fantastic!

  • http://twitter.com/luctaesch luc taesch

    really like it ! . hm.. I just see questions and ideas . what do you do for Just facts ? do we consider everything as a question ? ( or constraints if you prefer, an accepted bounding fact ). why ? because I d like to materialize fact to anchor readers and create consensus, or at least make them feel heard, and separate fact from questioning , i.e. opinion (= belief) on fact ..

  • http://derailleurconsulting.com/ Chris R. Chapman

    Hopefully we can chat later today, Luc, but I’ll make a brief stab at your questions.

    Yes, almost all dialogue maps begin with a root question, typically in the form of “What should we do about…?” or “How should we do x?” This is recorded on the shared display with a “?” node that is then responded to with ideas, which in turn are argued pro or con (+ and – nodes)

    If you’re wanting to record facts into the map, you could ask a factual question like “Is x true?” or “We know this because…” and then respond to that with idea nodes for each factual response. In the Compendium tool you can also add a reference node for hyperlinks.

    Critical to all of this is a continuous verification with the group: As a facilitator you are an engaged observer, not a driver. Your aim is to have the group engage with the map and direct you on how to make their tangled thoughts coherent. This builds toward shared understanding of the problem domain between the participants and hopefully a shared commitment on what to do next.