Sort Any Folder in 20 Minutes: Four Moves That Get It Done
Four moves get any folder back to an operable state in 20 minutes.
The article presents a four-step method for organizing any folder in 20 minutes. The core idea: whether a folder is messy isn't the point—whether its purpose is clearly defined is. Step one, the only one requiring real thought, is writing the folder's specific purpose in one sentence with a target and deadline; if you can't, the problem is a missing purpose. Then sort by next action rather than file type into ACT/FILE/KILL piles, forcing a decision for every file. Kept files should be named by "what, who, when" so a stranger can find them. Duplicates: keep the latest and delete the rest. Undecidable files go into a dated unsorted pile. The method works because it front-loads decisions—not aiming for perfect archiving, just restoring an operable state.
Most people describe their Downloads folder as "a total mess," but the problem isn't the mess—it's that nobody ever defined what the folder is for. Without a clear purpose, none of the files inside have a "next action." An AI agent (yes, the author himself) shares a four-step method that claims to make any folder manageable in 20 minutes. The core insight: the key to organizing isn't categorization—it's decision-making.
Write a one-line purpose first, then start
The author stresses that before touching anything, you must write down the folder's purpose in a single sentence. Not a vague word like "documents," but a specific goal that includes a target and a deadline—for example, "Send the lease documents to the landlord by Friday" or "Collect all source notes for Chapter 3." If you can't write that sentence, that's the real problem—you haven't figured out why this folder exists. Don't organize a folder whose purpose you can't even articulate.
This step is the only part of the whole method that requires real thinking, and the author considers it the most valuable part of the 20 minutes.
Sort by next action, not by file type
When sorting, create only three piles: ACT (needs handling and has a date), FILE (already has a home—move it there), and KILL (duplicates, expired, or never opened—delete outright). The author specifically warns against creating folders like "Documents/Images/Videos"—those are just storage furniture, not decisions. Folders organized by type essentially still haven't made a decision.
The clever part of this sorting logic is that it forces you to answer "what happens next" for every file, rather than "what is it." The former produces action; the latter just produces more drawers.
The ACT / FILE / KILL three-pile method essentially borrows the "Next Action" principle from personal knowledge management, a concept first systematized by David Allen in GTD (Getting Things Done): any material entering the system must ultimately correspond to a specific next action that can be determined within two minutes, rather than lingering in a "to be categorized" state. Unlike creating folders by file type (documents, images, videos), action-oriented sorting gives each file a single home at any given moment, while also allowing that home to shift as actions are completed—files in ACT naturally flow into FILE or KILL once handled. This approach aligns with the "inbox zero" philosophy: the point isn't to archive everything beautifully, but to clear out unresolved states and return the system to an operable starting point.
Name files from a stranger's perspective
For files you keep, the naming must let someone who has never met you find them: what it is, who it's about, and when. lease-2024-signed.pdf is clearly better than scan_0012.pdf. If a name requires extra explanation from you, rename it now. This rule seems simple, but it dramatically reduces future retrieval costs—after all, your future self isn't that different from a stranger.
Delete known duplicates and keep one dated "unsorted" pile
When you encounter duplicates, keep the latest version and delete the other—don't re-read them to confirm, you've already decided. As for files you can't decide on right now, toss them all into an "unsorted" pile labeled with today's date. Next week you'll probably delete most of them. The author's principle: "The rule isn't to organize everything—it's to make some decisions."
The whole method sounds simple, but the execution bottleneck is that first sentence. The author even offers free help: reply with the folder's purpose and roughly what's in it, and he'll tell you what sentence to write and which of the four moves you're actually stuck on.
Why this method works
Traditional organizing methods fail because they tend to focus on "how to categorize" while ignoring "why keep it." The four-move method front-loads the decision: define the purpose first, sort by action, then lock in decisions through naming and deletion. It doesn't aim for perfect archiving—just to get the folder back to an "operable state." For anyone drowning in their Downloads folder, this might be the most practical way out.
If you want to try it right now, pick one real folder, write that one-line purpose, and start dividing into three piles. Twenty minutes later, you'll at least know where you're stuck.
One-line Summary
Four moves get any folder back to an operable state in 20 minutes.
Paragraph Summary
The article presents a four-step method for organizing any folder in 20 minutes. The core idea: whether a folder is messy isn't the point—whether its purpose is clearly defined is. The first step, and the only one requiring real thought, is writing the folder's specific purpose in one sentence, including the target and deadline; if you can't, the problem is a missing purpose. Then sort by next action rather than file type into ACT (to-do), FILE (archive), and KILL (delete) piles, forcing a decision for every file. Kept files should be named by "what, who, when" so a stranger can find them. Duplicates: keep the latest and delete the rest. Undecidable files go into a dated unsorted pile. The method works because it front-loads decisions—not aiming for perfect archiving, just restoring an operable state.
Related articles
RAG Interview Essentials: Breaking Down the Full Offline Indexing and Online Retrieval Pipeline
A complete breakdown of the RAG retrieval-augmented generation workflow: offline document loading, chunking, vectorization, and indexing; online query rewriting, vector retrieval, reranking, and generation, plus core interview points and system optimization directions.
AI Large Models for Absolute Beginners: Principles and API Calling in Practice
From AI's evolution to large model training principles and core concepts like Token, Temperature, and Top-P, this article explains system prompts, Function Call, RAG, and memory with hands-on examples and four API call scenarios—ideal for beginners.
Will GitHub Die? Open Source Maintainer Burnout and the Collaboration Crisis in the AI Era
Lex Fridman podcast discussion on open source maintainer burnout and GitHub's predicament: massive pull requests overwhelm core maintainers, and AI worsens code bloat. Using math journal peer review and Poincaré conjecture verification as analogies, the article analyzes why verification in knowledge production must be deliberately slow, and how open source communities can avoid the failure mode of maintainers exiting.