Spaced repetition can lower the stakes around destructive inbox-maintenance operations

Inboxes only work if you trust how they’re drained, but Triage strategies for maintaining inboxes (e.g. Inbox Zero) are often too brittle. In large part that’s because Software interfaces often harmfully frame destructive operations as final decisions, not contingent preferences.

If you recast the destructive operations as “not right now,” they feel completely different. That browser tab isn’t gone—it’ll come back later. Maybe it’s a day later at first, then if I skip it again, a few days later, then maybe a week, and so on, until “not right now” is effectively “close”… but it doesn’t feel nearly so stressful. This notion can be applied to task queues, reading lists (A reading inbox to capture possibly-useful references), email inboxes, etc. Spaced repetition mechanics create a sense of effortlessness.

It helps me to bring some physicality into the metaphor. Imagine your desk has lots of papers on it. You naturally pull out the few which you’re using at the moment, and maybe you set a few aside for special attention. The rest sit, perhaps in a couple of piles. You intermittently look through the piles, pulling out ones which strike your fancy. The ones which sit long enough start to simply dissolve, compost into the table surface. You can always restore them if you like, but if you don’t, they’ll get tilled under.

This is an example of a way in which Spaced repetition systems can be used to program attention.


References

Matuschak, A. (2019, December). Taking knowledge work seriously. Presented at the Stripe Convergence, San Francisco.

Discovered in Dec 2020 that Simon Hørup Eskildsen blogged about a similar idea in June 2018.

A reading inbox to capture possibly-useful references

To avoid a proliferation of anxiety-inducing browser tabs and a terrifying folder of PDFs, it’s important to have an automatic procedure for capturing references to readings which might prove useful.

Once captured, each item in the inbox either:

  1. gets trashed (doesn’t look like it’s worth a detailed read after all)
  2. gets read in a serious fashion (i.e. Write about what you read to internalize texts deeply)
  3. gets read shallowly and filed in the reference library
  4. (maybe) gets added to some other list like “recipes to be cooked”

Importantly, this isn’t a “someday maybe” list. It doesn’t accumulate indefinitely, because then it wouldn’t be a reliable way to Close open loops.

So, when constructing a reading inbox, the important considerations are:

  1. zero-friction capture for books, articles, web pages (to easily close that loop)
  2. zero-friction to view the reading corresponding to an inbox item
  3. zero-friction listing across item type
  4. the inbox should encourage lingering items to be removed (e.g. it should be obvious when one has been passed over many times)

Interestingly, no existing “read later” or reference management system fits these criteria. They’re usually siloed by content type, and none of them encourages lingering items to be removed. See also: Beware automatic import into the reading inbox.

The reading inbox is an important release valve for things I encounter when on my smartphone (see Use phones to collect and triage, not (usually) to read).

Related: Incremental reading


References

Note-Taking when Reading the Web and RSS • Zettelkasten Method

The Inbox is the place to hold the items we either want to or need to pay attention to. A lot of stuff will never reach our inbox; we can shut off the noise outside.

Some things that found their way onto the reading lists turn out to be useless. Toss them. Putting items on the reading list is a tiny commitment only: we commit to pay attention to them later, but we don’t need to hold on to them if they don’t withstand a critical look.