Small Group Tutorials

Here to help students catch up, keep up, and move ahead. Book a consultation here.

Primary 5 Mathematics Learning Guide | Simplify the Problem, Solve a Smaller Case & Rebuild the Original

PRIMARY 5 MATHEMATICS LEARNING GUIDE · BATCH 12 · GUIDE 47

Simplifying a problem means reducing its complexity while preserving the structure that makes it mathematically interesting. The goal is not to dodge the original task. The goal is to reveal the mechanism in a smaller, friendlier or more visible case, then return to the original with a tested model.

This heuristic is especially useful for visual patterns, systematic search, complicated fractions, multi-stage processes, large-number arrangements and unfamiliar non-routine problems.

Return to the Primary 5 Mathematics Learning Hub. Related guides: Find a Pattern · Guess, Check, Improve · Mathematical Modelling.

1. What must stay the same?

Before simplifying, identify the structure that must be preserved. If the original problem is about a repeated growth rule, the smaller case must keep the same growth rule. If it is about changing percentage bases, the smaller case must still change the base at the same stages.

2. Friendly numbers can expose a relationship

If 37% of 482 is difficult to reason about, temporarily ask what 37% of 100 means. The simpler case reveals that 37% means 37 per hundred. Then return to the actual quantity.

3. Smaller cases are especially useful for patterns

If a figure has 50 stages, study stages 1 to 4 first. Record what changes from stage to stage. The smaller cases may reveal a constant addition, repeated cycle or geometric invariant.

4. Simplify size, not logic

Replacing 482 with 100 is legitimate if the same percentage relationship is being studied. Replacing a two-stage percentage problem with a one-stage problem may destroy the very structure causing difficulty.

5. Use a toy version of a search problem

If arranging 20 items under several rules feels opaque, try 4 or 5 items first. The smaller search can reveal which constraints eliminate cases and which choices branch.

6. Solve the small case completely

Do not merely glance at it. List all valid possibilities, compute the relevant quantities and explain why the result follows. A vague small case creates a vague generalisation.

7. Then ask what scales

Some features scale directly; others do not. If one extra square always adds three matchsticks, the added amount scales with the number of extra squares. But corner effects or shared boundaries may prevent simple proportional scaling.

8. Rebuild from the invariant mechanism

Once the small case shows the mechanism, express that mechanism in a form that can be applied to the original. The return step is what turns a classroom trick into mathematical reasoning.

9. Example: connected squares

One square uses 4 sticks, two use 7, three use 10. The small cases show each additional square adds 3. For 20 squares, 4+19×3=61 sticks.

10. Example: changing-whole percentages

Instead of starting with $482, test $100. Remove 20% → 80. Then remove 25% of remainder → remove 20, leaving 60. The structure reveals a final factor of 0.6. Apply that factor to the original quantity.

11. Example: fractional remainder

Take a simple original of 60. Remove 1/3 → 40 remains. Remove 1/4 of the remainder → 30 remains. This reveals the survival factors 2/3 and 3/4, so final is 1/2 of original.

12. Example: geometry decomposition

If a complex composite shape is difficult, first solve the same arrangement with clean side lengths such as 10 and 4. Focus on which rectangles or triangles are added and subtracted. Then return to the original dimensions.

13. Simplify units when conversions distract

If the structure is about rate rather than unit conversion, temporarily use consistent units. Once the rate relationship is understood, restore kilometres, metres, hours or minutes carefully.

14. Simplify a table

If a table has ten rows, examine two or three representative rows. Look for the rule connecting input and output before processing every row.

15. Simplify a before–after model

Use smaller totals with the same transfer rule. If 20 moves internally in the large problem, model a version where 2 moves. Observe that the difference changes by twice the transfer.

16. Simplify to check feasibility

Before calculating a huge search, test whether the constraints can even coexist in a small analogue. Contradictions often appear early.

17. Smaller cases can reveal parity

Build the first few cases and record whether totals are odd or even. If a process always changes the total by 2, parity stays unchanged. That invariant can eliminate impossible targets.

18. Smaller cases can reveal remainder cycles

For repeating arrangements, list positions through one or two full cycles. Then use quotient and remainder instead of extending to position 100 manually.

