SRS Is Not a Memorization Tool

When I first encountered Anki, I was genuinely amazed. The gap between paper flashcards and a system that schedules reviews based on how well you know each thing — that felt like a genuine leap. I wrote about it obsessively.

But the memorization framing eventually started feeling limiting. The mechanism isn’t really about flashcards or retention rates. It’s about controlling when you encounter something again. That’s a much more general capability than “studying for exams.”

What SRS actually does

The core mechanic is simple: things you know well get shown less often, things you’re shaky on get shown more. The Ebbinghaus forgetting curve shows that most information is lost within 24 hours — but reviewing at the right intervals drives retention up exponentially.

Anki implements this as flashcards, which is why most people think of SRS as a memorization tool. But the underlying principle — controlling the timing of re-encountering something — applies to almost anything you want to return to.

The more precise framing: SRS is a tool for managing forgetting. Memorization is one application of that.

Three applications that aren’t memorization

Note cultivation — incremental writing

The Obsidian Spaced Repetition plugin lets you apply the SRS algorithm to your own notes rather than to flashcards.

The review session looks different from Anki. Instead of “do I remember this?”, the question is “what can I add to this now?” Each session, you spend a few minutes with a note — refining a sentence, adding a link to something you’ve written since, cutting something that no longer fits. Five minutes per note, five sessions over a few months, and a note becomes something you couldn’t have written in a single sitting.

The psychological effect matters here. Trying to write something complete in one sitting creates pressure that often causes paralysis. When the system schedules the next visit, that pressure disappears. You’re not finishing — you’re just doing today’s increment.

Task management — cycling the someday list

GTD’s “someday/maybe” list has a well-known failure mode: it fills up, the weekly review becomes overwhelming, and the list turns into a graveyard of intentions.

SRS changes the structure. Tag items as “someday,” let the system schedule when they resurface. You don’t review the whole list — you review the five items that come up today, decide each one, and move on. The system handles the scheduling so you don’t have to.

This works because the problem with someday lists isn’t the items — it’s the overhead of managing them. SRS reduces that overhead to near zero.

Idea maturation — designing the re-encounter

Notes written weeks or months ago often read differently than they did when you wrote them. A half-formed thought from three weeks ago can suddenly connect to something you read yesterday. This happens by accident sometimes, but SRS makes it happen by design.

The shift is changing the review question from “do I remember this?” to “does this connect to anything I’m thinking about now?” That reframe turns SRS into something closer to an incubation system — a way of returning to ideas before they’ve fully developed, and developing them incrementally over time.

The counterintuitive point: SRS helps you forget

The most useful thing I’ve learned from extended SRS use is that it’s fundamentally a tool for safe forgetting, not for remembering.

Once something is in the system, it will come back. That guarantee removes the mental overhead of trying to hold things in your head “just in case.” The cognitive space that was occupied by “I need to remember this” becomes available for whatever you’re actually working on.

Starting from memorization, SRS turns out to be infrastructure for how knowledge develops over time — not a way to hold more in your head, but a way to use what you’ve already accumulated.

The Japanese version covers implementation details and specific Obsidian plugin setup: 日本語版 →