THE QUESTION
Why do complaints keep rising while the product improves?
The causes, deepest first. Disagreements stay on the map.
closed · back to Actions
Viewing as guest. Enter a handle to join and take part.
The map
Left to right: deepest causes first; outlined green boxes are the roots. Only direct links are drawn — a link implied by a path is on the record, not in the picture. Dashed red is contested. Hover for full text.
How this dialogue measures
why
The indicators the method's own practitioners use to judge a dialogue's quality (Laouris & Metcalf 2024, Table 7), computed from this record so it can be compared with the hundreds of face-to-face and virtual dialogues behind their baselines. Spreadthink is the share of ideas that got at least one vote: 100% means everyone voted only for their own, and it usually settles to 25–45% once meaning has been shared. Situational complexity falls as more ideas are structured.
ideas (N)
27 usual: 50–100
27 usual: 50–100
with 1+ vote / 2+ votes
24 / 19
24 / 19
spreadthink
86.4% usual: 25–55
86.4% usual: 25–55
demosensus
13.6%
13.6%
clusters (dimensions)
4
4
cards in a cluster
29.6%
29.6%
structured / levels / links
20 / 5 / 17
20 / 5 / 17
situational complexity
0.77
0.77
minds moved
—
—
cards hidden by the steward
0
0
pairs contested
0
0
The merged map
why
Every group built its own map from its own wall; these are folded into one. The same claim raised in two groups is one item, and each connection shows how many groups found it. Where groups found opposite things, that is published as a conflict.
ROOT CAUSES
◆ b752f5c
◆ a224a5a
◆ 22aaf4e
Connections several groups found (17 of 17)
| Refund policy is different on the website, in the app and in the scrip | → | A customer who complains twice gets the same first reply both times | 1 group |
| Angry customers are moved to the back of the queue by the priority rul | → | Agents who take the time to fix a problem properly miss their numbers | 1 group |
| Angry customers are moved to the back of the queue by the priority rul | → | Complaints are counted only when someone uses the word complaint | 1 group |
| Refund policy is different on the website, in the app and in the scrip | → | Agents cannot issue a refund without a manager, and the manager is in | 1 group |
| Most complaints are about waiting, not about the answer | → | Complaints are counted only when someone uses the word complaint | 1 group |
| Managers see the dashboard, agents see the queue, nobody sees the cust | → | Survey requests go out before the problem is solved | 1 group |
| Nobody from product reads the ticket tags | → | Survey requests go out before the problem is solved | 1 group |
| Most complaints are about waiting, not about the answer | → | A customer who complains twice gets the same first reply both times | 1 group |
| Agents who take the time to fix a problem properly miss their numbers | → | Complaints about one feature spike after every release | 1 group |
| Survey requests go out before the problem is solved | → | Templates make every reply sound like nobody read the message | 1 group |
| A customer who complains twice gets the same first reply both times | → | Most complaints are about waiting, not about the answer | 1 group |
| Nobody from product reads the ticket tags | → | The same question is answered a hundred times because the help page is | 1 group |
| Survey requests go out before the problem is solved | → | The same question is answered a hundred times because the help page is | 1 group |
| Nobody from product reads the ticket tags | → | The best agents leave within a year | 1 group |
| Agents who take the time to fix a problem properly miss their numbers | → | Refund policy is different on the website, in the app and in the scrip | 1 group |
| Agents who take the time to fix a problem properly miss their numbers | → | Complaints are counted only when someone uses the word complaint | 1 group |
| A customer who complains twice gets the same first reply both times | → | Complaints are counted only when someone uses the word complaint | 1 group |