19. Simplify an assumption problem

If there are 50 objects of two types, test a 5-object analogue. The smaller case can reveal that replacing one type with another changes the total by a fixed amount.

20. Simplify unknowns by fixing one quantity

Sometimes choose a convenient temporary value for one unit. If A and B are in a 3-unit to 5-unit relationship, let one unit=10 to understand the structure. Later recover the actual unit from the given total or difference.

21. Use simpler cases to discover, not to prove everything

A pattern seen in cases 1–4 is evidence, not automatically proof. The learner should still explain why the relationship continues.

22. Rebuild with an explicit mapping

Write which feature of the small case corresponds to which feature of the original. Example: “one extra square” in the small case is the same structural move as “one extra square” in the large case.

23. Beware of boundary effects

A rule that works in the middle of a pattern may behave differently at the first or last stage. Small cases help reveal such edge conditions.

24. Beware of accidental friendliness

Numbers such as 100 may make percentages easy but can hide whole-object or divisibility constraints that matter in the original. Restore those constraints during reconstruction.

25. Error map

ErrorCauseRepair question
Simplified case has different number of stagesStructure changedDid I preserve the same sequence of operations?
Pattern from two cases assumed universalInsufficient evidenceWhy must the rule continue?
Small-case answer scaled directly when it should notNonlinear or boundary effect ignoredWhat exactly scales?
Never returns to originalHeuristic incompleteHow does the discovered mechanism map back?

26. A six-step routine

  1. Name the hard feature.
  2. Choose a smaller or friendlier version.
  3. Preserve the essential structure.
  4. Solve the smaller case completely.
  5. State the discovered mechanism.
  6. Rebuild and verify the original.

27. Practice set A

  1. One connected square uses 4 sticks and each extra square adds 3. Use cases 1–3 to predict 12 squares.
  2. 100 items lose 20%, then 25% of remainder. What fraction of original survives?
  3. 60 items lose 1/3, then 1/4 of remainder. What fraction survives?
  4. A repeating colour cycle has 4 colours. Build one full cycle and identify the 29th colour position within the cycle.
  5. An internal transfer of x changes the difference by 2x. Test this with a simple 20/10 starting pair and transfer 3.

28. Practice set B

  1. A complex rectangle problem uses dimensions 48 and 27. Explain how a 12-by-6 analogue could help reveal decomposition without determining the original answer directly.
  2. A two-type ticket problem has 50 tickets. Explain why a 5-ticket analogue can reveal replacement difference.
  3. A sequence has 40 stages. What should you record for stages 1–5 before generalising?
  4. A search involves arranging 8 items under two constraints. Why might solving a 3-item version help?
  5. A percentage problem uses awkward $482. What can a $100 analogue reveal, and what must still be recomputed?

29. Answers and discussion

1. 4+11×3=37 sticks.

2. 0.8×0.75=0.6, so 60% survives.

3. 2/3×3/4=1/2.

4. 29÷4 leaves remainder 1, so the 29th item matches the first colour.

5. Start 20/10, transfer 3 internally → 17/13. Difference falls from 10 to 4, a decrease of 6=2×3.

6–10. The simplified cases are for exposing structure, not substituting for the original arithmetic. Each answer must explicitly map the discovered relation back to the original.

30. Full non-routine example

A staircase pattern has 1 square in the first row, 2 in the second, 3 in the third, and so on. How many squares are in the first 20 rows?

Simplify to 4 rows: 1+2+3+4=10. Pair first and last rows: 1+4=5, 2+3=5. Two pairs give 10. For 20 rows, pair 1+20, 2+19, …, 10+11. There are 10 pairs, each totaling 21.

Total=210 squares.

The smaller case reveals the pairing mechanism; the original uses the same structure.

31. Final checkpoint

A strong Primary 5 learner can simplify a difficult problem without destroying its structure, solve a smaller case completely, identify the mechanism rather than merely copy the answer, recognise boundary and divisibility effects, and rebuild the original with an explicit structural mapping and verification.

Continue to Primary 5 Mathematics Learning Guide | Spatial Visualisation: Rearrangement, Decomposition, Hidden Dimensions & Area–Perimeter Reasoning.