MTLE Mathematics (Grades 5-12) common mistakes
MTLE Mathematics (Grades 5-12) · Understand the traps and how to avoid them.
When converting between units within the metric or customary system (for example, square feet to square inches, or cubic centimeters to liters), the candidate applies the linear conversion factor once instead of raising it to the power of the dimension.
Unit conversion drills in earlier coursework emphasize single-step linear factors, so the candidate memorizes '1 foot = 12 inches' and reuses 12 for area and volume rather than 144 and 1,728. The dimensional exponent is treated as decoration rather than as part of the operation.
What to do instead
Before computing, write the target unit as a product of base units (for example, ft^2 = ft x ft) and cancel units symbolically so the exponent is visible. Practice a set of area and volume conversions where the factor must be squared or cubed, and check reasonableness: a square foot should contain far more than 12 square inches.
The candidate simplifies rational expressions or solves rational equations by multiplying both sides by a common denominator without recording the excluded values, then reports a solution that makes an original denominator zero.
The procedural habit of 'clear the fractions' is overlearned, and checking domain restrictions feels like an optional extra step. Extraneous roots are rare in linear equation practice, so the candidate has not built the reflex to test candidates against the original equation.
What to do instead
Adopt a fixed two-line ritual: list restrictions from every original denominator first, then solve, then strike any candidate on the restriction list. Practice with equations deliberately constructed to produce an extraneous root so the failure is experienced, not just described.
When asked to describe the effect of a transformation on a function, the candidate applies horizontal shifts and stretches in the wrong direction or order (for example, treating f(x - 3) as a shift left, or stretching before translating when the form requires the reverse).
Vertical transformations behave intuitively because the operation appears outside the function, and candidates generalize that intuition to the inside. The counterintuitive direction of horizontal changes is easy to state but hard to internalize without repeated graphing.
What to do instead
Rewrite every transformed function in the form a·f(b(x - h)) + k before answering, and verify with three test points computed by hand. Build a habit of graphing the parent and transformed function together and predicting the image of a single labeled point before checking.
The candidate computes a conditional probability by dividing the joint probability by the wrong marginal, or confuses P(A|B) with P(B|A), especially in word problems involving screening tests or two-way tables.
The notation is read left to right as if it were symmetric, and the 'given' condition is buried in prose rather than flagged. Two-way table practice often stops at joint frequencies, so the conditioning step is under-rehearsed.
What to do instead
Restate every problem as 'given ___' and circle the denominator population before computing. Rebuild the same problem from a two-way table of counts, where the denominator is literally a row or column total, then convert to probabilities and confirm the two methods agree.
The candidate computes the mean, median, and standard deviation of a data set but misreads the question's inferential target, reporting a statistic as a parameter or treating a sample result as a claim about the population without acknowledging sampling variability.
Computation is the part that feels like mathematics, so the candidate stops once a number is produced. Distinctions between statistic and parameter, and between describing data and drawing an inference, are conceptual and receive less practice than calculation.
What to do instead
Before computing, label each quantity in the problem as sample or population and write one sentence stating what the question actually asks. Practice interpreting outputs in context, including a sentence on how much the result could vary from sample to sample.
In geometric proof or reasoning tasks, the candidate cites a theorem by name without verifying that its hypotheses are satisfied, for example applying the Pythagorean theorem to a triangle not known to be right or using a similarity shortcut without the required angle or side correspondence.
Theorem names are memorized as labels attached to formulas rather than as conditional statements with premises. Under time pressure, the candidate pattern-matches the diagram instead of checking given information.
What to do instead
For each theorem used, write its hypothesis as a checklist and tick each item against the given information before writing the conclusion. Practice identifying which of several theorems could apply and why the others fail on the same figure.
The candidate solves a multi-step word problem correctly in the middle steps but answers a different question than the one asked, for example reporting the discounted price when the question asks for the amount saved, or reporting the total when the question asks for the per-unit amount.
Working memory is consumed by the arithmetic, and the final question sentence is read once at the start and not revisited. Intermediate quantities feel like answers because they are the last number computed.
What to do instead
Underline the actual question sentence and write a one-line answer skeleton with units before starting ('answer = ___ dollars saved'). After computing, substitute the result into that skeleton and check it matches the requested quantity and scale.
The candidate treats a counterexample as sufficient to prove a general statement, or treats several confirming examples as proof of a universal claim, and writes justifications that assert rather than argue.
School mathematics rewards getting the right answer, so the candidate has limited experience distinguishing verification from proof. The logical structure of universal and existential claims is rarely made explicit in prior coursework.
What to do instead
Classify each claim as universal or existential before responding, and match the response type: a single counterexample refutes a universal claim, but only a general argument establishes one. Practice writing two-column or paragraph arguments where every step names its justification.
When analyzing student work or planning instruction, the candidate identifies the student's error correctly but proposes a fix that only restates the correct procedure, without diagnosing the underlying misconception or selecting a task that would surface and confront it.
The candidate's own fluency makes the error seem like a slip, so the response addresses the symptom. Coursework often emphasizes error identification as an endpoint rather than as the beginning of instructional decision-making.
What to do instead
Use an error-analysis frame: name the misconception, cite the evidence in the student's work, then choose an instructional move (a contrasting case, a number line or area model, a targeted question) that makes the misconception visible to the student. Practice writing responses that quote the student's reasoning and predict the next likely error.
The candidate describes a lesson activity in general terms ('students will explore fractions in groups') without specifying the mathematical goal, the representations used, the questions the teacher will ask, and how understanding will be assessed.
Lesson-planning templates emphasize activity sequences and classroom management, so the mathematical trajectory and formative evidence are underspecified. Vague language feels safe because it cannot be marked wrong.
What to do instead
For every activity described, write the specific learning objective, the representation or model students will use, two anticipated student responses (one correct, one partial), and the question or task that will reveal understanding. Replace adjectives with observable actions and evidence.