Every organisation solves problems and makes decisions. Few do it systematically.
A problem surfaces. Ideas are generated. A quick evaluation follows. A solution is chosen. The same pattern applies to decisions — options appear, discussion happens, someone decides. What's often missing: a structured process that ensures all dimensions of the issue are examined.
Without structure, we're inconsistent. Sometimes we consider implications; sometimes we don't. Sometimes we map stakeholder views; sometimes we forget. Sometimes we articulate assumptions; sometimes we only discover them when they fail.
The frameworks on this page provide that structure.
Two facets of critical thinking
Critical thinking has two distinct facets:
How to think critically
The underlying skills — logical reasoning, evaluating credibility, recognising fallacies, understanding cognitive biases, seeing through rhetorical manipulation.
Thinking critically about an issue
The structured process — ensuring all dimensions of a problem or decision are examined systematically.
The relationship between these two is analogous to science and engineering. Science provides the principles; engineering applies them to build things that work. "How to think critically" provides the principles; "thinking critically about an issue" applies them to problems and decisions.
We can know all the critical thinking skills, but without a structured process, we'll miss dimensions. We can follow the frameworks perfectly, but without the skills, the reasoning inside them will be flawed. Both are necessary. Neither is sufficient.
This page focuses on the second facet — the frameworks for thinking critically about issues.
The problem-solving framework
Problems don't arrive neatly defined. They show up as symptoms, complaints, anomalies. The first task is to understand what we're actually solving.
The framework:
1. Define the problem
2. Formulate hypotheses
3. Gather evidence
4. Analyse the evidence
5. Identify root cause
6. Develop alternative solutions
7. Evaluate and choose a solution
8. Apply AISI
Define the problem
Problems are often presented as symptoms. "Sales are down" is a symptom. The problem might be pricing, product-market fit, competitive pressure, or sales execution — each requiring different solutions. Watch out for framing bias — the tendency to define a problem from a limited perspective, which can distort everything that follows.
Formulate hypotheses
What might be causing this problem? Hypotheses require domain knowledge — we need to know enough about the area to propose plausible causes. The risk here is confirmation bias: we tend to formulate hypotheses that match causes we've seen before, overlooking less familiar possibilities.
Gather evidence
Evidence should relate directly to each hypothesis. Confirmation bias reappears here — we naturally seek evidence that supports what we already believe. Consider both primary and secondary sources. Ensure the evidence is reliable, valid, and sufficient.
Analyse the evidence
Interpret the data. Identify patterns. Validate or reject hypotheses. This step often involves analytical frameworks — root cause analysis, cost-benefit analysis, comparative analysis. The goal is to understand what's actually happening, not to confirm what we assumed was happening.
Identify root cause
With analysis complete, identify the underlying cause. This is what the solution must address. Solving symptoms leaves the root cause intact — and the problem returns.
Develop alternative solutions
Generate multiple solutions that address the root cause. Evaluate each for effectiveness, feasibility, and practicality.
Evaluate and choose a solution
Assess each alternative against defined criteria. Choose the solution that best addresses the root cause while remaining practical to implement. But choosing a solution is not the final step.
Apply AISI
Before finalising, examine the solution through four dimensions that exist whether we consider them or not. This is where many processes stop too early.
AISI: The four dimensions
Every solution and every decision has four dimensions that are present regardless of whether we explicitly examine them. Miss any one, and there's a gap in the analysis.
Assumptions
What are we taking for granted? Every solution rests on assumptions — about adoption, timing, resources, market conditions, behaviour. Articulating assumptions makes them visible and testable. When assumptions fail, solutions fail.
Implications
What follows from this solution? Every choice creates consequences — intended and unintended, positive and negative, immediate and downstream. Considering implications helps anticipate side effects before they materialise.
Stakeholder views
Who is affected, and how do they see it? Stakeholders have different interests, concerns, and perspectives. A sales manager sees discounting differently than a finance manager. Mapping these views surfaces conflicts and builds buy-in.
Implementation risks
What could go wrong when we execute? Even good solutions fail if implementation is unwieldy or risks are too high. Outlining the implementation plan — even at a high level — precipitates risks that a conceptual discussion misses. If risks are unacceptable, return to alternatives.
AISI isn't a final check. It's an integral part of the evaluation. Sometimes the AISI analysis reveals that a promising solution is built on fragile assumptions or carries unacceptable implementation risks — and we need to go back.
The decision-making framework
Decision-making differs from problem-solving. In problem-solving, we start with something wrong and seek to fix it. In decision-making, we start with a choice to be made — often without a clear "problem" at all.
The framework:
1. Define the decision to be made
2. Identify decision options
3. Define decision criteria
4. Gather evidence
5. Evaluate options against criteria
6. Select the best option
7. Apply AISI
Define the decision precisely. "Should we expand?" is vague. "Should we enter the European market in Q3 2026 with our current product line?" is precise. Precision prevents drift.
Identify all options. Not just the obvious two or three. What options haven't we considered? What would we do if the leading option disappeared?
Define criteria before evaluating. This prevents post-hoc rationalisation — choosing an option and then finding criteria that justify it. Agree on what matters before assessing how each option performs.
Gather evidence and evaluate. For each combination of option and criterion, what does the evidence show? Systematic evaluation surfaces trade-offs that informal discussion obscures.
Apply AISI. Before finalising, examine assumptions, implications, stakeholder views, and implementation risks — exactly as with problem-solving.
What the frameworks don't do
The frameworks ensure we examine all dimensions of an issue. They don't ensure the quality of thinking within each step.
We can follow the problem-solving framework perfectly and still:
- Accept evidence from unreliable sources
- Fall prey to confirmation bias when gathering data
- Be swayed by logical fallacies in the analysis
- Confuse correlation with causation
- Miss rhetorical manipulation in stakeholder input
This is why the frameworks are only one facet of critical thinking. The other facet — how to think critically — provides the skills that ensure quality of reasoning at every step.
See how all the pieces fit together in a single business decision →
The framework as communication protocol
Beyond its analytical value, the framework serves as a shared language across teams.
When someone brings a recommendation, the structure makes the thinking visible. Assumptions are stated, not hidden. Implications are considered, not discovered later. Stakeholder views are mapped, not assumed. Implementation risks are surfaced, not ignored.
The framework isn't just a thinking tool. It's a communication protocol. Faster alignment. Less back-and-forth. Better decisions.
Learn the complete system
These frameworks are central to the training programs at Critical Thinking Academy. Participants learn the frameworks alongside the critical thinking skills that make them work — logical reasoning, credibility evaluation, fallacy recognition, bias awareness, and persuasive communication.
Programs for universities and colleges →
The textbook: Critical and Analytical Thinking (Cengage, 2024) →
See the detailed step-by-step framework reference →
Free download - Critical thinking field guide - preview
Get the Critical Thinking Field Guide
The Critical Thinking Field Guide has been written for the experienced professional who would like to get all the concepts of critical thinking without long stories or fluff. Straight to the concept with clear examples to grasp the essence.
Read almost half the book free — the frameworks, deductive and causal reasoning in full, plus 15 cognitive biases and 16 fallacies. Complete, concise, no fluff. No sign-up.
Download the free preview →