Here is a habit worth forming before you write down another exponent answer. You apply a rule — product, quotient, power-of-a-power — and get a simplified form. Before you commit, stop. Pick three small numbers: a = 2, m = 3, n = 2. Evaluate the original expression and the simplified expression. Confirm the two numbers are equal. If they are, you almost certainly got the rule right; if not, you caught an error in thirty seconds that would otherwise have cost you marks.
This is a close cousin of the "plug in x = 1 and check" habit, but tuned for the exponent laws — where the most common errors are adding when you should multiply, multiplying when you should add, or flipping a sign on a subtraction.
Why small numbers work
Three properties of the triple (a, m, n) = (2, 3, 2) make it ideal.
First, the relevant powers are all distinguishable integers — 2^3 = 8, 2^2 = 4, 2^5 = 32, 2^6 = 64, 2^1 = 2, 2^0 = 1. A correct rule produces a matching number; a wrong rule produces a wildly different one. No coincidental agreement waiting to fool you.
Second, powers of 2 grow fast. A mistake of even one unit in the final exponent produces a factor-of-two difference — 32 versus 64 — big enough to jump out the moment you look.
Third, a = 2 avoids two common traps. a = 1 is useless: 1 raised to anything is 1, so every rule and non-rule agrees trivially. a = 0 is worse: everything collapses to 0, and 0^0 is undefined. a = 2 dodges both while keeping the arithmetic small.
How to run the check
Four steps, mechanical once you've done them a few times.
- Write down the original expression — the one before you applied any rule.
- Write down your simplified form — the answer you are about to commit.
- Pick a = 2, m = 3, n = 2 (or similar small integers if your expression needs different variable names).
- Evaluate both, and confirm they produce the same number.
The check takes less than thirty seconds. The time saved on a wrong answer is measured in lost marks and a rewritten working.
Worked example 1 — verifying the product rule
You claim a^m \cdot a^n = a^{m+n}. Let's verify.
Original at (2, 3, 2): 2^3 \cdot 2^2 = 8 \cdot 4 = 32.
Simplified at (2, 3, 2): 2^{3+2} = 2^5 = 32.
Match. The rule is right. (You already knew this, but the point is to show the procedure on a rule whose answer you trust before using it on one where you aren't sure.)
Worked example 2 — catching a mistake
Suppose a student writes (a^m)^n = a^{m+n}. They have mixed up the power-of-a-power rule (which multiplies exponents) with the product rule (which adds them). Run the check.
Original at (2, 3, 2): (2^3)^2 = 8^2 = 64.
"Simplified" at (2, 3, 2): 2^{3+2} = 2^5 = 32.
64 \neq 32. Error caught. The student goes back, realises the correct rule is (a^m)^n = a^{mn}, and re-checks: 2^{3 \cdot 2} = 2^6 = 64. Match. Correct answer recovered, costing only half a minute.
Worked example 3 — catching a sign flip
Suppose a student writes \dfrac{a^m}{a^n} = a^{m+n}. They have flipped the sign on the quotient rule — should be subtraction, not addition.
Original at (2, 3, 2): \dfrac{2^3}{2^2} = \dfrac{8}{4} = 2.
"Simplified" at (2, 3, 2): 2^{3+2} = 2^5 = 32.
2 \neq 32. Error caught, and the size of the mismatch — a factor of 16, enormous — shouts "sign error in the exponent." The student fixes the rule to a^{m-n} = 2^1 = 2. Match. Done.
Notice how both of the caught errors are exactly the kind of mistake that real students make on real exams — confusing addition with multiplication of exponents, flipping a sign. The check fires on both.
Choosing values — avoid coincidences
A quick taxonomy of values and what they fail to catch.
- a = 0. Every power is 0. Useless — every rule and non-rule agrees trivially.
- a = 1. Every power is 1. Same problem.
- a = -1. Sign-dependent; can give false matches when only even exponents appear.
- a = 2. Small, positive, gives distinct powers. Safe.
- m = n. Hides asymmetric rules — if m = n = 3, then m - n = 0 and the quotient rule's answer coincides with a^0 = 1. Use m = 3, n = 2 so m + n, m - n, and mn are all different.
The triple (2, 3, 2) gives m + n = 5, m - n = 1, mn = 6, n - m = -1 — four different numbers, so every common-rule outcome is distinguishable.
When the check passes but the answer could still be wrong
An honest caveat. Plugging in ONE value cannot prove equivalence — x^2 and 2x agree at x = 2 but nowhere else useful. So the check is a failure detector, not a correctness proof. If the numbers disagree, you definitely got the algebra wrong. If they agree, you almost certainly got it right — but you haven't proven it. For exponent rules, coincidental agreement is rare enough that a single pass is usually enough evidence. Keep the asymmetry in mind: disagreement is a guaranteed bug; agreement is strong evidence, not a certificate.
The "second point" reinforcement
If your first check passes but you're still uncertain, plug in a second, different triple. Try (a, m, n) = (3, 2, 4). Two coincidences are much less likely than one. If both numbers match, your confidence should be very high. In an exam, one check is usually enough; for messy multi-rule problems or a nagging doubt, the extra thirty seconds is almost always worth it.
What this habit catches
A short list of the error types the plug-in check catches reliably.
- Operation confusion. Added exponents when you should have multiplied, or vice versa.
- Sign flips. Wrote m + n where it should have been m - n, or missed the minus sign on a negative exponent.
- Missing factors. Forgot the coefficient out front — e.g. wrote (2a)^3 = a^3 instead of 8a^3. At a = 2, the correct answer is 64 and the wrong answer is 8; mismatch caught.
- Bracket-precedence errors. Treated (a^m)^n as if the exponent only applied to part of the base, or vice versa.
- Forgotten special cases. Wrote a^0 = 0 instead of 1. Check with a = 2: true a^0 is 1, wrong "a^0" is 0; mismatch.
If the rule you've applied is correct, the two numbers will match. If it isn't, they won't. The check doesn't care about the specific error type — it just fires whenever the algebra and the arithmetic disagree.
Sanity checks at the end of a problem chain
The habit scales. It isn't just for verifying a single rule application — it is for verifying a whole chain. After you simplify \dfrac{(2a^3 b^{-1})^2}{4 a^{-2} b^3} through four or five rule-applications, plug a = 2, b = 3 into both the ORIGINAL expression and your FINAL answer. If the numbers match, the entire chain is almost certainly correct. If not, you have narrowed the bug from "somewhere in this messy derivation" to "somewhere I can find by re-running the check after each intermediate step" — the same binary-search debugging technique a programmer uses on a broken pipeline.
Close
Thirty seconds of arithmetic catches hours of lost marks. The arithmetic is easy: 2^3 = 8, 2^2 = 4, 2^5 = 32, 2^6 = 64. The discipline is the hard part — remembering to run the check every time, especially when you are sure. Make it a reflex. Apply the rule, write the answer, plug in (2, 3, 2), confirm the numbers agree, then commit. Students who never lose marks on exponent problems are not the ones who never make mistakes — they are the ones who catch their mistakes before the grader does.