Leech Cards: How to Fix the Words That Won't Stick

3 Failure Types, 3 Different Fixes

Study Systems & Sequencing

{{first_name | みんな}}さん、こんにちは ☕

You open your SRS app. The same 20 words are back. める or まる? (We covered why those pairs trip everyone up — learning them with their particle is the fix.) Was it くう or そら for そら? You hit "Again" for the eighth time on the same card and start wondering if your brain is just... broken.

It's not.

Every leech card — a card you fail so often it starts consuming a disproportionate share of your review time; most SRS apps (like Anki) tag and suspend these automatically after a threshold number of failures — is trying to tell you something. There are exactly three things it might be saying. Today we crack all three.

In our SRS Triage edition, we gave you the system-level triage: when to add cards, when to stop, when to change decks. Today we go one level deeper — card-level triage. The stubborn ones that survived your first purge? Those are the ones we're after.

Leech cards — how to fix the words that won't stick

Your cards are broken, not your brain

Here's the thing most learners get wrong about leeches: they assume a leech means the word is hard.

Sometimes a word genuinely IS harder — abstract concepts, sound-alike pairs, kanji with overlapping readings. That's real. But the card failing eight times in a row? That's almost always a card problem, not a brain problem. The word とどける is not inherently harder than べる. Your card for 届ける just failed to create the conditions for encoding.

And the default SRS experience gives you zero help. Anki's leech system? It tags the card, suspends it, and then leaves you staring at it with no guidance. WaniKani detects leeches but offers no framework for fixing the underlying cause. The tools identify the symptom without treating the disease.

That's where most learners get stuck. They either brute-force through (doesn't work — shallow processing creates unstable memory traces that crumble under pressure), or they mass-delete everything (loses words they actually need).

Neither approach asks the only question that matters: why did this card become a leech?

🎴

New: The Kotoba Brew Vocabulary Deck — Free

We built the Anki deck we wish existed when we started. 3,000+ notes with pitch accent on every card, native audio, context images, sentence audio, and conjugation tables — designed to work with Minna No Nihongo, Genki or on its own. Every note produces two cards: one for recognition (see the Japanese word → know the meaning) and one for recall (hear the word and sentence audio → recall the word and its meaning). This two-way system builds both reading comprehension and listening recall. Beautiful cards. Dark mode. Completely free.

The Leech Triage: three failure types, three different fixes

Every leech you've ever had falls into one of three categories. Diagnose the type, apply the matching fix. That's it.

☝️ Chotto

A quick note on thresholds: Anki's default leech threshold is 8 lapses. We recommend trying 6 — catching leeches earlier gives you more diagnostic signal before the card becomes deeply frustrating. You can adjust this in Anki under Deck Options > Lapses > Leech Threshold. Different learners land on different numbers, but 6 is a solid starting point.

Type 1: The Ghost Card (encoding failure)

The word never formed a strong memory trace. You added it from a word list or pre-made deck without context. You "learned" it by seeing the answer, not by understanding it.

The signal: You see the card and feel nothing. No partial recognition, no tip-of-the-tongue. Just blank.

Example: You added 届ける from a frequency list. You see "to deliver" and think... nothing. No image, no sentence, no situation where you'd ever say this.

The fix: Context injection. Add a sentence you care about: 荷物にもつとどけてくれますか? "Can you deliver the package for me?" Add an image or personal connection — we covered how the right image transforms a card in a previous edition. If you've never encountered this word outside your SRS — that's the problem. Wozniak's first rule of knowledge formulation: "Do not learn if you do not understand."

One more trick that works surprisingly well: learn the kanji that compose the word. If you understand the components — what each kanji means, how it contributes to the compound — you build structural memory that supports word-level recall. 届ける becomes less of a stranger when you recognize 届 as "reach/deliver" from its components.

Type 2: The Evil Twin (interference failure)

You know this word exists. You can almost remember it. But your brain keeps swapping it with a similar word — same reading, similar kanji, overlapping meaning. This is proactive interference — old memories blocking new ones, or similar items competing for the same mental slot.

The signal: You see the card, you think you know it, and you're confidently wrong. You give the answer for the other word.

Example: く vs く — both きく, but one is passive hearing and the other is active listening. Or the classic おもう vs かんがえる — both "to think," but your card asks for one and you always produce the other.

The fix: Distinction card. Do NOT study the two words separately and hope your brain sorts it out. Create a new card that puts them side by side and asks: "What is the difference between X and Y?" This is discrimination training — and once the distinction is explicit, both original cards often become easy.

