Filers and Pilers: Two Ways to Lose the Same Thing

Filers vs pilers looks like a choice between an orderly folder tree and a heap of open tabs. Both can work. Both can also leave you unable to find the article you remember as “the one my sister sent about sleeping after a late shift.”

The useful distinction is where the effort goes. Filing asks you to choose a place now. Piling leaves more of the finding to later. Either approach improves when you save a short phrase explaining why the thing mattered.

Filers vs pilers began with real desks

Thomas W. Malone's 1983 paper, How do people organize their desks?: Implications for the design of office information systems, appeared in ACM Transactions on Information Systems, volume 1, issue 1, pages 99–112. It describes case studies of office workers and their desks.

The contrast concerns recognizable ways of handling papers: arranging them in named files and leaving them in piles. These arrangements serve purposes beyond looking tidy. An item kept visible can remind someone of unfinished work; a file can provide a deliberate place to look later.

Both choices have a cost. Filing requires decisions about categories and placement. A pile avoids some of those decisions but depends more on cues such as position, appearance, and memory when someone wants a paper back.

The digital examples below are a practical interpretation of that distinction, not findings from a modern phone experiment. A bookmark collection is different from a desk, even when the difficulty of deciding where something belongs feels familiar.

The filer pays at the moment of saving

Imagine saving a useful article about preparing for a difficult presentation. Your folders include Work, Communication, Learning, and Things to Try. The article could fit in all four. Choosing one feels harmless until you want it later and choose a different route through the folders.

You can create another subfolder, add tags, or keep duplicate references. Those options may help, but each adds a decision. If every useful link arrives with a small classification task, saving can become something you postpone until you have time to do it properly.

The folder structure may be perfectly reasonable. The friction comes from asking it to represent every possible future use of a piece of information. An article saved for a presentation this week might become useful for coaching a colleague next month.

Filers often benefit from stable categories where the destination is obvious: a current project, a particular client, a reference collection with a clear boundary. Keep those. The trouble begins when the category must also stand in for the reason, the source, and the future question.

A bookmark called by its original headline may sit in exactly the right folder and still be difficult to recognize. Knowing where to look helps; knowing what you are looking at is a separate part of retrieval.

The piler pays when it is time to retrieve

Now imagine saving the same article into one large collection. Capture is easy. There is no pause to choose between Work and Learning, so the useful thing gets kept while your attention is elsewhere.

For a while, recency does much of the organizing. You remember saving it just after a recipe, or seeing a blue image near the top of the collection. Scrolling feels efficient because the surrounding items are still familiar.

Later, the collection has moved. New saves occupy the top, thumbnails change, and the original sequence is harder to reconstruct. You may remember that the article exists while having no clear route to it.

Search can help when you remember words in the title or captured content. But the phrase in your memory may describe your relationship to the article: who sent it, what you were trying to solve, or where you expected to use it. Those words might not appear anywhere in the source.

A single collection remains a reasonable choice. The missing step is giving it something more dependable than the expectation that you will recognize everything when it comes around again.

The shared blind spot: a category is not the whole context

Suppose an article's title is “Making Space for Recovery.” You saved it after your sister mentioned working late shifts. Months later, you search for “sister sleep late shift.” A folder named Wellbeing and a pile of bookmarks can both contain the article without containing that phrase.

This does not mean folders cannot express purpose or piles cannot carry meaning. A folder called “Ideas for night shifts” already preserves useful context. A visible pile can serve as a reminder. The problem appears when that context remains only in your memory.

Your own sentence makes the connection explicit: “My sister sent this because I struggle to wind down after a late shift.” It need not summarize the whole article. It tells you why this particular source entered your collection.

That distinction matters because a polished summary can still omit the detail you remember. A summary about rest routines might accurately describe the article while leaving out your sister and the late shift. The missing information is personal context, not another description of the source.

Add one phrase without rebuilding the system

Start with the next thing you save. Use the description or note field if your saving tool provides one. In Chrome's bookmark editor, you can append a short phrase to the bookmark's name. Keep enough of the original title to recognize the source.

If a tool has no suitable field, put the reference and your sentence together in a note you can search. Do not scatter the sentence somewhere unrelated and assume you will remember which item it belongs to. The connection should survive without you supplying it again.

What the desk research cannot tell us

Malone's paper is more than forty years old and concerns physical office information. It does not establish that the same behaviors produce the same results in browser bookmarks, saved videos, or phone apps. Search, copies, changing links, and automated indexing alter the conditions considerably.

It also does not prove that adding a sentence will solve every retrieval problem. A deleted source, inaccessible account, or inaccurate remembered detail needs a different response. The sentence is a practical suggestion drawn from the recognizable tension between easy capture and later finding.

You may file some things and pile others. Work references might need shared folders, while recipes can live in a single collection. There is no need to choose one identity or make every part of your digital life look the same.

Keep the method; make the reason retrievable

For a place to hold that context, dEssence lets you manually save a thing together with your own words and later ask about it in your own words. It does not supply an unspoken reason or require you to rebuild a folder system. Save the detail you expect to remember, and keep enough source information to check the result.

A successful system can look ordinary: some folders, a loose collection, and a few imperfect notes. Judge it by whether you can get back to the thing you wanted. The next useful change may be a sentence, not a weekend spent reorganizing.