PRIMARY 4 MATHEMATICS LEARNING GUIDE · BATCH 9 · GUIDE 33
When a mathematics problem feels complicated, one of the most powerful moves is to make a temporary version that is easier to see. This does not mean changing the problem until it becomes a different problem. It means preserving the relationship while reducing the load: smaller numbers, fewer distracting details, a simpler diagram, one stage instead of three, or a nearby case whose structure is easier to inspect.
A learner who can simplify deliberately gains something more useful than a trick. The learner gains a way to keep thinking when the first representation is too dense. The simplified case becomes a laboratory: we see what the quantities are doing, identify which operation or model fits, and then rebuild the original problem with the same mathematical logic.
This guide develops that process across number, fractions, decimals, geometry, data and word problems. The examples are independent teaching material. The official curriculum reference is the MOE Primary Mathematics Syllabus, updated October 2025, whose mathematics framework emphasises reasoning, representation, communication and problem-solving processes.
Series route: return to the Primary 4 Mathematics Learning Hub. For diagnostic use, connect this guide with Diagnostic Assessment, Capability Profile and Repair Routing.
Navigate: preserve the relationship · smaller numbers · strip the surface · simpler cases · rebuild the original · practice · answers.
1. Simplification must preserve the mathematical engine
Suppose a question asks: “A shop receives 18 boxes with 24 notebooks in each box, sells 157 notebooks, and shares the remaining notebooks equally among five shelves. How many notebooks go on each shelf?”
The mathematical engine is: equal groups create a total → a fixed amount is removed → the remainder is shared equally.
A simplified case might use 3 boxes of 10 notebooks, remove 5, then share the remaining 25 equally among 5 shelves. The numbers are easier, but the dependency chain is the same.
A bad simplification would remove the selling stage entirely. That would change the structure from three steps to two and might hide the very dependency causing difficulty.
The rule is simple: simplify the surface, not the relationship you are trying to understand.
2. State what will stay fixed
Before changing a difficult problem, name the invariant:
- same operation order;
- same comparison relationship;
- same fraction of a whole;
- same type of missing quantity;
- same shape structure;
- same graph-reading task;
- same condition on remainders or capacity.
This protects the learner from creating an easier question that no longer tests the original idea.
For example, when simplifying “A has four times B and together they have 315”, keep the “four times” comparison and the total unknown-unit structure. Changing it to “A has four more than B” would replace multiplication with addition.
3. Smaller numbers can expose a hidden relationship
A learner struggles with 3,456 ÷ 8. Use 56 ÷ 8 temporarily. If the learner can explain that eight equal groups contain seven each, division meaning is intact.
Next try 456 ÷ 8 or 1,256 ÷ 8. If the concept remains clear but the written algorithm fails, the weakness is likely in place-value execution rather than division meaning.
Reducing the numbers is not lowering expectations permanently. It separates the mathematical idea from the calculation load.
Once the relationship is visible, restore the original scale and solve it using the same reasoning.
This move is especially useful diagnostically because it tells us whether the concept survives when arithmetic is made easier.
4. Use a known fact as a stepping stone
To estimate or calculate 398 × 7, first consider 400 × 7 = 2,800. The nearby fact is easier to see.
But simplifying to 400 changed the number by two in every group. Correct the difference: 2 × 7 = 14. Therefore 398 × 7 = 2,786.
The simplified case gives a useful structure only because the return correction is explicit.
If we simply report 2,800, we have produced an estimate rather than an exact answer.
A learner should always ask: what did I change, and what must I restore?
5. Simplify place value without deleting it
For 47,362 rounded to the nearest hundred, a learner may be overwhelmed by all five digits.
Temporarily focus on the neighbouring hundreds: 47,300 and 47,400. The midpoint is 47,350. Now ask where 47,362 lies.
The original number remains present, but irrelevant digits are temporarily organised around the actual decision.
This is different from replacing 47,362 with 362 and forgetting the ten-thousands and thousands. The scale must remain meaningful.
Simplification can mean reducing what needs attention rather than reducing the numerical value itself.
6. Remove story decoration while keeping every mathematical condition
A long story may contain names, objects and sequence words. Rewrite it in a compressed form:
Start ? → receive 149 → finish 580
The unknown start is now visible. The relationship is ? + 149 = 580, so the start is 431.
Do not remove a condition merely because it sounds like story detail. “No items were removed” may be essential if we are using the difference between starting and final stock to identify a delivery.
Strip only what does not change the mathematics.
Then return to the original wording and confirm that the compressed representation still accounts for every relevant sentence.
7. Replace a word problem with a bar or timeline
Suppose “Nadia has four times as many beads as Omar. Together they have 210.”
Write Omar as one unit and Nadia as four equal units. The total is five units.
The story is now reduced to the relationship 5 units = 210. One unit is 42. Omar has 42 and Nadia 168.
The representation has simplified the language without simplifying the mathematics.
Return to the sentence and check both conditions: the total is 210 and 168 is four times 42.
8. Convert a graph into a smaller reading task
If a line graph is visually dense, isolate one decision: what does one vertical interval represent?
Suppose labels 20 and 40 are separated by four equal gaps. The difference is twenty. Divide by four: each gap represents five.
Once the scale is secure, return to the full graph and read the plotted point.
Do not calculate the graph question before reconstructing the scale.
Simplifying a representation often means solving its decoding problem first.
9. Solve a one-step case before a multi-step case
A learner struggles with “One third of 72 is used, then one quarter of the remainder is used.”
First ask only: one third of 72 is used; how much remains? The answer is 48.
Then ask: one quarter of 48 is used; how much remains? The answer is 36.
Now reconnect the stages. The second fraction applies to the new whole, 48.
The simplified one-step cases expose the changing reference whole without removing it from the final reconstruction.
10. Use a smaller geometry figure with the same structure
A composite L-shape may look complicated. Replace the original measurements temporarily with a 10 cm by 8 cm rectangle with a 3 cm by 2 cm corner removed.
Area can be found as 80 − 6 = 74 cm². The structural decision is “full rectangle minus missing rectangle”.
Return to the original dimensions and perform the same decomposition.
Do not replace the L-shape with an ordinary rectangle and call the practice equivalent. The missing-corner structure is the important feature.
Simplify the measurements, preserve the geometry.
11. Use an extreme or obvious case to test a proposed rule
A learner suggests, “Whenever I add the same number to the numerator and denominator, the fraction stays the same.”
Test 1/2. Adding one to both gives 2/3, which is not equal to 1/2.
A very small simple case can disprove a false general rule quickly.
This is different from using one example to prove that a rule is always true. A single counterexample can disprove an “always” claim, but one successful example cannot establish universality.
Simpler cases are powerful because they make structure easier to inspect.
12. Keep units when simplifying measurement problems
Suppose a learner struggles with 3.65 L + 850 mL.
Use 3 L + 500 mL first. Convert one quantity so both use the same unit: 3,000 mL + 500 mL = 3,500 mL.
The simplified case teaches the unit-conversion decision.
Return to the original: 3,650 mL + 850 mL = 4,500 mL = 4.5 L.
Do not remove the unit mismatch when that mismatch is the concept being tested.
13. Simplify the unknown, not only the numbers
Take “A has four times B, and A has 90 more than B.”
A simpler related question is “A has four times B. If B is 10, what is A and what is the difference?” A = 40; difference = 30.
This reveals that when A has four units and B one unit, the difference is three units.
Return to the original. Three units = 90, so one unit = 30. B = 30 and A = 120.
The simple known-unit case helps the learner discover which unit span represents the difference.
14. Reverse-engineer a complicated answer
Suppose a learner gets 2 1/2 for 4 1/3 − 1 5/6 but cannot explain why.
Use a simpler case: 3 1/3 − 1 5/6. Convert thirds to sixths: 3 2/6. Regroup one whole: 2 8/6. Subtract to get 1 3/6 = 1 1/2.
Now return to the original. The same regrouping relationship applies.
The smaller whole numbers reduce load while preserving unlike denominators and regrouping.
A simplified example should expose the exact difficult step, not replace it with an easier skill.
15. Rebuild the original one layer at a time
After a simple case is solved, restore one source of complexity at a time:
- restore the original numbers;
- restore the original representation;
- restore the original number of steps;
- restore the original context;
- restore any constraint such as remainder, unit or capacity.
This order is flexible. The key idea is to know what changed between the simpler and original versions.
When several features are restored at once, it becomes harder to identify which one caused renewed difficulty.
A staged rebuild turns simplification into a controlled learning experiment.
16. The final answer must belong to the original problem
A simplified case produces insight, not the final answer unless its numbers are the original numbers.
If we simplify 18 boxes of 24 to 3 boxes of 10, an answer of five per shelf in the simplified problem cannot be copied back to the original.
We return the method, not the simplified numerical result.
Write a clear boundary on paper: “Simple case” and “Original problem”.
This prevents temporary numbers from leaking into the final solution.
17. Know when simplification has changed too much
| Original difficulty | Useful simplification | Bad simplification |
|---|---|---|
| Changing fraction whole | Smaller divisible numbers, same two-stage fractions | Remove the second fraction stage |
| Composite area | Smaller dimensions, same missing-corner structure | Use an ordinary rectangle |
| Multiplicative comparison | Use a known one-unit amount first | Change “times” to “more” |
| Graph scale | Isolate two labels and the gaps between them | Assume each gap equals one |
| Remainder interpretation | Use a smaller quotient with a remainder | Choose an exactly divisible total |
The simplified task should preserve the feature we want to understand.
18. Simplification can reveal insufficient information
A question says, “After some counters are removed, 40 remain. How many were there at first?”
Strip away the story. We have ? − ? = 40. Two unknown quantities remain.
A smaller version such as ? − ? = 4 does not become uniquely solvable. The structural problem remains.
The simplification makes the missing information obvious.
Not every difficult-looking question needs calculation. Sometimes the correct result is that more information is required.
19. A learner can create the simple case
Do not always supply the easier numbers yourself.
Ask: “Can you make a smaller version that keeps the same relationship?”
If the learner changes the wrong feature, that is useful diagnostic evidence. For example, replacing “three times” with “three more” shows that the multiplicative relationship is not yet secure.
When the learner creates a structurally faithful small case, they are demonstrating ownership of the relationship.
That skill becomes increasingly valuable as problems become less familiar.
20. Simplification is a strategy, not an escape from exact work
A learner might repeatedly solve easy versions and avoid returning to the original. That is not the purpose.
The cycle is:
simplify → see the structure → explain the structure → rebuild → solve → verify.
The original problem remains the destination.
If the original still fails, identify which restored feature reintroduced the difficulty and work on that feature directly.
Good simplification makes the next exact attempt more informed.
21. Practice laboratory: simplify without changing the engine
- Make a smaller equivalent case for 3,456 ÷ 8 that still tests equal sharing.
- Simplify 47,362 rounded to the nearest hundred by identifying only the two neighbouring hundreds and midpoint.
- Create a simpler case for “A has four times B and together they have 315”.
- Create a smaller changing-whole version of “Use 1/3 of 72, then 1/4 of the remainder”.
- Simplify an L-shape area problem while preserving the missing-corner structure.
- Use a nearby round number to calculate 398 × 7 exactly.
- Strip “After receiving 149 stickers, Hana has 580” into a symbolic timeline and find the start.
- Reduce a graph-scale problem with labels 20 and 40 across four equal gaps to its essential calculation.
- Create a simpler problem that tests a division remainder used for capacity.
- Explain why replacing 4 times with 4 more is not a valid simplification.
- Use smaller numbers to expose why adding one to numerator and denominator does not preserve a fraction.
- Simplify 3.65 L + 850 mL while preserving the unit-conversion issue.
- Create a known-unit case to understand “A has four times B and 90 more”.
- Create a simpler mixed-number subtraction that still requires regrouping with unlike denominators.
- List the steps for rebuilding an original problem after solving a simple case.
- Explain why the numerical answer from a simple case cannot normally be copied into the original.
- For ? − ? = 40, explain why making the numbers smaller does not create enough information.
- Make a simple case for a rectangle whose area is known and one side must be recovered.
- Turn a long equal-group story into a one-line dependency chain without deleting a needed condition.
- Write one example where simplification reveals the concept is secure but the written calculation is weak.
22. Explained responses
1. One valid case is 56 ÷ 8 = 7. It preserves exact equal sharing among eight groups. The purpose is to test division meaning before returning to multi-digit place value.
2. 47,362 lies between 47,300 and 47,400. The midpoint is 47,350. Because 47,362 is above the midpoint, the original rounds to 47,400.
3. One simple case is “A has four times B and together they have 50.” Five units total 50, so B=10 and A=40. Return to 315 by using the same five-unit structure.
4. Use 24: one third is8, leaving16; one quarter of16 is4, leaving12. The two-stage changing reference whole remains intact.
5. Use a 10 by8 rectangle with a 3 by2 corner removed. Full area80 minus6 gives74. The key missing-corner structure remains.
6. 400×7=2,800. Two extra are counted in seven groups, so subtract14. Exact answer: 2,786.
7. Start ? → +149 → 580. Undo the receipt: 580−149=431.
8. Difference40−20=20; four equal gaps; one gap=5. Then return to the full graph.
9. One valid case: 17 people, vans holding4. Division gives4 remainder1, so five vans are required. The remainder interpretation remains present.
10. “Four times” is multiplicative; “four more” is additive. Changing the relationship changes the problem’s engine.
11. Start with 1/2. Adding one to numerator and denominator gives 2/3. Since 1/2≠2/3, the proposed universal rule fails.
12. Use 3 L + 500 mL. Convert 3 L to 3,000 mL before adding. Then return to the original with the same conversion decision.
13. If B=10, A=40 and the difference is30. This shows the difference spans three units. Therefore in the original, three units=90, so B=30 and A=120.
14. One valid case is 3 1/3 − 1 5/6. Convert to sixths and regroup; it preserves unlike denominators and borrowing one whole.
15. Restore the original numbers, representation, stages, context and constraints one at a time, checking which restoration changes the difficulty.
16. The simple case has different inputs. What transfers is the relationship and method, not normally the numerical output.
17. Two unknowns remain. Examples such as 50−10=40 and 70−30=40 show multiple solutions. Smaller numbers do not supply a missing condition.
18. Use area24 and width4. Length=6. The reverse area relationship is preserved and can then be returned to the larger original numbers.
19. Example: total received → subtract used → divide remainder among equal groups. Keep conditions such as “all remaining items are shared” when they affect the answer.
20. If 56÷8 is explained correctly but 3,456÷8 fails during long division, the concept may be secure while written place-value execution needs repair.
23. Teaching routine: let the learner own the simplification
Begin with a difficult but already-taught problem. Ask the learner to identify the exact part that feels unclear. Then ask what could be made smaller or simpler without changing that relationship.
Write the simple case in a separate box. Solve it and explain what each number represents. Before returning to the original, ask the learner to state what must stay the same.
Rebuild the problem. If the learner succeeds, finish with a changed surface to confirm the strategy travels. If the learner fails at the same point, route directly to the underlying concept or execution skill.
Do not use simplification as a way to complete every difficult question for the student. The learner should increasingly choose the simplifying move, explain its validity and perform the return.
A parent prompt can be as small as: “What is a simpler version of this same problem?” The phrase same problem should lead naturally to the question: which relationship are we preserving?
24. Handover to special cases and generalisation
Simpler cases help us see a relationship. The next mathematical step is to ask where that relationship changes, fails or reveals a boundary.
Continue to Special Cases, Boundaries, Counterexamples and Impossible Cases.
Final checkpoint: can the learner make a problem simpler without changing its engine, use the simpler case to understand the relationship, and then rebuild and solve the original accurately?
Source and editorial note
The curriculum boundary is referenced to the MOE Primary Mathematics Syllabus, updated October 2025. The simplifying-problem protocol, examples and practice tasks are independently written eduKate learning material.
Editorial control: Wintour House V1.0 · CivDJ · eduKate Publishing.
