Dialectical Mapping

Thinking Tools4.4 Refining Ideas Into Practical SolutionsAlso known as Dialectical Maps

Descends from G. W. F. Hegel's dialectical method (Science of Logic, 1812) and the pragma-dialectics of Frans H. van Eemeren and Rob Grootendorst (Speech Acts in Argumentative Discussions, 1984); the map itself comes from E. Michael Nussbaum and Gregory Schraw's argument vee diagram (2007), put on screen by Hui Niu and John C. Nesbit (The Dialectical Map, 2015).

Diagrams a contested question as a thesis and its antithesis, each with its strongest arguments, the counterarguments, and the replies, to see where a synthesis might lie.

The four-day week argued on both sides, down to the replies that survive

Each side's strongest arguments open into the best counter to each, then the reply. Select each reply to judge it, and mark the ones that hold up; then select the question at the root to read the position built from what survived on both sides. Illustrative.

0 of 4 marked1 of 4 marked2 of 4 marked3 of 4 marked4 of 4 marked

Select a box to read it. Mark each reply that holds up, then read the root.Move the company to a four-day week? What survived on both sides: burnout drives exits, and support needs five-day cover. The synthesis: a staggered four-day week for teams of six or more, trialed for one quarter against retention and response times, with smaller teams kept on five days.Thesis: yes, four days at full pay. The claim, stated sharply so it can be opposed.Exits cost $40,000 a head. Argument: replacing an engineer costs about $40,000 in recruiting and lost months, and twenty left last year.Counter: perks do not cure pay gaps. Counterargument: people leave for money, and a shorter week will not hold someone a rival pays more.Reply: 7 of 10 exits cite burnout. Reply: the exit interviews name workload far more often than pay. This holds: the counter does not fit this company's data.Same output in fewer hours. Argument: most of the work that matters gets done in focused hours, and the fifth day is mostly meetings.Counter: support needs five-day cover. Counterargument: customers call on Fridays, and an empty support desk would cost renewals.Reply: stagger the days off. Reply: half the team off on Monday, half on Friday, and the desk is covered every day. This holds for teams large enough to split.Antithesis: no, keep five days. The opposing claim, with its own strongest case.Customers expect five-day service. Argument: the largest accounts have five-day response terms in their contracts.Counter: staggered days cover five. Counterargument: with staggered days off, every weekday is staffed.Reply: small teams cannot stagger. Reply: a team of three cannot split its days off and still cover the work. This holds: the staggered plan works only above about six people.Output will fall. Argument: a fifth fewer hours means less shipped, whatever the theory says.Counter: trial it and measure. Counterargument: run it for a quarter with agreed measures, and the question answers itself.Reply: a trial is hard to undo. Reply: once given, the day off is hard to take back. This one is weak: a trial announced as a trial, with its measures set in advance, can be ended.

An example

A software company's leadership team had argued about a four-day week for two months. The head of engineering wanted it to stop the resignations; the head of customer success said the support desk could not be empty on Fridays. Each meeting replayed the same exchange.

The chief of staff put the question on a wall with both sides as sharp claims and asked each camp for its two strongest arguments. Under every argument the other side wrote its best counter, and the first side replied. Two replies held: the exit interviews named burnout in seven of ten cases, and support could be covered by staggering the days off. One reply from the other side held too, since teams of three could not stagger. The position that came out of the map kept all three: a staggered four-day week for teams of six or more, trialed for a quarter against retention and response times, with small teams on five days. Both heads signed it in the same meeting.

Why it works

In a looping debate each side restates its own case and attacks the weakest version of the other. A dialectical map makes both cases visible at their strongest, side by side, and attaches to each argument the best answer the other side has. Arguments that collapse under their counter drop out; arguments that survive the counter and its reply are the ones any decision has to respect.

A synthesis can then be read off the survivors on both sides, which is different from a compromise that splits the difference. Writing the replies down also shows where a branch turns on a fact nobody has checked, so the next step is often a piece of evidence instead of another meeting.

The thinking behind it

G. W. F. Hegel G. W. F. Hegel, the German idealist philosopher, made logic a dialectic in his Science of Logic (three volumes, 1812 to 1816): each concept, pressed to its limits, turns into its opposite, and the tension is overcome in a richer concept that keeps both. The map's habit of drawing a synthesis out of opposed positions descends from him, though the tidy triad of thesis, antithesis, and synthesis is a later simplification; Hegel rarely used those terms and warned against reducing dialectic to a lifeless schema.

E. Michael Nussbaum E. Michael Nussbaum, an educational psychologist, studied with Gregory Schraw how to get students to weigh arguments against counterarguments, in Promoting Argument-Counterargument Integration in Students' Writing (Journal of Experimental Education, 2007). Their tool was the argumentation vee, a diagram shaped like a letter V, with arguments on one side, counterarguments on the other, and an integrated conclusion written below, the layout this map keeps.

John C. Nesbit John C. Nesbit, a professor of education at Simon Fraser University who studies argumentation and cognitive tools for learning, is credited with Hui Niu for the Dialectical Map, an online tool that lays arguments and counterarguments side by side and asks the writer for an integrated conclusion. Nesbit described this line of work in Cognitive Tools for Scaffolding Argumentation (2018).

How to run it

  1. State both claims sharply. Write the thesis and the antithesis as plain opposing sentences that cannot both be fully true.
  2. List each side's strongest arguments. Ask each camp for two to five, and accept only the best versions.
  3. Attach the best counter to each. Have the other side write it, so each counter is as strong as its authors can make it.
  4. Add replies until each branch settles. Stop a branch when a reply goes unanswered or the branch turns on a fact nobody has.
  5. Mark what survives. Tick every argument or reply that still stands, on both sides.
  6. Build the position from the survivors. Write one proposal that respects every ticked point, and check it against each in turn.

Where it goes wrong

One side writes the other's case. A camp that drafts its opponents' arguments drafts weak ones, and the map flatters it. Each side writes its own arguments and its own counters.

The synthesis is a split. Meeting in the middle, three and a half days, keeps neither side's surviving points. Check the proposal against each surviving argument; if one is ignored, it is not yet a synthesis.

The map hides a factual question. Some branches cannot settle by argument, only by data. Mark them, assign someone to find the fact, and come back before deciding.

When to use something else

  • IBIS. When one question has several candidate answers in place of two opposed sides, and a record of the reasoning matters.
  • Steelmanning. When the immediate need is to state the other side's view at its strongest before any mapping.
  • Toulmin Model. When one argument needs checking link by link, from data to claim.

Where it sits in SOLVE eX

Go to the source

  • Science of Logic, 1812
  • Speech Acts in Argumentative Discussions, 1984
  • Promoting Argument-Counterargument Integration in Students' Writing, Journal of Experimental Education 76(1), 2007
  • The Dialectical Map (DMap), Simon Fraser University, 2015

Back to the catalog