Here's a mindset shift worth making: not all cards in your deck need to be vocabulary, kanji, or grammar cards. You can create "question yourself" cards — cards that test your understanding of a distinction, not just recall of a single item. Your deck is a thinking tool, not just a memorization tool.

And just like with Ghost Cards, studying the kanji that compose each word helps here too. When you understand why く uses みみ "ear" + もん "gate" while 聴く uses 耳 + 十 + 四 + こころ "heart," the distinction stops being arbitrary and starts being structural.

Leech card failure types — Ghost Card, Evil Twin, Wrong Shape

Type 3: The Wrong Shape (format failure)

The card is testing the wrong thing, or testing too many things at once. You know the word. You use it in conversation. But something about the card trips you up every time.

The signal: You know you know this. The card just doesn't let you prove it.

Example: A card asks "What does はやい mean?" and the answer is "early/fast." You write "fast" — wrong, it wanted "early." But the real issue: the card is testing two things at once. If the problem is actually a near-twin (早い vs はやい), treat it as an Evil Twin instead.

The fix: Redesign the card. Split cards that test multiple things. Change direction (recognition instead of production, or vice versa). Add acceptable answer variants. If the card tests something you don't actually need (like handwriting kanji when you only type), delete it. The Minimum Information Principle: each card should test exactly one thing.

Enjoying this? If someone forwarded you this issue, subscribe here so you don't miss next week's.

Subscribe

The Kotoba Brew Protocol: five steps to fixing leeches for good

This is the part we wish someone had told us two years ago. Not a quick hack — a real system for cards that won't behave.

After diagnosing the type, one more question: "Do I actually need this word in the next 3 months?" If no — suspend it. Not delete. Suspend. You might need it later.

If yes — here's our five-step protocol.

Step 1: Suspend and forget. Always suspend leech cards for a minimum of 2 weeks. We recommend 3-4 weeks. The goal is counterintuitive: you want to forget the word completely. That broken neural path you've been reinforcing with every failed review? You need it to decay so you can build a fresh one. Spacing research supports this — longer gaps before reintroduction improve long-term retention.

Step 2: Reset AND modify the card. When you come back to it, don't just hit "reset." That changes the interval but keeps the same broken card. Fix the actual problem — add context, add a photo, rephrase the prompt, add a hint. If it's a vocabulary card, consider creating a dedicated context card: a card that shows the word used in a real sentence or situation. The diagnosis from the triage tells you what to fix.

Step 3: Move to a dedicated leech deck. Don't toss the modified card back into your main deck. Create a separate leech deck with tighter review intervals (we use a 1-day graduating interval and 3-day maximum interval to start). This quarantine strategy keeps your main deck clean and gives leeches the focused attention they need.

Step 4: Unfreeze and restart. After 3-4 weeks paused, unfreeze the card — always inside the leech deck, never back in your main rotation yet. Start fresh. And here's the key mindset shift: for your leech deck, do NOT aim for perfect retention. 70-80% retention rate is fine. The goal isn't perfect SRS recall — it's building enough familiarity that natural immersion and context can do the rest.

Step 5: Don't fail cards in the leech deck — pass them. Even if you don't remember, pass them. This shifts you from "memorizing mode" to "reviewing only" mode. You're not trying to hammer the word into your brain anymore. You're giving it gentle, repeated exposure while trusting that reading, listening, and real-world context will fill in the gaps. The leech deck is the bridge, not the destination.

⚠️ Abunai!

Do NOT mass-delete without diagnosing first. "Delete all leeches" is the SRS equivalent of throwing away every shirt that doesn't fit instead of checking whether you grabbed the wrong size.

Level up レベルアップ

⬆️ For advanced readers

At higher levels, the Evil Twin type becomes dominant. Advanced vocabulary is full of near-synonyms with subtle usage differences:

おうじる vs 対応たいおうする vs こたえる — three ways to "respond," different registers

ようやく vs やっと vs ついに — three ways to say "finally," different emotional coloring

The advanced fix: Instead of a distinction card (which works for binary pairs), create a spectrum card — place 3-4 near-synonyms on a scale from formal to casual, or positive to negative. This handles the synonym clusters that pile up at higher levels.

The real endgame for synonyms: Stop using English definitions. When your English gloss for three different words is the same word — "to respond" — the problem isn't your memory. It's that English can't capture the difference. The fix is shifting to Japanese-Japanese (monolingual) definitions.

