Rigorous Reasoning

Problem Solving Logic

Understanding the Problem Before Solving It

Introduces problem states, goal states, and constraints as the backbone of disciplined practical reasoning, and establishes the habit of describing the problem before proposing a solution.

Focus on understanding the core distinction first, then use the examples to see how the idea behaves in actual arguments.

Problem SolvingConceptLesson 1 of 40% progress

Start Here

What this lesson is helping you do

Introduces problem states, goal states, and constraints as the backbone of disciplined practical reasoning, and establishes the habit of describing the problem before proposing a solution. The practice in this lesson depends on understanding Problem State, Goal State, Constraint, and Resource and applying tools such as Clarify the Goal Before Choosing a Strategy and Respect Constraints correctly.

How to approach it

Focus on understanding the core distinction first, then use the examples to see how the idea behaves in actual arguments.

What the practice is building

You will put the explanation to work through classification practice, quiz, guided problem solving, analysis practice, evaluation practice, rapid identification, and diagnosis practice 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

Given 4 practical cases, identify the problem state, goal state, at least three constraints, and at least two resources for each.

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.

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.

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.

Orientation

Understanding the problem is a step, not a preface

The biggest reason people fail at problem solving is not a lack of clever solutions — it is a failure to understand the problem clearly in the first place. Jumping to solutions feels productive, but it often produces plans that do not match the actual situation. Polya's first step of problem solving is 'understand the problem,' and he meant it as a full stage, not a box to tick on the way to action.

Understanding the problem means being able to state three things: where you are, where you want to be, and what prevents you from going directly from one to the other. Those three things are the problem state, the goal state, and the constraints. Every disciplined problem-solving process starts from this triad, and most problem-solving failures come from skipping or rushing one of the three.

What to look for

  • Resist the urge to propose a solution in the first thirty seconds.
  • Write down the three components: current state, goal, constraints.
  • Re-read the problem until you can restate it in your own words.
Good problem solving starts with disciplined description, not with clever action.

Problem state

Describing the problem state precisely

The problem state is the current situation. Describing it precisely means listing what you know, what you don't know, what you've already tried, and what resources are available. It is the factual ground that any plan has to stand on.

A common mistake is to describe the problem state as 'everything is going wrong' or 'I'm stuck.' Those are feelings, not facts. A useful problem state lists observable conditions: 'the report is due Friday, I have three of the six sections drafted, two sources are still unread, I haven't heard back from my co-author, and I've already tried writing the introduction twice.' That level of specificity opens doors that a vague description cannot.

What to look for

  • List observable facts, not feelings.
  • Note what has already been tried.
  • Include resources and people who might help.
A specific problem state makes the situation tractable.

Goal state

Stating the goal so you can tell when you've reached it

The goal state is what you're trying to achieve. It should be specific enough that you can tell when you've arrived. 'Do better in the class' is a wish, not a goal. 'Submit a complete draft by Friday noon that covers all six required sections' is a goal — you can tell whether you've hit it.

When goals are vague, strategy selection becomes impossible because you can't measure whether any given plan is good. When goals are specific, strategies become comparable: you can ask which plan is most likely to produce exactly that outcome under the given constraints. If you find that you can't say when you'd be done, you haven't yet stated a usable goal.

What to look for

  • State the goal so someone else could tell whether it's been reached.
  • Avoid vague language like 'do well' or 'get things under control'.
  • If the goal seems too big, break it into smaller, measurable sub-goals.
A goal is only useful if you can tell whether you've reached it.

Constraints

Naming the real constraints

Constraints are the limits that a real solution must respect. Time, money, rules, resources, and the behavior of other people are all constraints. A good constraint list contains both hard constraints ('the deadline is Friday') and soft ones ('it would be awkward to ask my manager again').

Constraints do the double work of eliminating fantasy solutions and making real solutions visible. A plan that ignores the constraints is not a plan; it is an aspiration. When you catch yourself thinking 'this would be easy if only…,' the part after 'if only' is usually a constraint you're trying to wish away, and that's exactly where the real problem-solving work happens.

What to look for

  • List time, resource, rule, and people constraints explicitly.
  • Distinguish hard constraints from soft ones.
  • Do not ignore a constraint just because it makes the problem harder.
Constraints are where real problem solving happens — embrace them.

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.

Goal State

