liveBook · Manning

Problem shape

As explained in The Architecture of Reasoning

The structural characteristics of a problem that indicate what kind of reasoning it may require.

Problem shape is the set of structural signals that indicates what kind of reasoning a discussion needs. Diagnose those signals before committing to a reasoning mode: once a mode is underway, it can reinforce itself. Use the smallest structure that restores clarity; too little leaves the problem unresolved, while too much adds overhead. section 7.3 section 7.8

Look for the pattern beneath the visible disagreement or stalled decision:

  • A clear, bounded problem with sufficient information and reversible consequences usually needs only direct Q&A. section 7.3
  • If execution unravels after apparent agreement, revisit hidden assumptions: the team may have agreed on an answer without sharing its reasoning. section 7.3
  • If debate hardens into competing camps, the solution space may have narrowed before exploration is complete. section 7.3
  • If discussion circles around different priorities, such as customer impact, operational risk, or cost, make the competing perspectives explicit. section 7.3
  • If confidence grows while evidence recedes, test the reasoning rather than treating coherence as proof. section 7.3

Select or layer a reasoning structure in response to the diagnosed pattern. Reassess as the problem unfolds, and return to simpler modes once clarity is restored. Short framing phrases and clear boundaries can help a team coordinate its reasoning in real time. section 7.8 section 7.0

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

Use the scenario-to-failure pairs as a quick check for compressed reasoning, premature narrowing, perspective mismatch, or insufficient testing. section 7.3

How The Architecture of Reasoning covers it

How deep it goes
Distinguishes several diagnostic signals and links them to reasoning needs, without detailing every mode’s procedure.
Examples
Uses bounded questions, post-meeting execution breakdowns, binary debates, persistent conflict, and growing certainty.
What you can do after
Diagnose reasoning mismatches and select or shift to the smallest sufficient structure.
How it connects
Connects hidden assumptions, premature narrowing, perspective mismatch, and testing to reasoning architectures.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of The Architecture of Reasoning. The section links point to the parts of the book it draws on.