What Resurfacing Cannot Do
Delivering an old note to someone is a small, cheap intervention that does one thing well. It has a ceiling, the ceiling is lower than the category's marketing suggests, and knowing where it sits is more useful than another argument about whether the idea is good.
This site is on a domain that used to run a product doing exactly this. That is a reason to be careful about the assessment in both directions.
For a workplace-oriented comparison with this kind of workflow, the reference provides additional context.
The one thing it does
It tells you something exists. You cannot use an idea you have forgotten you had, and search cannot help because search requires knowing what to look for.
Resurfacing is the only mechanism in this whole subject that operates without a query. That is genuinely valuable and genuinely rare, and it is the entire case.
Three things above the ceiling
It cannot make the note good. A fragment with no context arrives as a fragment with no context. Resurfacing is a delivery mechanism applied to whatever was written, and most of what determines whether a returning note is useful was decided at capture — twenty seconds that no downstream system can supply retroactively.
For an independent external reference related to this topic, see CNET.
This is the largest limit and the least discussed, because it points at the user rather than at the product.
It cannot produce retention. Being shown something is restudy, and the evidence is about the attempt to recall. A daily note in an inbox is not spaced repetition, whatever the marketing cites.
And it cannot create the habit of engaging. The note arrives; opening it, thinking about it, and doing anything with it are all still voluntary. What resurfacing removes is the trigger problem. What it does not remove is everything after the trigger, and in practice that is where most people stop — the email arrives, is glanced at, and is closed.
The scaling problem
Worth stating plainly because it is arithmetic rather than opinion.
One note a day from an archive of two thousand returns each note about once every five and a half years. From four hundred, once every fourteen months.
So the mechanism works better the smaller your archive is, which is precisely backwards from the situation of the people who want it most. And it means that for a large collection, resurfacing is not a way of covering the archive — it is a lottery, with a real but modest chance of a useful ticket.
Weighting the pool fixes this and almost no implementation offers it. Restricting the draw to a marked set of a few dozen changes the return interval from years to weeks and raises the hit rate enormously.
What sits above the ceiling
Three things, in order of cost.
Context at capture. Twenty seconds, and it determines whether any of this works. Free, and nobody does it.
An attempted recall before opening. Fifteen seconds, and it converts the whole operation into something the evidence supports.
And a decision on each note. Keep, promote, delete. This is what makes the practice improve the archive rather than merely sample it.
None of the three is a feature. All three are things a person does, which is why they are the hard part and why no tool in this category has ever solved the problem it is sold against.
The honest summary
Resurfacing is the cheapest useful thing you can do with an archive and the least powerful.
It is worth having. It should be expected to produce occasional rediscovery rather than retention, insight or a practice. And it works far better on forty marked notes than on four thousand unmarked ones, which is the opposite of how it is usually deployed.
If that sounds like faint praise, it is not meant to. Most people do nothing at all, and a cheap intervention that happens beats an excellent one that does not. It just should not be described as more than it is.
The short version
- Resurfacing does one thing no other mechanism does: it operates without a query
- It cannot improve a note that lacked context at capture, which is the largest and least-discussed limit
- It cannot produce retention, because being shown something is restudy rather than retrieval
- It removes the trigger problem and nothing after the trigger, which is where most people stop
- The arithmetic scales backwards: it works best on small archives and is wanted most for large ones
- Weighting the pool to a marked set changes the return interval from years to weeks, and almost no implementation offers it