The outcome or condition the reasoner is trying to reach, stated clearly enough to tell whether a proposed solution would actually produce it.

Why it matters: A clear goal helps determine which strategies are relevant and when the problem is actually solved.

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.

Resource

Anything the reasoner can draw on to move toward the goal, including time, money, tools, information, or help from others.

Why it matters: Realistic planning depends on knowing what you actually have, not just what you wish you had.

Reference

Open these only when you need the extra structure

How the lesson is meant to unfold

Hook

A motivating question or contrast that frames why this lesson matters.

Concept Intro

The core idea is defined and separated from nearby confusions.

Worked Example

A complete example demonstrates what correct reasoning looks like in context.

Guided Practice

You apply the idea with scaffolding still visible.

Assessment Advice

Use these prompts to judge whether your reasoning meets the standard.

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

Missed Assignment Recovery

The best plan depends on the real constraints, not on an idealized version of the problem. Notice how specific the goal and constraints are — both can be checked for completion.

Scenario

A student realizes they missed two assignments and now has limited time before finals.

Resources

  • Office hours with the instructor are available Tuesday.
  • A study group meets Thursday.
  • Existing notes cover most of the second missing assignment.

Goal State

Recover at least 15 of the 20 missing grade points and submit all other coursework on time.

Constraints

  • The semester ends in one week.
  • The instructor only accepts one late assignment.
  • The student also has two other exams.
  • The student cannot miss sleep for more than two more nights.

Problem State

Two assignments missing (worth 10% each), three drafts in progress for other classes, the student has been sleeping poorly, and no extensions have been requested yet.

Pause and Check

Questions to use before you move into practice

Self-check questions

  • Have I clearly separated the current problem state from the goal state?
  • What constraints could block an otherwise attractive solution?
  • Could a stranger tell from my description whether the goal has been reached?

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.

Classification Practice

Problem Solving

Extract Problem State, Goal, and Constraints

For each case, write a clear problem state, a specific goal state, at least three constraints, and at least two available resources.

Four practical problems

These are deliberately messy. Extract the structured triad from each.

Case 1 — Assignment recovery

A student realizes they missed two assignments and now has limited time before finals. The instructor only accepts one late assignment, and the student also has two other exams. The semester ends in one week.

Separate the facts from the feelings and list real constraints.

Case 2 — Team conflict

Two members of a four-person project team disagree sharply on the direction of a deliverable. The deliverable is due in ten days and requires both members' expertise. A partial draft exists but it doesn't reflect either member's preferred approach.

The problem state includes more than just 'they disagree'.

Case 3 — Moving budget

A graduate student needs to move 400 miles for an internship that starts in three weeks. They have $800 saved, a car with unknown long-distance reliability, three weeks of remaining rent, and a friend in the destination city who has offered a couch for one week. They also have a final exam in their current program one week before moving.

List the constraints and resources explicitly.

Case 4 — Product bug

An engineer discovers that a production system returns incorrect results for about 2% of requests. The bug has been present for at least three weeks. Reverting the last deployment would remove some bug fixes that customers have asked for. The on-call engineer has just been assigned but has never seen this part of the code.

What's the goal state? Fix the bug? Restore correctness? Both?

Not saved yet.

Quiz

Problem Solving

Scenario Check: Understanding the Problem Before Solving It

Each question presents a scenario or challenge. Answer in two to four sentences. Focus on showing that you can use what you learned, not just recall it.

Scenario questions

Work through each scenario. Precise, specific answers are better than long vague ones.

Question 1 — Diagnose

A student makes the following mistake: "Jumping to a solution before describing the actual problem." Explain specifically what is wrong with this reasoning and what the student should have done instead.

Can the student identify the flaw and articulate the correction?

Question 2 — Apply

You encounter a new argument that you have never seen before. Walk through exactly how you would describe problem state, starting from scratch. Be specific about each step and explain why the order matters.

Can the student transfer the skill of describe problem state to a genuinely new case?

Question 3 — Distinguish

Someone confuses problem state with goal state. Write a short explanation that would help them see the difference, and give one example where getting them confused leads to a concrete mistake.

Does the student understand the boundary between the two concepts?

Question 4 — Transfer

The worked example "Missed Assignment Recovery" showed one way to handle a specific case. Describe a situation where the same method would need to be adjusted, and explain what you would change and why.

