Prerequisite diagnosis
Find out that the thing you're stuck on isn't the thing you're stuck on; it's something from two years ago that never quite landed.
When a topic feels too heavy, these methods keep you in the work without drowning you.
You ask for the smallest useful help: one hint, a worked example with decisions labelled, a diagnosis of which earlier idea is missing. Then you do the next step yourself.
Use this family when you keep rereading and still cannot start, or when full solutions keep leaving you unable to begin the next problem.
Find out that the thing you're stuck on isn't the thing you're stuck on; it's something from two years ago that never quite landed.
Get unstuck without getting rescued.
Design a short sequence that starts with full support and ends with you doing the work alone, and advance only when you've earned the next rung, instead of staying on crutches that feel like studying.
Get more out of a worked solution than the feeling of having followed it, and know exactly what it will and won't buy you.
Receive a solution with the last steps missing, and finish it.
Walk the full prerequisite chain for a topic out loud, stopping at the first link you cannot explain, so you find the real break instead of restudying the chapter that sits on top of it.
Take the analogy you already have (from a teacher, a textbook, or A5) and find exactly where it stops being true, which wrong prediction that break would cause, and whether you should keep the scaffold or drop it.
Study a solution that contains a deliberate mistake and find it, which is a far better test of understanding than following a correct one.
Get the prerequisite structure of a topic drawn out, and locate yourself on it before you start.
Ask for the same idea at three levels of sophistication and use the level where you break as a precise measurement of where your understanding stops.
Learn an abstract idea by walking a fixed path, concrete instance, then schematic version, then the bare formalism, so the symbols arrive attached to something you can already do.
Break a long procedure into named stages you can recite from memory, so mid-task panic becomes "I'm in stage 3" instead of "I've forgotten everything."
Get a structural map of a topic before the detail arrives, then place each new piece into that map as you learn, instead of drowning in facts with nowhere to put them.
Use simplification without losing what it removed, by putting the caveats back yourself and saying what each one changes.
Start from a finished answer and reconstruct the reasoning backwards, so you see why each prior step was forced, not just how to mimic a forward template.
Take an idea in spoken form while following a silent visual (or the reverse), then switch channels, so the same structure is encoded two ways instead of as one fragile verbal string.
Stop bouncing between a diagram and a separate wall of text, and get one integrated explanation that keeps eyes and mind on the same object.
Generate a handful of candidate analogies for one idea, keep the one whose structure actually maps, then restate the target without the metaphor so the story becomes a bridge, not a substitute.
Build a personal glossary where every technical term is stated in your own words, then checked against what the field actually means, so vocabulary stops being a fog you nod through.
Take an expression full of symbols, name what each symbol is doing, and read the whole thing aloud as a sentence about the world, until the page stops being a texture and becomes a claim.
Learn the eight to twelve load-bearing terms a text depends on before you read it, so the reading becomes about the argument, not about surviving the lexicon.
Meet a hard source at a simpler level first, then return to the original and notice exactly what the simplification removed, so difficulty becomes a ladder, not a wall.
Ask for the shortest explanation that is still correct (then expand only the parts that actually blocked you) so you stop paying for essays when you needed three sentences.
Demand the same explanation in several registers, expert, peer, child, hostile skeptic, and compare what changes, so you see which load-bearing pieces survive translation and which were vibes.
Tell the AI what you already know up front so support starts on the right rung, instead of enduring a beginner lecture you didn't need, or a specialist fog you weren't ready for.
Tell the AI your current working-memory limit and get an explanation cut to exactly that size, so you stop accepting firehoses on tired evenings and thimblefuls when you could handle more.