Read
Build the mental model
Move through the guided explanation first so the central distinction and purpose are clear before you evaluate your own work.
Problem Solving Logic
Capstone: Running the Full Problem-Solving Loop
An integrative lesson that asks students to take a real problem description, model it, generate candidate strategies, commit to one, build in revision triggers, and write a short postmortem plan for how they will know whether to revise.
Read the explanation sections first, then use the activities to test whether you can apply the idea under pressure.
Start Here
What this lesson is helping you do
An integrative lesson that asks students to take a real problem description, model it, generate candidate strategies, commit to one, build in revision triggers, and write a short postmortem plan for how they will know whether to revise. The practice in this lesson depends on understanding Problem State, Constraint, and Revision Trigger and applying tools such as Clarify the Goal Before Choosing a Strategy and Respect Constraints correctly.
How to approach it
Read the explanation sections first, then use the activities to test whether you can apply the idea under pressure.
What the practice is building
You will put the explanation to work through guided problem solving and quiz activities, so the goal is not just to recognize the idea but to use it under your own control.
What success should let you do
Run the full problem-solving loop on at least 3 mixed problems, producing model, candidate strategies, commitment, revision triggers, and postmortem plan.
Reading Path
Move through the lesson in this order
The page is designed to teach before it tests. Use this sequence to keep the reading, examples, and practice in the right relationship.
Study
Watch the move in context
Use the worked example to see how the reasoning behaves when someone else performs it carefully.
Do
Practice with a standard
Only then move into the activities, using the pause-and-check prompts as a final checkpoint before you submit.
Guided Explanation
Read this before you try the activity
These sections give the learner a usable mental model first, so the practice feels like application rather than guesswork.
Framing
Running the unit pipeline end-to-end
Earlier lessons taught the parts in isolation: understanding the problem, building a structured map, and choosing and revising a strategy. The capstone asks you to run the whole loop on a single problem without stopping.
Real problem solving is not a single decision. It is a loop: model, plan, commit, watch for revision signals, and either stay the course or change. The capstone trains the explicit handoffs between these stages.
What to look for
- Model the problem state, goal, and constraints before planning.
- Generate at least two strategies before committing.
- Name revision triggers and write a postmortem plan.
Problem solving is a loop, not a single decision; the capstone trains the full cycle.
Strategy
Choose the move that matches the case
Use a fixed pattern: (1) describe the problem state, goal, and constraints, (2) generate at least two candidate strategies, (3) pick one and explain why, (4) name the revision triggers that would cause you to change course, and (5) write a short postmortem plan: how will you decide whether the strategy worked?
The revision triggers step is what separates committed-but-not-stuck problem solvers from stuck ones. Without explicit triggers, you either change course too late or keep changing course on impulse.
What to look for
- Describe the state, goal, and constraints.
- Pick a strategy and say why.
- Name revision triggers and a postmortem plan.
Explicit revision triggers turn commitment into durable focus rather than sunk-cost pride.
Error patterns
How integration failures actually look
The commonest failure is committing to a strategy without naming the conditions under which you would abandon it. Without triggers, you cannot distinguish 'this is hard and I should persist' from 'this is broken and I should switch'.
The second commonest failure is writing a plan with no postmortem. You finish the work, but you cannot say whether the strategy actually solved the problem or merely relieved its symptoms.
What to look for
- Do not commit without naming triggers.
- Do not skip the postmortem plan.
- Do not generate only one candidate strategy.
Problem-solving failures cluster around missing triggers and missing postmortems.
Before practice
What this lesson is testing
The cases below are real problem descriptions drawn from work, study, and everyday decisions. Each requires you to run the full loop from model to postmortem plan.
A case is only complete when you have produced the problem model, candidate strategies, commitment with justification, revision triggers, and postmortem plan.
What to look for
- Model, generate, commit, set triggers, write postmortem.
- Name specific thresholds for each trigger.
- Make the postmortem concrete and measurable.
The capstone measures whether you can run the full problem-solving loop on a case that does not come pre-framed.
Core Ideas
The main concepts to keep in view
Use these as anchors while you read the example and draft your response. If the concepts blur together, the practice usually blurs too.
Problem State
The current situation that must be understood before a reasonable plan can be formed, including what is known, what is unknown, and what has already been tried.
Why it matters: Good problem solving starts with describing the present situation accurately rather than racing to a solution.
Constraint
A limitation, requirement, or condition that shapes which solutions are acceptable — time, budget, rules, resources, or policies.
Why it matters: A plan that ignores constraints is not a genuine solution; it is an aspiration.
Revision Trigger
A specific observation or event that would signal the plan needs to change.
Why it matters: Naming revision triggers in advance makes plans self-correcting rather than blindly committed.
Reference
Open these only when you need the extra structure
How the lesson is meant to unfold
Review
This step supports the lesson by moving from explanation toward application.
Guided Synthesis
This step supports the lesson by moving from explanation toward application.
Independent Synthesis
This step supports the lesson by moving from explanation toward application.
Reflection
This step supports the lesson by moving from explanation toward application.
Mastery Check
The final target tells you what successful understanding should enable you to do.
Reasoning tools and formal patterns
Rules and standards
These are the criteria the unit uses to judge whether your reasoning is actually sound.
Clarify the Goal Before Choosing a Strategy
A strategy cannot be assessed well until the goal state is explicit and specific enough to recognize success.
Common failures
- The learner starts proposing solutions before identifying the actual goal.
- The target outcome remains vague or shifts during the analysis.
Respect Constraints
A proposed solution must fit the relevant time, resource, and rule constraints of the problem.
Common failures
- The plan assumes resources that are not available.
- The solution ignores explicit limitations or requirements.
Compare Options Explicitly
A good practical judgment weighs at least two plausible options before committing to a path.
Common failures
- Only one option is considered.
- The chosen path is asserted without comparison or tradeoff analysis.
Build In Revision Triggers
A good plan names the observations that would justify revising or abandoning it.
Common failures
- The plan has no stopping or revision conditions.
- The reasoner continues executing the plan even when obvious failure signals appear.
Patterns
Use these when you need to turn a messy passage into a cleaner logical structure before evaluating it.
Problem Map Schema
Input form
practical_problem
Output form
structured_problem_map
Steps
- State the current problem state.
- State the goal state.
- List key constraints and available resources.
- List candidate strategies.
- Compare the strategies against the goal and constraints.
- Choose the best next step and name its revision triggers.
Watch for
- Skipping the constraint analysis.
- Treating a first idea as if it were already the best option.
- Confusing the final goal with the immediate next action.
Decision Matrix
Input form
multiple_candidate_solutions
Output form
criteria_based_comparison
Steps
- Identify at least two candidate strategies.
- Name the criteria for judging them (goal fit, constraint fit, cost, risk, reversibility).
- Compare how each option handles the criteria.
- Identify tradeoffs.
- State the most reasonable current strategy and the conditions that would reopen the comparison.
Watch for
- Choosing without explicit criteria.
- Ignoring obvious tradeoffs.
- Treating a provisional choice as irreversible.
Worked Through
Examples that model the standard before you try it
Do not skim these. A worked example earns its place when you can point to the exact move it is modeling and the mistake it is trying to prevent.
Worked Example
Model, Commit, and Trigger
A full-cycle answer includes triggers and a postmortem plan, not just a strategy choice.
Model
Goal
Ship on time with verified compatibility.
State
Release scheduled in 14 days; compatibility unverified; no response from vendor.
Constraints
- Cannot delay the release.
- Cannot ship without verified compatibility.
- Cannot fully replicate the vendor's environment internally.
Problem
A software release is two weeks away and a key external dependency has not responded to questions about compatibility.
Commitment
Run the first two strategies in parallel for 48 hours, then commit to fallback if neither succeeds.
Postmortem Plan
After release, check whether compatibility was verified, whether the fallback was needed, and whether the triggers fired at the right times.
Revision Triggers
- If no response from vendor within 48 hours, commit to fallback.
- If the internal harness cannot be built in 72 hours, abandon that track.
Candidate Strategies
- Escalate to the vendor's account manager and set a 48-hour response deadline.
- Begin building an internal compatibility test harness in parallel.
- Prepare a fallback release with the dependency disabled.
Pause and Check
Questions to use before you move into practice
Self-check questions
- Did I model the state, goal, and constraints explicitly?
- Did I name at least two revision triggers with thresholds?
- Can I say how I will judge whether my strategy worked?
Practice
Now apply the idea yourself
Move into practice only after you can name the standard you are using and the structure you are trying to preserve or evaluate.
Guided Problem Solving
Problem SolvingFull-Cycle Problem Solving
For each problem, produce: (1) a short model of state, goal, and constraints, (2) two or more candidate strategies, (3) a commitment with a one-sentence justification, (4) a list of revision triggers with thresholds, and (5) a postmortem plan describing how you will judge whether the strategy worked.
Integrative cases
Work one case at a time. These cases are deliberately mixed; part of the exercise is deciding which moves from the unit each case requires.
Case A
A small team is falling behind on a product launch. Two engineers have been out sick, the backlog has grown, and the planned launch is in four weeks. The team lead must decide how to handle the gap.
The state is deadline-limited; model it before planning.
Case B
A student has three major assignments due in seven days and a part-time job. They have already committed to about ten hours of work and need to plan the rest.
A time-budget allocation problem with a firm deadline.
Case C
A family is moving to a new city in six weeks. They have to handle housing, schools, jobs, and the physical move. Some tasks depend on others.
Dependency-heavy problem. Which tasks go first?
Case D
A manager is rolling out a new process at work. Early feedback is mixed: some teams report improvements, others report confusion. The rollout has two weeks until a company-wide deadline.
A live decision: should you revise the process now or collect more data?
Quiz
Problem SolvingCapstone Check Questions
Answer each short check question in one or two sentences. These questions test whether you can articulate the reasoning you just performed in your own words.
Check questions
Answer each question from memory in your own words. No answer should need more than two sentences.
Question 1
Why is generating multiple candidate strategies more important than picking the first good one?
Strategy comparison exposes assumptions the first idea hides.
Question 2
What is a revision trigger and why is it essential to commitment?
It is a pre-committed signal for changing course without ego.
Question 3
What makes a postmortem plan concrete rather than vague?
Measurable criteria set in advance.
Question 4
Why is the problem model the first step, before strategy?
A bad model produces confident wrong strategies.
Animated Explainers
Step-by-step visual walkthroughs of key concepts. Click to start.
Read the explanation carefully before jumping to activities!
Further Support
Open these only if you need extra help or context
Mistakes to avoid before submitting
- Letting commitment become stubbornness because no trigger was set.
- Treating the first viable strategy as the only one.
Where students usually go wrong
Committing without triggers.
Generating only one candidate strategy.
Writing a vague postmortem plan.
Skipping the problem model and going straight to action.
Historical context for this way of reasoning
Herbert Simon
Simon argued that problem solving should be treated as a process of iterative search and commitment, not a one-shot decision. The capstone implements Simon's loop in miniature.