Can the student adapt the demonstrated method to a variation?

Not saved yet.

Guided Problem Solving

Problem Solving

Strategy Selection: Understanding the Problem Before Solving It

Read each problem scenario. Identify the most appropriate problem-solving strategy, justify your choice, and outline the first three steps of your solution.

Practice scenarios

Work through each scenario carefully. Apply the concepts from this lesson.

Problem 1

A hospital needs to reduce emergency room wait times from 4 hours to under 1 hour. Budget increases are not possible. Staff are already working overtime.

Problem 2

A software team discovers that 80% of their bugs come from 20% of their modules. They have 6 weeks before release and need to cut the bug rate in half.

Problem 3

A city wants to reduce traffic congestion but cannot build new roads. Public transit ridership is declining despite subsidies.

Not saved yet.

Analysis Practice

Problem Solving

Constraint Analysis: Understanding the Problem Before Solving It

Identify the constraints, assumptions, and trade-offs in each problem. Which constraints are hard (non-negotiable) and which are soft (flexible)?

Practice scenarios

Work through each scenario carefully. Apply the concepts from this lesson.

Scenario A

A school must improve test scores within one academic year using only existing staff. The principal believes smaller class sizes are the answer, but the building has no additional rooms.

Scenario B

A restaurant wants to add delivery service but the kitchen is already at capacity during peak hours, and hiring new cooks would take months of training.

Not saved yet.

Evaluation Practice

Problem Solving

Evaluate Solutions: Understanding the Problem Before Solving It

Three proposed solutions are offered for each problem. Evaluate each on feasibility, effectiveness, and potential unintended consequences. Recommend the best option.

Practice scenarios

Work through each scenario carefully. Apply the concepts from this lesson.

Problem

A university library is running out of physical shelf space. Solution A: Digitize all books and remove shelves. Solution B: Build an off-site storage facility and retrieve books on request. Solution C: Remove books not checked out in 10 years.

Problem

A factory's error rate is 5%. Solution A: Add a second quality inspector. Solution B: Retrain all workers. Solution C: Replace the oldest 20% of machines.

Not saved yet.

Guided Problem Solving

Problem Solving

Deep Practice: Understanding the Problem Before Solving It

Each scenario presents a multi-constraint problem. Define the problem clearly, identify constraints, generate solutions, evaluate trade-offs, and recommend an approach.

Complex problem scenarios

Apply a structured problem-solving framework to each case. Address feasibility, risks, and implementation steps.

Scenario A

A school district must reduce its budget by 15% without laying off teachers or closing schools. Current spending: 60% salaries, 20% facilities, 10% supplies, 10% transportation. Student enrollment is increasing 3% annually.

Scenario B

A software startup has 4 developers and 6 months to build a product that typically takes a team of 10 one year. They cannot hire more staff but can use open-source tools. The product must be secure enough for healthcare data.

Scenario C

A coastal town's only freshwater source (a river) is projected to decrease by 30% due to upstream damming. The population is growing. Desalination costs 5x more than river water. The town budget cannot increase.

Not saved yet.

Guided Problem Solving

Problem Solving

Real-World Transfer: Understanding the Problem Before Solving It

Apply structured problem-solving to real-world challenges. Use the frameworks from this lesson to develop actionable recommendations.

Real-world problem solving

Use a structured approach: define the problem, identify constraints, generate options, evaluate, and recommend.

Community challenge

A neighborhood has a growing problem with package theft from doorsteps. Solutions tried so far (security cameras, signed delivery) have not reduced theft. The neighborhood association has a small budget. Develop a creative solution.

Workplace challenge

A team of 8 remote workers in 4 time zones needs to collaborate on a project with a 3-month deadline. Previous remote projects have suffered from miscommunication and duplicated work. Design a coordination strategy.

Not saved yet.

Rapid Identification

Problem Solving

Timed Drill: Understanding the Problem Before Solving It

For each scenario, quickly identify: (1) the core problem, (2) the main constraint, and (3) one feasible first step. Work fast but be specific.

Rapid problem decomposition

Decompose each problem in under 60 seconds. Identify the core issue, primary constraint, and a concrete first step.

Item 1

A food bank receives 30% more donations in December than it can store. Much of it spoils before distribution.

Item 2

A school bus route takes 90 minutes because it serves three neighborhoods in sequence. Parents are complaining about early pickup times.

