A mistake that gets labeled “silly” is a mistake that has not been diagnosed. Most errors that feel careless on review turn out to belong to one of three distinct categories — and each category has a different cause and a different fix. Treating them all as carelessness produces more practice, not better performance.
The Three Error Categories
| Category | What It Looks Like | Actual Cause | Fix |
|---|---|---|---|
| Higher-order | Chose the wrong approach, misread what the question was asking, applied a concept in the wrong domain | Conceptual gap — the schema does not connect correctly at the level of understanding | Re-encode: revisit the concept with active questioning (why/how/relationship questions), not re-reading |
| Lower-order | Arithmetic slip, sign error, wrote the wrong word, missed a unit, mis-copied | Execution under load — the schema is correct but attentional resources ran out during application | Slow the process step down; add a review pass specifically for mechanical output |
| Procedural | Knew the concept, used the right approach, but applied the method in the wrong sequence or skipped a step | Process gap — the procedure was not practiced to the point where the sequence is automatic | Deliberate procedural rehearsal — practice the sequence as a sequence, not just the individual components |
Diagnosis matters before any fix. Running extra practice at the wrong level is not neutral — it reinforces the wrong schema or the wrong process and can make the mistake harder to correct later.
Why “Silly Mistakes” Is a Misleading Category
The label is appealing because it feels like the problem is attentiveness, which implies a simple fix: be more careful. But attentiveness is not a skill that can be improved directly. The underlying error is always in the schema, the execution process, or the procedural sequence — and fixing the wrong one costs time without reducing the error rate.
The reframe: a higher-order error that gets treated as carelessness will recur because the conceptual gap remains. A lower-order error that gets treated as a conceptual gap wastes encoding effort on something that is already understood. The fix has to match the diagnosis.
Double Generation Practice Test
When a mistake is ambiguous — it is not clear whether it is conceptual or procedural — use the double generation method to locate where the breakdown actually occurred:
- First generation. Attempt the problem from scratch, without notes or any external aid. Write out the full working.
- Second generation. Wait at least 10 minutes. Attempt the same problem again from scratch. Do not look at the first attempt.
- Compare. Look at both attempts together. Where do they diverge? The divergence point identifies the step where the schema or procedure is unstable.
If both attempts fail in the same place, the cause is a gap — not carelessness. If the attempts fail in different places, the error is execution variance — the process is inconsistent under load.
The second generation is important. Generating once can feel fluent even when the knowledge is shaky. The second attempt removes the recency effect from the first and forces genuine reconstruction.
Applying This In Practice
After each practice session or exam review:
- Sort the errors into higher-order, lower-order, and procedural before deciding what to do next.
- For higher-order errors, flag the concept for re-encoding — not re-reading.
- For lower-order errors, identify which step in the execution sequence is producing the slip and slow that step down in the next attempt.
- For ambiguous errors, run the double generation test before categorizing.
- Track which category your errors cluster in across sessions — a persistent cluster points to a systemic fix, not session-by-session correction.
Open Questions
- Which error category accounts for most of your current exam losses?
- Do your higher-order errors cluster around specific concept types or specific domains?
- At what point in a long practice session do lower-order errors start increasing?