Math // Mathematical Thinking

Justifying mathematical reasoning

Construct and follow multi-step mathematical arguments; identify errors in reasoning and explain why a method works or does not work

Ages
7 to 8
Type
Thinking skill
Builds on
5 topics
Leads to
1 topic

Quick check

If the learner hears another child's explanation for how they solved a maths problem, can the learner say whether the reasoning makes sense — and if not, point out exactly where the logic goes wrong?

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.
  • Explain step by step why a columnar addition method gives the correct answer
  • Find and explain an error in a worked example (e.g. incorrect regrouping)
  • Construct a simple argument for why a general statement is true (e.g. 'adding two even numbers always gives an even number')

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

5 topics
  • Explaining Mathematical ReasoningRequired

    Mathematical Thinking // Ages 6 to 7

    Age 7-8 arguing/justifying builds on age 6-7

  • Describing AloudHelpful

    English // Speaking & Listening // Ages 4 to 8

    Cross-subject: constructing and following multi-step mathematical arguments requires the ability to express thoughts and give well-structured explanations orally

  • Adding and subtracting (age 7+)Helpful

    Addition & Subtraction // Ages 7 to 8

    Explaining columnar methods exercises identifying and justifying steps

  • Addition and subtraction strategies (age 7+)Helpful

    Addition & Subtraction // Ages 7 to 8

    Explaining why strategies work exercises constructing arguments

  • Teaching It BackHelpful

    Learning to Learn // Learning to Learn // Ages 7 to 8

    Constructing multi-step mathematical arguments and identifying errors in reasoning is the maths form of the universal self-explanation habit

You are here

Justifying mathematical reasoning

Ages 7 to 8 // 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 7-8 year olds learning to justify mathematical reasoning: help children move from checking a few examples toward arguing why a GENERAL statement must be true for all cases (the empirical-to-structural shift). Core moves: build multi-step because/therefore chains, use generic/visual proofs (an even number as pairs with none left over), disprove a universal claim with a single counter-example, and locate and explain the faulty step in a worked example grounded in place value. Accept examples as a starting point but explicitly name that examples illustrate rather than prove — treat this as a developmental milestone, not a mistake to punish.

Common misconceptions

  • Empirical proof scheme — treating a few confirming examples as proof that a general statement is always true
  • Convincing-not-justifying — a confident argument with missing steps, close to but not yet a complete chain
  • Identifying an error only as 'the answer is different' rather than naming the faulty step and why
  • Not realising that one counter-example is enough to disprove a general statement

Useful representations

  • Generic/visual proof (even number as pairs; place-value columns)
  • Counter-example as a disproof tool
  • Multi-step because/therefore chain
  • Worked examples containing deliberate errors
  • The justify → prove steps of the NRICH ladder

Teaching practices

  • Model the move from examples to a general argument: 'it works for these — but how do we know it works for EVERY even number?'
  • Use generic/visual proofs accessible at this age (an even number as pairs with none left over; two evens make pairs with none left over, so the total is even)
  • Teach disproof by counter-example — one case that breaks a statement is enough to show it is false
  • Use worked examples with errors (e.g. wrong regrouping) and require an explanation of which step is wrong and why, grounded in place value
  • Build multi-step because/therefore chains and check each link follows from the last
  • Accept examples as illustration but name explicitly that a few examples are not a watertight proof — this is a key development, not a failing to be punished

Activities to try

  1. 1

    Convince the friendly skeptic

    Why it works: When there are endlessly many cases, as with even numbers, no pile of examples can establish a claim for every case, but a structural reason can — and a single counter-example is enough to disprove a general ('always') statement even though many examples cannot prove one.

    1. State a general claim, e.g. 'adding two even numbers always gives an even number', and offer an example such as 4 + 6 = 10
    2. Respond to a partner (an adult or a role-play) who cheerfully agrees each example is even but keeps asking: 'Can you give me another? And another?'
    3. Face the key question: 'I believe every pair you've tried — but even numbers go on forever, so you could never check them all. How do you KNOW there isn't one pair that breaks it?'
    4. Reach for a reason that covers all cases at once, e.g. 'every even number is made of pairs with none left over, so two of them still make complete pairs, so the total is even'
    5. Then take a FALSE statement from the partner (e.g. 'adding two numbers always gives an even number') and topple it with a single counter-example such as 2 + 3 = 5
  2. 2

    Build and test an argument workspace

    Why it works: Testing cases can suggest a conjecture, but a generic argument built from how numbers are structured is what establishes it for every case. Always/sometimes/never sorting sharpens disproof: one counter-example rejects a claimed 'always', one confirming case rejects a claimed 'never', while a 'sometimes' claim needs a case each way.

    1. Take a statement such as 'two evens → even' and run it against several cases, noticing that no number of green ticks ever proves it for all cases
    2. Use a grouping tool (physical counters, drawn dots, or an on-screen manipulative) to split a number into pairs with none left over, then show that two such numbers still make complete pairs
    3. Sort statements into always / sometimes / never true. To reject a claim that something is ALWAYS true, give one counter-example that breaks it; to reject a claim that something is NEVER true, give one case where it does hold; for a statement that is genuinely SOMETIMES true, show both a case where it holds and a case where it does not
    4. Build the argument as a chain: 'every even number splits into pairs, SO two evens are pairs plus pairs, THEREFORE the total is even' — and check each link follows from the last
  3. 3

    Spot and explain the faulty step

    Why it works: Finding an error means naming the specific faulty step and the place-value rule it breaks, not merely observing that the answer looks different.

    1. Examine a worked columnar addition that contains a deliberate error (e.g. incorrect regrouping between the ones and tens columns)
    2. Locate the exact step that is wrong — not just notice the final answer differs from your own
    3. Explain WHY it is wrong in terms of place value, e.g. 'the ten that should have been carried into the tens column was dropped'
    4. Say what should have happened in that column to make it correct

Math // Mathematical Thinking

More in Mathematical Thinking

All 48 topics