Item 3

A non-profit website gets 10,000 visits per month but only 50 donations. The donation button is on a separate page from the stories.

Item 4

A clinic has a 3-week wait for appointments, but 20% of scheduled patients do not show up.

Item 5

A warehouse ships 500 orders daily but the error rate is 8%. Most errors involve wrong quantities rather than wrong items.

Not saved yet.

Evaluation Practice

Problem Solving

Peer Review: Understanding the Problem Before Solving It

Below are sample student solutions to problems. Evaluate each: Did they define the problem clearly? Did they consider constraints? Are their solutions feasible? What did they overlook?

Evaluate student problem solutions

Each student proposed a solution to a real-world problem. Assess their approach.

Student A's solution

Problem: A library wants to increase youth attendance. Student A wrote: 'Solution: Add a gaming lounge with consoles and high-speed internet. Young people love gaming, so this will bring them in. Cost estimate: $15,000 for equipment. Expected result: 50% increase in youth visits.'

Student B's solution

Problem: A rural clinic needs more doctors. Student B wrote: 'Offer student loan forgiveness for doctors who commit to 3 years. This addresses the financial barrier. However, the clinic budget is limited. We could partner with the state medical school for funding. Risk: doctors may leave after the commitment period.'

Student C's solution

Problem: Plastic waste in a coastal town. Student C wrote: 'Ban all single-use plastics immediately. This will eliminate the source of waste. Similar bans worked in other countries. Implementation: pass a local ordinance next month and begin enforcement.'

Not saved yet.

Guided Problem Solving

Problem Solving

Construction Challenge: Understanding the Problem Before Solving It

Design a complete solution from scratch. You are given only a problem statement. Build a structured response including problem definition, constraint analysis, solution generation, evaluation criteria, and an implementation plan.

Build complete solutions

For each challenge, construct a full problem-solving framework with explicit reasoning at every stage.

Task 1

A mid-sized city wants to reduce food waste by 50% within three years. Currently, 40% of food waste comes from restaurants, 35% from households, and 25% from grocery stores. Design a comprehensive solution addressing all three sources.

Task 2

A university wants to reduce cheating on online exams without making the exam experience stressful for honest students. Current proctoring software has a 15% false-positive rate. Design a better system.

Task 3

An island community of 5,000 people wants to become energy-independent within five years. They currently import all fuel by ship. The island has strong winds, moderate sunlight, and geothermal activity. Design an energy transition plan.

Not saved yet.

Diagnosis Practice

Problem Solving

Counterexample Challenge: Understanding the Problem Before Solving It

For each proposed solution, identify a realistic scenario where it would fail badly. Explain what assumption the solution makes that your counterexample violates.

Break the solution

Each solution seems reasonable. Find a realistic scenario where it fails and explain why.

Solution 1

Problem: Reducing traffic congestion. Proposed solution: Make public transit free. Find a scenario where this backfires or fails to reduce congestion.

Solution 2

Problem: Improving employee retention. Proposed solution: Increase salaries by 20%. Find a scenario where this does not solve the retention problem.

Solution 3

Problem: Reducing hospital readmissions. Proposed solution: Schedule follow-up appointments before patients are discharged. Find a scenario where this approach fails.

Solution 4

Problem: Reducing food waste in school cafeterias. Proposed solution: Let students choose their portion sizes. Find a scenario where this makes the problem worse.

Not saved yet.

Guided Problem Solving

Problem Solving

Integration Exercise: Understanding the Problem Before Solving It

These exercises combine structured problem-solving with formal reasoning, evidence evaluation, and explanatory analysis. Use every tool in your reasoning toolkit.

Cross-topic problem-solving exercises

Each problem requires structured problem-solving combined with other reasoning types.

Scenario 1

A city council must decide whether to invest in a new water treatment plant. Data: current system serves 50,000 people and is at 95% capacity. Population is growing at 2% annually. The new plant would cost $80 million. An alternative is to reduce per-capita usage through conservation programs. Apply problem-solving frameworks, use inductive projections for population growth, and construct a deductive argument for or against the investment.

Scenario 2

A tech company's AI model shows bias in hiring recommendations. The team must fix the bias without reducing the model's overall accuracy. Apply: (1) problem-solving to define constraints, (2) abductive reasoning to explain why the bias emerged, (3) deductive reasoning to determine what fairness criteria logically require.

