Math // Mathematical Thinking

Complex Multi-Step Problems

Make sense of complex multi-step problems involving large numbers, fractions, decimals, and percentages by analysing what is known and unknown, planning multi-step strategies, and evaluating reasonableness through estimation and inverse operations

Ages
9 to 10
Type
Thinking skill
Builds on
4 topics
Leads to
1 topic

Quick check

When the learner faces a complex multi-step maths problem involving percentages, large numbers, or fractions, do they pause to identify what's known, estimate an answer, and then check their final result makes sense?

Ask this to see whether the topic is secure.

Topic // Mastery

What mastery looks like

What a learner can do once this topic is secure.
  • Break a three-step problem involving unit conversion and multiplication into sub-problems and solve systematically
  • Estimate 4,832 × 7 as roughly 5,000 × 7 = 35,000 to check a calculated answer of 33,824
  • Identify that a percentage answer over 100% doesn't make sense in context

Topic // Map

Where this fits

What to learn first and what this topic opens up, with the reason for each link. Required links come first.
  • RequiredMust come first
  • HelpfulHelps, but not essential

Before this

4 topics
  • Mathematical Thinking // Ages 8 to 9

    Age 8-9 problem sense-making is prerequisite to age 9-10 level

  • Fractions // Ages 9 to 10

    Percentage problems exercise multi-step reasoning

  • Multiplication & Division // Ages 9 to 10

    Multi-step word problems exercise problem sense-making at age 9-10

  • Learning to Learn // Learning to Learn // Ages 9 to 10

    Planning multi-step mathematical strategies and evaluating them is the maths-specific form of the universal strategy-evaluation habit

You are here

Complex Multi-Step Problems

Ages 9 to 10 // Thinking skill

Leads to

1 topic

Topic // Research-informed

Teaching notes

From the Marble Skill Taxonomy. These notes have not been validated in classrooms, so treat them as a starting point for your own judgement.

The approach

For 9-10 year olds tackling complex problems of three or more steps that span large numbers, fractions, decimals, and percentages (often with unit conversion), the goal is to make estimation-as-benchmark, inverse-operation checking, and magnitude sense into trusted, routinely-used tools. The dominant threats are the keyword strategy (choosing operations from cue words), the compulsion to calculate (computing without checking reasonableness), and weak magnitude sense (accepting a percentage over 100%, or a 'part' larger than the whole, as a part of a fixed group). Activities centre on: estimate-first routines that set a magnitude band before computing, student-built representations (bar models, double number lines, strip diagrams) that expose problem structure, explicit known/unknown analysis, and modelled self-questioning to monitor long solutions.

Common misconceptions

  • Keyword strategy on complex problems — operations chosen from words, wrong order
  • No estimate/reasonableness check — accepting a computed answer that rounding would flag as wrong (compulsion to calculate)
  • Weak magnitude sense — accepting a percentage over 100% or a 'part' larger than the whole as a valid answer in context
  • Losing track across three or more steps — not monitoring what has been found versus what remains

Useful representations

  • Rounding/estimation to a benchmark (≈ 5,000 × 7) for reasonableness
  • Bar model and double number line for percentages/decimals
  • Strip diagram for fraction sub-steps
  • Inverse-operation check (work backwards)
  • Known/unknown analysis with a letter for the unknown

Teaching practices

  • Estimate first with rounding to set a magnitude benchmark, then compute, then check against the estimate; verify with inverse operations
  • Analyse known vs unknown explicitly before planning; represent the unknown (letter or bar) rather than rushing to combine numbers
  • Teach magnitude sense for percentages and decimals: a part cannot exceed 100% of the whole; sense-check the size of decimal answers
  • Build the student's own diagram (bar/double-number-line for percentages, strip for fractions) to expose sub-structure (WWC Rec 3)
  • Model self-questioning to monitor progress across three or more steps (WWC Rec 2)
  • Teach structure/schema over keywords — keyword matching is unreliable and collapses on multi-step problems

Activities to try

  1. 1

    Estimate-first complex-problem solver

    Why it works: An answer can be rejected by your own estimate and by plain context, not just by a teacher. Estimation and magnitude sense become tools you trust, and a long problem stays manageable when its sub-structure is laid out and monitored.

    1. Take a three-step problem, e.g. finding a percentage of a large quantity that also requires a unit conversion, and lay it out as separate sub-step cards so each step is visible.
    2. Build your own representation for the key step: a double number line or bar model for the percentage step, a strip diagram for a fraction step.
    3. Before computing, round each number and place an estimate into a benchmark band (e.g. round 4,832 to about 5,000, so 4,832 × 7 should be about 35,000).
    4. Compute each sub-step, then compare the computed answer against your own estimate band, and against what makes sense in context (e.g. a 'part' of a fixed group cannot be more than everyone in it).
    5. Keep a running 'found so far / still to find' tracker so you don't lose your place across the steps.
  2. 2

    Known/unknown analysis before computing

    Why it works: The plan should come from the structure of the problem, not from matching keywords to operations, which is unreliable and breaks down on multi-step problems.

    1. Before touching the numbers, write down what is known and what is unknown in the problem.
    2. Represent the unknown explicitly — with a letter or a bar — rather than rushing to combine numbers.
    3. State a plan for the order of steps, explaining why that order, based on how the quantities relate rather than on cue words.
    4. Discuss why a cue word (e.g. 'altogether', 'left') can point to the wrong operation on a multi-step problem.
  3. 3

    Reasoning partner that prompts (does not supply)

    Why it works: Articulating the monitoring routine — analyse, estimate, sense-check magnitude, verify by inverse — makes it habitual and portable to new problems.

    1. Work through a long problem with a partner (teacher, peer, or in-role coach) who asks, not tells.
    2. Answer prompts aloud: 'What's known and unknown? What's your estimate? Could that percentage be right — more than everyone? Can you check it a different way, working backwards?'
    3. Justify your magnitude reasoning aloud, e.g. explain why 130% of the pupils cannot be a valid part of a fixed whole group.

Math // Mathematical Thinking