Our recommendation: 旺文社国語辞典おうぶんしゃこくごじてん, commonly known as 旺国おうこく. Now in its 12th edition (2023). Its selling point: the most precise and easy-to-understand definitions of any monolingual dictionary — they're known for clear, accessible language. It explains differences between kanji usages (like う vs う) and is excellent for grammar definitions too.

We're planning a future edition on the monolingual transition — when to make the switch, how to survive the first painful weeks, and which dictionaries work best at each stage. Stay tuned.

When to retire a word: If you read or listen to Japanese daily and a word appears naturally at least once a week, your SRS card for it is redundant. Suspend it. Let immersion do the work.

Kanji of the Week

ボウ ・ わす・れる

To forget

Key words

わすれる (to forget) | わすもの (lost property) | 忘年会ぼうねんかい (end-of-year party)

Components: ぼう "to perish/lose" + こころ "heart/mind"

Memory hint: When something perishes from your mind — that's forgetting. 亡 on top of 心. Gone from the heart.

Tie-in: The irony of studying 忘 in an issue about forgetting isn't lost on us. But look at the kanji — something dies from your mind. That's exactly what happens to a Ghost Card. The word perishes because it never had a strong enough trace to survive. Today's framework is about preventing that.

New to kanji readings? Onyomi, kunyomi, and all those symbols above — we explain it all.

How Readings Work →

Renshuu Time 練習 📝

The Leech Triage: Diagnose Your Top 5

Open your SRS app (Anki, WaniKani, Bunpro, Kitsun — whatever you use). Find your leech cards. In Anki: search tag:leech in the browser. In WaniKani: sort by most failed or use the Leech Training userscript. In other apps: find cards you've failed 5+ times.

Pick your top 5 worst offenders. For each one, ask: why did my brain reject this?

(Answers aren't pass/fail here — but we'll share example diagnoses next week so you can check your thinking!)

Starter: Pick 3 cards. Just label each one: Ghost, Evil Twin, or Wrong Shape. No fixes yet — diagnosis only.

Standard: Pick 5 cards. Diagnose each one, then apply the matching fix from the triage. Time yourself — most card edits take under 3 minutes.

Challenge: After diagnosing and fixing 5 cards, create a dedicated leech deck. Move your diagnosed cards into it and set tighter intervals (1-day graduating, 3-day max). Review daily for one week, then report back.

You'll know you did it when: You can point at each of your worst leeches and say exactly which of the three types it is — and you've done something different to each one.

✨ Yatta!

Even if you only diagnosed 3 cards today, you just did something 90% of SRS users never do: you stopped treating the symptom and started treating the cause. Those 3 cards are going to behave differently from now on.

Leech card diagnosis practice

Last week's answers (Kanji Radicals):

Last week we asked you to X-Ray 5 kanji — find the parts, spot the meaning hint and the sound hint. There's no single right answer, but here's what to look for: the semantic component (meaning hint) is often the 部首ぶしゅ, and the phonetic component (sound hint) is the other piece. In , the 言 tells you it's about language, and 吾 predicts the ゴ reading. In せい, 氵says "water/purity" and 青 predicts セイ. The pattern holds more often than you'd expect — and now you can't unsee it.

Tiny Win

You don't need to fix every leech today. You don't even need to fix five.

If all you did was look at one stubborn card and think "oh — that's a Ghost" instead of "I'm bad at this" — that's the shift. You just went from blaming your memory to diagnosing your cards. Everything changes from here. 💡

Further reading (optional):

For: Anyone who wants to go deeper on leech management strategy and the memory science behind it.

Use: Bookmark Anki's official leech documentation for the mechanics (threshold settings, tag behavior, suspend rules). Then read Hacking Chinese's "Killing Leeches" for practical tactics — it's written for Chinese learners but every technique transfers directly to Japanese.

Why it helps: Today's issue gave you the diagnostic framework. These resources give you the implementation details for each fix type.

Kotoba Brew — leech cards vignette

This week, triage one leech. Just one. Diagnose it, fix it, and reply to tell us: Ghost, Evil Twin, or Wrong Shape? We read every reply. (And yes, we get unreasonably invested in other people's leech stories.)

Kotoba Brew Podcast

🎧 Catch us on the Kotoba Brew podcast for more deep-dives — listen here.

これからも一緒いっしょ頑張がんばりましょうね〜 💪

— Kotoba Brew Editorial Desk

Keep Reading