Why a List of “Common Mistakes” Is Not Enough
A student may show ten visible problems in one composition: weak vocabulary, an abrupt ending, awkward dialogue, repeated sentence patterns, off-topic detail and spelling errors. Treating all ten as separate instructions can overload the learner without fixing the system that produced them.
The better question is:
What is the earliest unstable layer that can explain the later symptoms?
The repair runtime is:
Symptom → Trace Back → Locate Earliest Failure → Reduce Load → Repair → Reintegrate → Retest.
1. Off-Topic Writing
Visible symptom: the composition is fluent but the topic connection is weak, late or forced.
Do not begin with: better vocabulary, stronger hooks or more description.
Test first: Can the student explain the task in plain language before planning? Can they state what must remain visible throughout the response?
If not, the failure is upstream at interpretation.
Route: Visual Prompts → Inspect → Interpret → Generate → Select → Build
2. “I Don’t Know What to Write”
Visible symptom: blank page, dependence on memorised plots, repeated story types.
Test first: Given one topic, can the student generate three different candidate routes from the stimulus, memory, observation, motives or constraints?
If not, the student needs a stronger idea-supply system—not a finished plot donated by an adult.
Route: Idea Generation → Inputs → Connections → Alternatives → Routes
3. Too Many Ideas
Visible symptom: overplanning, changing direction halfway through, multiple subplots, unfinished endings.
Test first: Can the student reject a route because it is less relevant, less causal, harder to express or too large to finish?
If not, the problem is not creativity. It is convergence.
Route: Brainstorming → Open the Search → Fence the Search → Choose
4. Random Plot or Rushed Ending
Visible symptom: events happen beside one another rather than because of one another; the ending uses coincidence or arrives suddenly.
Test first: Can the student reduce the story to five connected states?
Situation → Pressure → Decision → Consequence → Resolution.
If one arrow cannot be explained, repair the causal spine before writing more prose.
Route: Narrative Structure → Situation → Pressure → Decision → Consequence → Resolution
5. Flat or Inconsistent Characters
Visible symptom: characters act because the plot needs them to, emotions appear suddenly, dialogue does not match the relationship.
Test first: Before the major action, can the student state what the character wants, knows, believes and fears?
If the action cannot be derived from that state plus the pressure, the character is being moved by the writer rather than by the story.
Route: Character State → Want → Know → Believe → Choose → Reveal
6. Forced Vocabulary
Visible symptom: difficult words are technically present but the sentence sounds unnatural or imprecise.
Test first: Can the student express the intended meaning clearly in simpler language?
If the meaning itself is unclear, vocabulary is not the first repair. If meaning is stable but retrieval or word choice is weak, then repair the language layer.
Route: Vocabulary for Composition → build a live language inventory

7. Purple Prose or Too Much Description
Visible symptom: many adjectives, similes and sensory details but the story becomes slower or less clear.
Test first: Delete the detail. What information does the reader actually lose?
If nothing changes in orientation, emotion, pressure, character or later causality, the detail may be decorative.
Routes: Description → Select → Focus → Encode and Imagery → Observe → Select → Compress → Evoke
8. Correct in Drills, Weak in Full Writing
Visible symptom: grammar, imagery or sentence control works during exercises but disappears when the student writes a full composition.
Test first: Remove one source of load. Does the skill return?
If yes, the skill may be installed but not sufficiently integrated or automated.
Route: Advanced Composition → Combine → Load-Test → Refine → Automate
9. Good With Tutor, Weak Alone
Visible symptom: the student writes well when prompted but cannot identify or repair the same problem independently.
Test first: Can the learner recognise the failure, select the repair and execute it without an adult naming the problem?
If not, the support has not yet been handed over.
Route: Reader Simulator → Write → Reconstruct → Detect → Repair
10. Good Practice, Weak Exam Output
Visible symptom: overplanning, freezing, unfinished stories, excessive late rewriting or sudden language collapse under time pressure.
Test first: Can the student independently move through interpretation, route selection, planning, drafting, monitoring and checking without live intervention?
Route: PSLE Composition Paper 1 Runtime → Interpret → Choose → Plan → Write → Monitor → Check
The Symptom-to-Repair Table
| Visible symptom | Earliest test | Likely repair layer |
|---|---|---|
| Off-topic | Can the task be stated accurately? | Interpretation |
| No ideas | Can three routes be generated? | Idea supply |
| Too many ideas | Can weak routes be rejected? | Convergence |
| Random middle | Do events form a causal chain? | Structure |
| Flat character | Is state known before action? | Character |
| Forced vocabulary | Is meaning clear before word choice? | Language |
| Overwritten description | Does each detail change reconstruction? | Imagery |
| Errors only under load | Does accuracy return when load falls? | Integration |
| Good only with prompts | Can the learner self-route? | Independence |
| Weak only in exam | Does the runtime survive time pressure? | Execution |
One Repair at a Time
Do not give ten instructions because ten symptoms are visible. Select the earliest high-leverage failure, reduce the load enough to repair it, then return it to whole composition writing.
Diagnose → Reduce → Repair → Reintegrate → Retest → Handover.
That is how “common mistakes” become useful: not as a checklist of faults, but as signals that route us toward the actual broken part.
