Skip to content
Mathematics · META · Ages 7–8

Multi-Step Problem Solving

With teacher support, make sense of multi-step problems involving larger numbers or mixed operations by breaking them into parts, choosing strategies, and checking answers for reasonableness — children at this stage are developing the habit with guidance; independent strategy evaluation comes later

Lesson: Multi-Step Problem Solving

Subject: Mathematics · Domain: Mathematical Thinking · Age band: 7–8 (tailored for gifted 5y9m) · Type: META Centrality: 0.104 (foundational reasoning habit, not a discrete skill) Taxonomy ID: mt_RKeheOL9uo · Standards: CCSS.MATH.PRACTICE.MP1, MP4, MP7 Tailored for: Asynchronous learner, IQ 125–130+, grade 2–3 math, 5-year-old social-emotional

Your son can already do multi-digit addition and subtraction. What he likely hasn't built yet is the metacognitive layer: noticing when an answer is nonsense, breaking a problem into sub-parts deliberately, and choosing a strategy on purpose rather than grabbing the first one. That's what this lesson targets. The arithmetic will feel easy to him — that's the point. We're after the thinking about thinking, not the calculation.


Why this matters

This is one of those quiet, high-leverage habits that separates kids who are "good at math" from kids who think like mathematicians.

Right now your son likely solves problems by pattern-matching: he sees numbers, picks an operation, computes. That works beautifully — until it doesn't. The problem with pattern-matching is that when a problem has two steps, or when the answer comes out ridiculous (like "the train has 3,000 passengers"), he may not notice. He trusts his procedure.

Multi-step problem solving is where the procedure-without-concept trap hides for gifted kids. He'll get the right answer often enough to look like he understands, but the underlying habit — pause, decompose, estimate, check — hasn't formed yet. This lesson builds that habit explicitly.

For your son specifically, this is likely where he actually lives developmentally: the math is easy, but the executive function of holding multiple steps in mind, sequencing them, and self-monitoring is age-appropriate 5-year-old work. That gap is normal and expected. You're not behind — you're ahead, which is why you're hitting this now.


Learning objective

Your son will break a two-step word problem into sub-problems, estimate a reasonable answer range before computing, and check his answer using a different strategy.

Sentence you want him to be able to say: "Before I solve, I figure out what steps I need. After I solve, I check if my answer makes sense."


Before you sit down together

Materials

  • Small objects for modeling (LEGO bricks, dry pasta, counters) — even though he's past counting, physical objects make the "two steps" visible and slow him down enough to think
  • Index cards or sticky notes — for covering up parts of the problem, forcing one-step-at-a-time reading
  • Blank paper and pencil — for drawing the problem, writing estimates, recording strategies
  • A number line (0–100, printable or hand-drawn) — for the "is this reasonable?" check
  • Whiteboard or large paper — so you can scribe his thinking visibly

No worksheets. The power of this lesson is in oral reasoning, not written output.

Best time of day for this lesson

Mid-morning, after a snack and some physical movement, works well for most 5-year-olds. You want him fed, alert, and not coming off screen time.

Avoid: right before transitions, late afternoon, or when he's already done another demanding cognitive task. This lesson asks for flexible thinking, which is the first thing to go when he's tired or hungry.

If he's in a silly or resistant mood, shelve it. Metacognition requires a regulated nervous system.


Activity: "The Two-Step Detective"

This is a META lesson — we're building the habit of thinking, not a specific procedure. The structure is Prompt → Reflect → Plan → Wrap-up.

Total time: 15–20 minutes. Stop sooner if he's done. Push longer only if he's in flow.


Phase 1: Prompt — Introduce the problem (4–5 min)

Present one problem, read aloud, then do nothing. Let him sit with it.

The problem:

"You have 24 LEGO bricks. You build a tower and use 8 bricks. Then your brother gives you 15 more bricks from his bin. How many do you have now?"

Resist the urge to ask "what should you do first?" Let him look at it.

If he immediately says "31!" — that's a flag. He may have computed without reading carefully, or he may have genuinely done both steps mentally. You'll find out in the next phase.

Sample dialogue:

"Here's a problem. I'm going to read it once, and then I'm just going to be quiet and let you think. You don't have to solve it yet — I just want you to think about what's happening in the story."

Read slowly. Pause. Wait at least 10 seconds. Count silently if you need to.


Phase 2: Reflect — Make the steps visible (5–6 min)

Now you help him externalize his thinking. The goal isn't the answer — it's making his reasoning visible so he can examine it.

Ask:

  • "What happened first in the story? Then what happened?"
  • "How many different things do you need to figure out?"
  • "Could you draw what's happening?"

Sample dialogue:

"Some kids see this and think 'two things happened.' First you used some bricks, then you got more. Can you show me both parts? You could draw it, or use the bricks, or just tell me."

If he draws or acts it out — excellent. If he says "I just know it's 31" — you might say:

