Weekly Note Pruning for Overgrown Folders

Find Core Insight
Weekly Note Pruning for Overgrown Folders
Method diagram
Method diagram

Weekly Note Pruning for Overgrown Folders. Notes rot quietly. A 15-minute weekly prune prevents annual desperate cleanup.

Friday 3:40 — Leo opens the vault with a timer

Leo sets fifteen minutes—hard stop at 3:55. He opens his notes app to the review tag and sorted-by-modified view. He does not redesign folder trees on prune day; tree redesign is quarterly work with a beginning and end. Friday is hygiene only.

He keeps a single line log after each session: deleted 4, archived 6, merged 2. Zeroes three weeks running mean capture is too loose or he is browsing without deciding. Counts make pruning real.

Checklist item: duplicates and near-duplicates

Search the week’s key terms: customer name, project codename, API version. Merge notes that answer the same question. Leo found three notes titled variants of vendor SLA; one ref note survived with links from old project notes.

Failure mode: keeping both because merge feels irreversible. Archive the loser; merging is reversible enough for personal systems. Require at least two destructive actions—archive or delete—each prune until the habit toughens.

Leo photographs merged losers before archive when legal might ask—one photo, not a full export. Lightweight reversibility beats hoarding duplicates.

Checklist item: finished projects

Any project note whose outcome shipped gets a harvest line, then archive. Leo archived March webinar launch after copying one lesson—he did not export forty pages of rehearsal notes.

Unopened six-month notes that are not legal or compliance records can archive without drama. If you have not opened them and nobody else depends on them, they are not working knowledge—they are emotional storage.

Checklist item: stale action and waiting tags

Notes tagged action or waiting older than fourteen days get a fork: redate with a real next step, move verb to task app, or delete if the work died quietly. Waiting notes without a person’s name in the title get renamed or deleted.

Orphans—notes with no links, tags, or clear title—get one decision: title and tag them, merge them, or delete them. Visiting orphans every week without deciding is how clutter becomes a personality trait.

Checklist item: same-question merges

Leo scans titles for the same question in different words: Launch risks and What breaks if we slip? may be one hub. Merge upward into the clearer question title; link sources with dates.

Do not merge if the notes answer different questions—even if the topic word matches. The test is search behavior, not keyword overlap.

Emergency ten-minute prune when Friday explodes

If the calendar breaks, Leo runs archive-only: finished projects and duplicates, no merges. Partial hygiene beats the annual Saturday purge that makes people swear off notes entirely. Measurable signal: review tag count under ten entering the weekend.

Attach prune to an existing Friday review so it does not rely on motivation. If Friday is slammed every week, the calendar problem is upstream—but ten-minute emergency prune still beats zero.

Leo once skipped four Fridays during a launch. review tag hit forty-one. Emergency prune archived only finished projects in ten minutes; merged duplicates the next week. Partial recovery beat waiting for a free Saturday that never came.

Leo’s prune log — three sample weeks

Week 12: deleted 3, archived 8, merged 2 — review tag 7.

Week 13: deleted 0, archived 4, merged 1 — review tag 11 (capture too loose; tightened inbox sweep).

Week 14: deleted 5, archived 6, merged 3 — review tag 6.

The log fits one line. Trends matter more than any single heroic session. Zero deletes for a month is a warning light, not a virtue.

Leo shares the log line with his team sometimes—archived 6 proves maintenance happened. Visibility prevents the shame spiral that makes people avoid notes entirely.

When review tag spikes after a busy launch, Leo runs emergency archive-only prune—ten minutes, finished projects only. Partial hygiene beats skipping prune entirely until a mythical free Saturday.

Quarterly tree redesign — not on prune day

Leo schedules tree redesign separately: ninety minutes once per quarter with an explicit end. Prune day touches only hygiene. Mixing them is how fifteen minutes become a lost Saturday and prune gets skipped entirely.

Quarterly work answers: Are folder names still questions we ask? Weekly work answers: What can leave today? Different questions, different calendars.

After Leo separated the two, weekly prune completion went from sporadic to four Fridays per month. The timer finally meant delete, not redesign.

Leo’s quarterly redesign once merged two folders that differed only by year in the title—same questions, duplicate answers. Merge saved search hits, not disk space.

Orphan photo — Leo’s archive safety net

Before deleting a note Leo never opened, he screenshots the title and first screen to an archive-log note—one line each. Takes five seconds. Recovery happened twice in a year; both times the orphan was truly dead and he felt better having looked once.

The photo log is not re-reading everything—it is permission to delete with a thin safety net. Without permission, orphans live forever.

Archive-log stays under fifty lines; old lines delete quarterly. The log is hygiene too.

Leo attaches prune to his existing Friday review block—same calendar dignity as standup. When prune shares a slot with something real, it survives busy launches.

Prune attached to Friday, not motivation

Counts in one log line turn vague guilt into a number you can improve. If deletes scare you, archive first; but do not archive everything—that is hiding, not pruning.

Tree redesign is a quarterly project with an owner and end date. Weekly prune is not the time to invent new folders—that is how fifteen minutes become a lost Saturday.

Prune is subtraction practice. Teams that never delete notes eventually stop trusting search entirely.

Fifteen minutes on Friday beats a heroic annual purge that makes people swear off notes forever.

Leo’s one-line log turns prune from mood into metrics—share it if shame keeps your team from deleting anything.

Require two destructive actions per prune until the habit toughens—archive counts; zero-destructive weeks mean capture is lying to you.