thinking-skills

Use concept maps to visualize relationships between entities in a concept, domain, or system. Use when the task involves understanding how parts connect, exposing knowledge gaps, or communicating system structure.

Use confidence determines speed vs quality to decide how much polish, validation, or speed a product decision needs. Use when confidence in problem importance or solution correctness affects delivery tradeoffs.

Use conflict resolution diagrams to resolve opposing demands by uncovering underlying needs and a shared goal. Use when a personal, team, product, or organizational conflict appears mutually exclusive.

Use connection circles to map cause-and-effect relationships and identify feedback loops in a system. Use when analyzing interacting variables, product dynamics, support load, customer behavior, or systemic side effects.

Use the Cynefin framework to classify situations as clear, complicated, complex, chaotic, or disordered and choose the right response. Use when deciding how to act under uncertainty or domain complexity.

Use a decision matrix to choose between options by scoring them against weighted criteria. Use when several options and multiple decision factors make an objective comparison useful.

Use the Eisenhower Matrix to prioritize work by urgency and importance. Use when deciding what to do, schedule, delegate, or eliminate from a task list.

Use first principles thinking to break complex problems into fundamental truths and rebuild solutions from the basics. Use when assumptions need challenging or innovative solutions are needed.

Use the hard choice model to classify a decision by impact and ease of comparison. Use when deciding whether to move quickly, refine options, gain confidence, or apply a decision matrix.

Use the iceberg model to move from visible events to patterns, structures, and mental models. Use when seeking root causes, system leverage points, or deeper explanations for recurring issues.

Use an impact-effort matrix to prioritize tasks by expected impact and required effort. Use when separating quick wins, major projects, fill-ins, and thankless tasks.

Use inversion to solve problems by reasoning backward from failure, bad outcomes, or the opposite of success. Use when identifying risks, running premortems, or escaping overly idealized thinking.

Use an Ishikawa diagram to identify possible root causes of a problem by organizing contributing factors. Use when diagnosing defects, declining metrics, failures, or complex cause-and-effect issues.

Use issue trees to break complex problems into mutually exclusive and collectively exhaustive branches. Use when structuring problem solving, root cause analysis, solution exploration, or consulting-style decomposition.

Use the ladder of inference to slow down conclusions and inspect selected data, interpretations, assumptions, beliefs, and actions. Use when decisions may be based on unchecked assumptions or incomplete reality.

Use the Minto Pyramid to structure communication from conclusion to supporting points and details. Use when writing recommendations, executive summaries, decision memos, or answer-first explanations.

Use the OODA loop to make faster decisions in changing environments by observing, orienting, deciding, and acting. Use when speed, incomplete data, adaptation, or competitive response matters.

Use the productive thinking model to solve defined problems creatively through a structured six-step process. Use when clarifying what is going on, defining success, generating questions, and selecting solutions.

Use reinforcing feedback loops to identify dynamics that amplify growth, decline, or compounding effects in systems. Use when analyzing exponential change, flywheels, vicious cycles, or self-reinforcing behavior.

Use second-order thinking to examine consequences beyond immediate effects. Use when evaluating decisions across time horizons, asking what happens next, or avoiding short-sighted optimization.

Use Situation-Behavior-Impact to give clear, non-judgmental feedback by naming the context, observed behavior, and impact. Use when feedback risks becoming vague, personal, or hard to act on.

Use Six Thinking Hats to examine a decision or problem from multiple perspectives including benefits, creativity, emotion, data, risk, and process. Use when groups need parallel thinking or balanced evaluation.

Use abstraction laddering to reframe problems by moving between higher-level why questions and lower-level how questions. Use when a problem statement feels too narrow, too vague, or needs more innovative solution framing.

Use balancing feedback loops to identify stabilizing mechanisms that push systems back toward a goal or desired level. Use when analyzing self-correcting behavior, system resistance, control loops, or corrective actions.