"That might be right! Let's check by doing it a different way. What if we use the actual bricks — start with 24, take away 8, then add 15?"

This is where you catch the pattern-matchers. If his mental answer was wrong, the physical model will reveal it. If it was right, he's now confirmed it two ways — which is the entire point.


Phase 3: Plan — The estimate-and-check habit (4–5 min)

This is the heart of the lesson for your son. Before he computes (or after, if he already did), introduce the reasonableness check.

Sample dialogue:

"Before we trust our answer, mathematicians do something called estimating. That means getting a rough idea first — not the exact number, just close. So: you started with 24, and you took some away, and then you got more. Should your answer be bigger than 24, smaller than 24, or about the same?"

If he says "bigger" — ask why. If he says "smaller" — that's informative; he may be anchoring on "took away" without weighting the +15.

Then:

"About how much bigger? A little or a lot?"

You're building number sense scaffolding here — a feel for magnitude that protects him from accepting absurd answers later.

If you haven't already, now compute (or confirm) the answer: 24 − 8 = 16, then 16 + 15 = 31.


Phase 4: Wrap-up — Name the habit (2–3 min)

Don't skip this. The naming is what makes the strategy available to him next time.

Sample dialogue:

"You just did something really smart. You broke a hard problem into two smaller problems. That's called decomposing. And you checked if your answer made sense. That's what mathematicians do — they don't just compute, they think about whether their answer is reasonable."

Ask:

  • "What would you do if your answer had been 200? Would that make sense?"
  • "What if it had been 5?"

Let him laugh at the silly answers. That's him calibrating reasonableness.


Kid-response scripts

He says... What's happening You might try...
"31! I just know." Fast mental math, possibly correct, but no visible reasoning "That might be right! Can you prove it to me with the bricks? Mathematicians check their answers a second way."
"I don't know what to do." Multiple steps feel overwhelming; he can't see the entry point "Let's just do the first thing that happened. You had 24 and used 8. What's that?" Break the invisibility of the first step.
Solves only the first step and stops. He's treating it as a one-step problem; didn't register the second event "Great — so now you have 16. But the story isn't over! What happened next?" Re-read the second sentence.
"It's 47." (added both numbers) Pattern-matched "give you" = addition, missed the subtraction "Let's act it out. Start with 24 bricks. Use 8 for a tower — how many are left?" Let the physical model correct him.
"This is too easy." He's right — jump to Stretch "You're right, this one's easy. Let me give you a harder one." Move immediately to Stretch. Don't make him sit through easy.
"I used 24 plus 15 minus 8." He reordered the steps — this is mathematically valid! "Oh interesting — you did the steps in a different order. Does that work? Let's check both ways and see if we get the same answer." Celebrate flexible thinking.
Gets frustrated when answer doesn't match estimate Good sign — he's monitoring, but not yet coping with being wrong "That's your math brain working! The fact that you noticed something's off means you're thinking like a mathematician. Let's find where it went sideways."

Common misconceptions to watch for

What you see What's actually going on How to gently address
Adds all the numbers in the problem No operation sense — treating numbers as a set to combine Act it out physically. "Watch — did I get bigger or smaller when I used the bricks?" Build the plus/minus meaning from the action.
Correct arithmetic, wrong operation sequence Can compute but isn't parsing the problem's logic Use the index cards to cover the problem. Reveal one sentence at a time. Solve each sentence before reading the next.
Never estimates, just computes Hasn't formed the habit; estimates feel like "extra work" Model estimating yourself out loud. "I don't know the answer yet, but I bet it's around 30-ish because..." Normalize estimating as part of solving, not separate.
Changes the problem to make it one-step Avoiding the hard part; wants the comfortable version Acknowledge it. "You changed the problem to make it easier — that's actually smart! But let's also try the harder version. I'll help."

Stretch (where the real lesson lives for your son)

Your son may blow through the main lesson. That's expected. These extensions go deeper — not just harder numbers, but more complex reasoning.

Stretch 1: Three-step problems (5 min)

"A zoo has 4 monkey cages. Each cage has 6 monkeys. The zoo sends 5 monkeys to another zoo. Then 3 new baby monkeys are born. How many monkeys are there now?"