Scenario 3

A school district must allocate a fixed budget between math tutoring and reading programs. Research shows both are effective but reading programs show stronger results for younger students while math tutoring benefits older students more. Use inductive evidence to evaluate program effectiveness, deductive reasoning to apply budget constraints, and problem-solving frameworks to design an optimal allocation.

Not saved yet.

Diagnosis Practice

Problem Solving

Misconception Clinic: Understanding the Problem Before Solving It

Each item presents a common misconception about problem-solving methodology. Identify the error, explain why it leads to poor solutions, and describe the correct approach.

Common problem-solving misconceptions

Diagnose and correct each misconception about structured problem-solving.

Misconception 1

A student says: 'The first step in problem-solving is to generate solutions. You should brainstorm answers immediately before the problem gets worse.'

Misconception 2

A student claims: 'A solution that worked in one context will always work in a similar context. Best practices are universal.'

Misconception 3

A student writes: 'The optimal solution is always the one that completely solves the problem. Partial solutions are failures.'

Misconception 4

A student argues: 'Constraints are always obstacles. The more constraints you have, the worse your solution will be.'

Misconception 5

A student says: 'Once you have found a working solution, there is no reason to look for alternatives. Efficiency means going with the first thing that works.'

Not saved yet.

Guided Problem Solving

Problem Solving

Scaffolded Solution: Understanding the Problem Before Solving It

Build a solution in stages. Each task walks you through a structured problem-solving process step by step. Complete each stage before moving to the next.

Step-by-step solution building

Work through each stage of the problem-solving process explicitly.

Scaffold 1

Problem: A community health clinic has a 40% no-show rate. Stage 1: Define the problem precisely -- what are the actual costs and impacts? Stage 2: Identify at least 4 constraints (budget, staff, technology, patient demographics). Stage 3: Generate 5 potential solutions. Stage 4: Evaluate each solution against your constraints. Stage 5: Design an implementation plan for your top solution.

Scaffold 2

Problem: A company's customer support response time is 48 hours, but the industry standard is 4 hours. Stage 1: Decompose the problem -- where does time go? Stage 2: Identify root causes (staffing, tools, processes, training). Stage 3: Generate solutions targeting each root cause. Stage 4: Evaluate trade-offs (cost vs. speed vs. quality). Stage 5: Propose a phased implementation plan.

Not saved yet.

Guided Problem Solving

Problem Solving

Synthesis Review: Understanding the Problem Before Solving It

These exercises combine all problem-solving skills: problem definition, constraint analysis, solution generation, evaluation, implementation planning, and risk assessment.

Comprehensive problem-solving review

Apply the full structured problem-solving process to each challenge.

Comprehensive 1

A mid-sized city (population 300,000) wants to become carbon-neutral by 2040. Current state: 50% of energy comes from natural gas, 30% from coal, 20% from renewables. Transportation is 90% fossil-fuel vehicles. The city's budget cannot increase, but state and federal grants are available. There are three coal-dependent neighborhoods where 15,000 jobs are at stake. Apply a complete problem-solving framework: define sub-problems, map constraints, generate solutions per sector, evaluate trade-offs, and create a phased 15-year plan.

Comprehensive 2

A regional hospital network (5 hospitals, 2,000 beds) must prepare for a potential surge of 3x normal patient volume while maintaining standard care. Constraints: cannot build new facilities in time, staff are already near burnout, supply chains are strained, and rural hospitals have fewer resources than urban ones. Design a comprehensive surge plan with prioritization criteria, resource allocation strategies, and contingency options.

Not saved yet.

Animated Explainers

Step-by-step visual walkthroughs of key concepts. Click to start.

Read the explanation carefully before jumping to activities!

Riko

Further Support

Open these only if you need extra help or context

Mistakes to avoid before submitting
  • Describing the goal vaguely enough that any action seems acceptable.
  • Omitting constraints that are inconvenient to mention.
Where students usually go wrong

Jumping to a solution before describing the actual problem.

Treating wishes as if they were available resources.

Writing vague goals that no one could verify.

Historical context for this way of reasoning

George Polya

Polya emphasized that understanding the problem is its own stage of reasoning, not a disposable preface. His first stage asks the solver to identify the unknown, the data, and the condition — roughly the same triad as the goal state, problem state, and constraints.