What "extract the WHY" actually means
The move most beginners never make.
Here's the move most beginners never make. A question is not one thing — it's a stack of bits of information. And specific bits of information are what make specific routes available.
So the answer sheet didn't "magically think of it." It read a bit of information and that bit unlocked a route. Your job is to map information → available move.
Concrete TMUA-flavoured examples
- The question hands you "the discriminant is non-negative" → that bit unlocks the route treat this as a quadratic in disguise and force real roots.
- The question hands you a symmetric expression → that bit unlocks substitute, or exploit the symmetry instead of brute-forcing both terms.
- The question hands you a weird constraint that looks like noise → 9 times out of 10 that "noise" is the bit that picks the route. Beginners ignore it. The model answer was built around it.
Now — nothing here is absolute. This is the part people get wrong when they try to do this. It is NOT "when expression X shows up, I MUST do action Y." That's just flashcards wearing a lab coat. It's softer than that: given these bits of information, it's possible the process goes down this route. You're not building a lookup table. You're stacking probabilities — building a library of "when I see this pattern, these two or three routes are worth trying first."
That's pattern recognition under uncertainty. That's the actual skill. And it's invisible in every answer sheet, which is why everyone misses it.
Zombie math vs Why math — the longer version
Zombie math
- "Oh okay, they used the chain rule here. Makes sense."
- "I get how they got from line 2 to line 3."
- "Right, so they factored it and got the answer."
Why math (sniper)
- "What specific trigger prompted the chain rule instead of the product rule? Ah — the nested function."
- "Why did they substitute u = x² here? What other paths were dead ends?"
- "Did they check for extraneous solutions? Did they consider the domain?"
The scaffolding phase
| Phase | What retail students do | What 9.0 TMUA students do |
|---|---|---|
| 1. Deconstruction | Reads the whole question, panics, looks for a formula that "looks" right. | Breaks it into Givens, Constraints, Target Goal. |
| 2. The Bridge | Tries to jump from Givens to Target with brute-force algebra. | Asks: "what intermediate state connects them?" Builds a logical bridge. |
| 3. Execution | Bashes through, makes a sign error, picks the wrong option. | Executes step-by-step, checking each micro-step for validity. |
Sloppy vs sharp thinking
| Sloppy (the trap) | Sharp (the 9.0) |
|---|---|
| "I divided both sides by x, so on and so forth, got x = 3." | "I divided by x. Wait — what if x = 0? Check that case separately first." |
| "I squared both sides to kill the root, something like that." | "I squared both sides. This can introduce extraneous roots — plug answers back into the original to verify." |
| "The graph goes up then down, so there's a max somewhere." | "The derivative changes sign positive → negative. By IVT, since continuous, a local max exists in that interval." |