A meeting about merging two product lines ends without a decision. One person wants an answer; another questions the cost assumptions; others propose different forms of consolidation, focus on customer impact, or ask for evidence of demand. Each contribution may be useful. The friction comes from using different reasoning modes without agreeing on what the conversation needs next. section 7.1
A reasoning mode is the structure used to approach a question. Direct Q&A seeks a bounded answer. Chain-of-Thought makes assumptions and intermediate reasoning visible. Tree-of-Thought opens distinct alternatives before narrowing. Chair-of-Thought examines different perspectives. ReAct presses a plausible account against evidence. The aim is not to use every mode, but to choose the smallest structure that resolves the current obstacle. section 7.1 section 7.8
Choose by the shape of the problem, not by a preferred meeting format:
- Use Direct Q&A when the question is clear, information is sufficient, and a wrong answer is limited or reversible. More structure would add drag. section 7.3
- Surface assumptions when quick agreement repeatedly falls apart during execution. The team may share an answer without sharing the reasoning behind it. section 7.3
- Generate distinct alternatives when a debate hardens around two options. Stop branching once new options are merely variations. section 7.3 section 7.5
- Name the perspectives when participants keep returning to different concerns, such as customer impact and operational risk. Ask what evidence would change the group's view when confidence outruns testing. section 7.3 section 7.5
A small intervention
Instead of restarting the whole meeting, say: “We are evaluating before we have generated options. Can we hold judgment for five minutes and create three distinct paths?” Once the options are clear, return to evaluation. A shift in mode can be brief and explicit; it need not become a new process. section 7.5 section 7.8
Table 7.1 Example scenarios which may indicate reasoning failures
|
Scenario
|
Possible reasoning failure
|
|
Fast agreement
|
may indicate compressed reasoning
|
|
Binary debates
|
may indicate premature narrowing
|
|
Persistent conflict
|
may indicate perspective mismatch
|
|
Growing certainty
|
may indicate insufficient testing
|
The scenario table offers quick signals for spotting compressed reasoning, premature narrowing, perspective mismatch, and insufficient testing. section 7.3
