“A flashcard that can be answered by pattern matching the shape of the question isn't testing your memory, it's testing your memory of the card.”
I made a deck once with a card that said "What is photosynthesis?" on the front and a full paragraph on the back. I reviewed it forty times over three weeks. I still couldn't explain photosynthesis.
The problem wasn't that I didn't review enough. It was that the card was bad, and no amount of reviewing a bad card fixes what's wrong with it.
The core rule: one fact per card
The photosynthesis card was trying to teach an entire process in one go. Which means every time I saw it, I could recall the first sentence, feel like I'd got it, and never notice I'd forgotten everything after "carbon dioxide and water."
Split it up. What are the inputs. What are the outputs. Where does it happen in the cell. What's the role of chlorophyll. Four small cards beat one big one every time, because each one gives you a clean, specific answer to check yourself against instead of a paragraph you can partially remember and call it a win.
If you're struggling to write a short answer for a card, that's not a writing problem. It's a sign the card is actually two or three facts wearing one costume.
Write the question so there's only one answer
"What did the Treaty of Versailles do?" has about six correct answers depending on which part you're thinking of that day. You'll answer it differently each time and never notice you're not actually being consistent, which means you're not actually being tested.
"What year was the Treaty of Versailles signed?" has one answer. So does "Name one of the treaty's terms relating to German military size." Specific questions produce specific, checkable answers. Vague questions produce vague answers that feel right because there's no wrong version to compare against.
Cut the recognisable words
This is the one that catches almost everyone. If your card says "What is mitosis?" you don't need to recall the concept, you just need to recognise the word "mitosis" and let it trigger whatever's loosely associated with it in your head. That's not the same skill as being asked "how does a cell divide to produce two identical daughter cells" with the technical term missing, which actually requires you to know what mitosis does rather than just what it's called.
Where you can, write the question around the concept instead of naming it. Save the vocabulary-recall cards for actually learning vocabulary.
Make the back short enough to actually check against
If the back of a card is four sentences, you'll never honestly compare your answer to it. You'll skim it, feel like your answer was "basically" right, and flip to the next card. A short, specific answer is one you can actually hold yourself to.
If a concept genuinely needs a long answer, that's usually a sign it belongs in active recall practice rather than on a card. Explaining something out loud handles nuance and connected ideas far better than a flashcard ever will. Cards are for facts you need on quick, reliable recall. Save the deep explaining for a format built to check depth, not just retrieval.
Test the direction you'll actually be asked
A lot of decks only test one direction. Term on the front, definition on the back, every time. Which means you get very good at "given the term, produce the definition" and no better at "given the definition or the situation, produce the term," which is often closer to how exam questions are actually phrased.
If a fact matters enough to be a card, it's usually worth making it in both directions. It roughly doubles your deck size for a fact that genuinely matters, and it's cheap insurance against an exam question that comes at the same knowledge from the angle you didn't practise.
Where the actual bottleneck is
None of this is complicated once you know it. The bottleneck is time. Making one good card, split correctly, worded specifically, with a checkable answer, takes a few minutes. A real set of lecture notes needs eighty of them, and that's before you've reviewed a single one.
That's the gap our flashcard generator is built to close: it reads your actual slides and drafts the split, specific version of each card automatically, so what would've been two hours of writing becomes ten minutes of editing the ones it got slightly wrong. You still make the judgment calls, you just don't spend your evening typing.
If you're starting from lecture slides rather than a blank deck, we've also written about the fastest way to turn slides into a first draft of cards worth then cleaning up with the rules above.
The short version
A flashcard is bad if it tests recognition instead of recall, if it's answerable from the shape of the question rather than the content, or if the answer is too long to honestly check against. Split big facts into small ones, write specific questions, and keep the answers short enough that you can't fool yourself.