Problem Solving¶
Core Idea¶
Problem solving is the organized attempt to bridge a gap between a present state and a goal when the route is not immediately available. The solver represents what is given, what counts as success, and what blocks direct attainment; generates or retrieves possible operations; tests candidate paths against constraints and evidence; learns from failure; and validates an outcome. The process may be deliberate or partly automatic, individual or distributed, symbolic or embodied. Its identity is the obstacle-to-solution transformation, not any single heuristic. A problem is not merely an unpleasant condition.
How would you explain it like I'm…
Getting Past the Stuck Part
Finding a Way Through
Bridging Obstacle to Goal
Broad Use¶
Problem Solving applies wherever its complete role structure is present; the source domain is historical provenance, not a boundary on the Prime. Mathematics. a solver represents givens and constraints, applies transformations, and proves that a constructed answer satisfies them Engineering design. teams generate architectures, simulate tradeoffs, test prototypes, and revise constraints Diagnosis. evidence narrows competing explanations and selects an intervention whose response supplies further feedback Software. developers reproduce a defect, localize causes, construct changes, and validate behavior with tests Operations. organizations identify a performance gap.
Clarity¶
Use Problem Solving only after naming the carrier and the relation that makes the case one. The minimal definition is: Problem solving is the goal-directed process of representing an obstructed or underdetermined state, generating or selecting possible transformations, testing them against constraints and evidence, and carrying an adequate path to a validated solution. The most common ambiguity is to substitute a neighbor, an enabling condition, or a consequence for the identity itself.
Manages Complexity¶
Problem Solving manages complexity by compressing many implementations into a stable role structure without erasing the variables that control validity. Analysts can compare cases by filling the same slots, locate disagreement in a missing role, and separate the constitutive relation from causes, instruments, representations, and consequences.
Abstract Reasoning¶
- Solver move. Identify an organism, person, team, institution, algorithm, or coupled system capable of transforming or representing states and record what observation supports the assignment.
- Present State move. Identify the relevant facts, resources, commitments, and uncertainties at the start of the attempt and record what observation supports the assignment.
- Goal Or Adequacy Criterion move. Identify the condition by which the problem is considered resolved and record what observation supports the assignment.
- Obstacle Or Gap move.
Knowledge Transfer¶
Cross-domain transfer. The present-state–goal–obstacle–operator–test–solution relation is literally instantiated across cognitive, mathematical, engineering, organizational, and computational systems despite very different mechanisms. The invariant is not the source-domain vocabulary but the typed relation expressed by the one-line definition. Transfer is literal when a receiving domain can fill the same roles and expose the same failure boundary; it is analogical when only a visual, verbal, or narrative resemblance survives. Local warrants for Problem Solving. Different domains establish those roles differently.
Example¶
To prove that a graph has a requested property, a mathematician first converts the statement into explicit givens, constraints, and a success condition. Small examples expose invariants; a decomposition reduces the search; a candidate lemma is tested against counterexamples; and the final proof validates that every admissible graph satisfies the conclusion. The proof is a solution, while the sequence of representation, candidate generation, rejection, and validation is the solving process. Merely applying a memorized theorem after its applicability is obvious is routine execution at the boundary.
Relationships to Other Abstractions¶
Current abstraction Problem Solving Prime
Parents (1) — more general patterns this builds on
-
Problem Solving is part of Problem Representation Prime
Problem Solving contains Problem Representation because a solvable state, goal, operators, obstacles, and success test must be encoded before candidate transformations can be evaluated.
Children (1) — more specific cases that build on this
-
Incubation (Problem Solving) Domain-specific presupposes Problem Solving
A prepared problem-solving attempt is required before a break can count as incubation of that problem.
Hierarchy path (1) — routes to 1 parentless root
- Problem Solving → Problem Representation → Representation → Abstraction
Distinction from Neighbors¶
-
Problem framing. Framing establishes the boundary and success criteria; it is often a stage of solving but not the whole process.
-
Problem representation. Representation determines available states and operations; solving uses and may revise that representation to reach adequacy.
-
Decision making. Decision making chooses among alternatives, while problem solving may need to discover, construct, or test the alternatives first.