This brings in multiplication (which he's touched) plus two more steps. The key question isn't the arithmetic — it's:

"How many different things happened in this story? Can you list them?"

If he lists "multiply, subtract, add" — that's exactly what you're after.

Stretch 2: The missing information problem (5 min)

"Sam had some markers. He gave 7 to his friend. Now he has 12. How many did he start with?"

This is an inverse problem — the "start" is unknown. It requires working backwards, which is a different kind of multi-step thinking. Gifted kids often love these because they feel like puzzles.

Ask: "Can you draw what happened, but backwards?"

Stretch 3: Create your own problem (5–7 min)

Ask him to write a two-step word problem for you to solve.

This is powerfully meta: to write a good problem, he has to hold both steps in his head, make sure the numbers work, and know the answer. If his problem is one-step, ask:

"Can you make it trickier — add one more thing that happens?"

When you solve his problem, model the thinking you want him to develop:

"Okay, first I'm going to estimate... then I'll solve the first part... then the second..."

Let him watch you use the strategy.

Stretch 4: The "wrong answer" critique (5 min)

Present a solved problem with a deliberate error:

"Tina had 40 stickers. She gave 15 to her sister. Then she got 10 more. The answer is 65."

Ask: "Do you agree with Tina? Why or why not?"

This develops the evaluation level of Bloom's taxonomy — judging someone else's reasoning, not just producing your own. For a gifted 5-year-old, this is cognitively rich and usually fun.


Quick mastery check (60 seconds)

  • [ ] Given a two-step problem, can he identify both steps before solving? ("What two things happen in this story?")
  • [ ] Does he estimate or check reasonableness without prompting? ("Does your answer make sense? How do you know?")
  • [ ] Can he explain his strategy, not just his answer? ("How did you figure that out?")

If he passes all three cleanly, he's already here. Move to the Stretch problems as your main lesson.


Formal mastery check

From the taxonomy evidence fields:

  • [ ] Break a two-step word problem within 1000 into sub-problems and solve each part. (Present a problem like: "A library has 450 books. They buy 120 more. Then they lend out 85. How many books are in the library now?")
  • [ ] Estimate answer before calculating and set a reasonableness benchmark. (Ask: "Before you solve — will the answer be closer to 300, 500, or 600?")
  • [ ] Check answer using a different method (inverse operation) and revise if needed. (After solving, ask: "Can you check that a different way?")

Assessment prompt from dataset: If he gets an answer that seems way too big or too small in a math problem, does he notice and go back to check, even without you pointing it out?

This last one is the truest measure. Spontaneous self-correction is the signature of mathematical thinking. If he does this unprompted, he's mastered the core habit.


Vocabulary to use naturally

Drop these into conversation — don't pre-teach them:

  • Decompose — "Let's decompose this problem into smaller parts."
  • Reasonable — "Is 450 a reasonable answer for this problem?"
  • Estimate — "Let's estimate first before we calculate."
  • Strategy — "That's one strategy. What's a different strategy we could try?"
  • Inverse — "Addition and subtraction are inverse operations — one undoes the other."
  • Sub-problem — "Each part of this story is a sub-problem."

What comes next

This lesson is foundational for several downstream topics:

  1. Multi-Step Problem Solving (age 8–9 level) — the next iteration involves larger numbers, more steps, and more independent strategy selection without teacher prompting. The habit you're building now is what makes that possible.

  2. Choosing Strategy (age 9–10) — eventually he'll evaluate which strategy is most efficient for a given problem. That requires the habit of pausing and reflecting that this lesson introduces. He can't choose a strategy if he doesn't notice he has a choice.

  3. Estimating and rounding — the reasonableness checks in this lesson feed directly into formal estimation skills. If he's already asking "does this make sense?", the conceptual groundwork for rounding and estimation is laid.


If this lesson didn't land

Some days, even the best lesson doesn't work. Here are fallback strategies:

Try a different manipulative. If LEGO bricks didn't work, try coins, grapes, or drawn circles. Sometimes the physical material itself creates the engagement. The concept is the same; the delivery changes.

Switch the context. If word problems about LEGO don't grab him, rewrite the same problem structure with his current obsession — dinosaurs, Minecraft, spaceships, whatever it is this week. The math doesn't change, but motivation might.

Shorten and return. If he's done after one problem, that's fine. Come back tomorrow with a fresh problem. Spaced practice across days builds habits better than one long session anyway.

Skip to Stretch 3 (create-your-own). Some gifted kids resist solving problems but love making them. Flip the dynamic. Let him be the problem-setter.

Check the prerequisite. If he genuinely can't follow the two steps, it may be that the working memory load is too high right now. Try the same lesson with single-digit numbers (e.g., "You have 8 crackers. You eat 3. Mom gives you 2 more."). Reduce cognitive load and build up. The strategy is the same; the numbers shrink.


Source

  • Taxonomy ID: mt_RKeheOL9uo
  • Dataset: Learning Taxonomy (Mathematics, Mathematical Thinking)
  • Standards: CCSS.MATH.PRACTICE.MP1 (Make sense of problems & persevere), MP4 (Model with mathematics), MP7 (Look for & make use of structure)
  • Generated by: Parent-facing lesson builder, tailored for gifted asynchronous learner (IQ 125–130+, age 5y9m)

A final note: you're not teaching your son to solve this one problem. You're teaching him to notice his own thinking. That habit, once started, compounds for years. The single most valuable thing you can do in this lesson is model the pause — the moment between reading the problem and computing — and make that pause feel normal and powerful. Everything else flows from there.