Good and Bad Flashcards: Before-and-After Examples
Six flashcards that look fine but waste your reviews, why each one falls short, and how to rewrite it into cards you can actually learn from.
How to Create a Useful Deck covers the rules: one idea per card, a back you can grade yourself against, decks split by what you want to review together. Rules are easy to agree with and easy to break without noticing, so this post is the other half: real-looking cards that go wrong, what's wrong with them, and what to write instead.
A word without its context
A card for a Spanish learner:
- Front: "embarazada" Back: "pregnant"
Nothing here is false. The trouble is that it trains a lookup, not the word. You may recognise it on the card and still freeze when you hear it in a sentence, and nothing on the card warns you that it looks like "embarrassed" and isn't. Put the word where it lives:
- Front: "Mi hermana está embarazada de seis meses." Back: "pregnant (not embarrassed, which is avergonzada)"
Now add a second card for the other direction, because recognising a word and producing it are two different skills:
- Front: "pregnant (Spanish)" Back: "embarazada"
If you want to train your ear too, set the deck's language (and the back's, if it differs) and let read-aloud speak the front, or embed an audio clip on it. Then you're practising hearing the word, not only reading it.
A question without a clear target
- Front: "What happened in 1789?" Back: a paragraph about the French Revolution.
It's easy to tell yourself you "basically" knew it. A question with one clear target, where you can tell right from wrong at a glance, is much harder to grade on a feeling, so ask several of those instead:
- Front: "On what date was the Bastille stormed?" Back: "14 July 1789"
- Front: "What assembly did Louis XVI convene in May 1789, for the first time since 1614?" Back: "The Estates-General"
- Front: "What document did the National Assembly adopt on 26 August 1789?" Back: "The Declaration of the Rights of Man and of the Citizen"
Three small cards usually go faster than one big one, and each gets scheduled on its own. The date you keep missing comes back more often, and the one you already know stops taking up your time.
A list on one card
- Front: "Name the phases of mitosis." Back: "Prophase, metaphase, anaphase, telophase"
Lists are where partial credit lives. Remembering three of four isn't clearly a pass or a fail, so you'll tend to grade it differently each time, and the one phase you always forget never gets the extra reviews it needs. Give each item its own card, with a question only that item answers:
- Front: "In which phase of mitosis do the chromosomes line up at the cell's equator?" Back: "Metaphase"
- Front: "In which phase of mitosis do the sister chromatids separate?" Back: "Anaphase"
If the order itself matters, that's one more card: "Which phase comes right after metaphase?" Back: "Anaphase".
Sometimes the whole sequence is the point, like the steps of a procedure you need to recite in order. A list card can be the right choice there. Just make it on purpose, knowing the items won't be scheduled separately.
A concept that asks you to explain
- Front: "Explain closures in JavaScript." Back: a textbook definition.
You can recite a definition and still not predict what code does. Ask the question the way the code asks it:
-
Front: "What does this print?"
function counter() { let n = 0; return () => ++n; } const next = counter(); next(); console.log(next());Back: "2: the returned function keeps its own
nbetween calls"
There's one answer to check, and you can check it in a moment. It's also hard to get right without understanding the idea. An "explain" card still has its place if you're practising for an oral exam or an interview, where explaining is the skill being tested.
A formula you only know by sight
- Front: "Quadratic formula" Back: the formula
You'll probably recognise it every time, which isn't the same as knowing when to use it or what its parts mean. Ask about the parts:
- Front: "For ax² + bx + c = 0 (a ≠ 0), what does it mean if b² − 4ac is negative?" Back: "No real roots"
- Front: "Which formula solves ax² + bx + c = 0 (a ≠ 0) for x?" Back: the formula
The second card still drills the formula itself. It just starts from the problem, not the name. On your own cards you can type formulas properly with the visual formula editor instead of plain characters like these.
An AI draft you kept as-is
AI generation is good at getting a deck started, and it tends to write long backs. A typical suggestion from a lecture on the water cycle:
- Front: "What is evaporation?" Back: "Evaporation is the process by which water changes from a liquid to a gas or vapour, primarily driven by heat from the sun, and it is a key part of the water cycle."
Most of that back is padding, and padding is what you skim during review. Trim it to the part you'd actually say out loud:
- Front: "What is it called when liquid water turns to vapour below its boiling point?" Back: "Evaporation"
A short back also matters in two quiz modes. Written asks you to type the back (case, punctuation and extra spaces don't count), and Sentence builder has you tap the back's words, plus a few extras, into the right order. The first version would be very hard to type from memory and would turn into a pile of tiles. The trimmed one works in both.
Five quick checks for any card
Before you save a card, ask:
- Does it have one clear target? Different wordings of the same answer are fine. If you'd accept genuinely different answers, split it or narrow the question.
- Could you grade it at a glance? If you'd need to reread the back to decide, the back is probably too long.
- Is it testing the thing you need? Recognising a word isn't using it, and reciting a definition isn't applying it.
- Would a picture or a sound help? Then embed one, on the front.
- Is it secretly a list? Then it's probably several cards, unless the sequence itself is what you're learning.
A card that passes these usually takes just a few seconds to review, and those quick, honest reviews are the ones that add up.