#workflow

Spent most of today reorganizing my project folder structure, and it reminded me how much time we waste hunting for files. I timed myself yesterday—eight minutes looking for a single reference image buried three folders deep. Eight minutes I'll never get back.

Here's the system I built today that cut my search time to under thirty seconds:

The Three-Layer Rule

Spent the morning reorganizing my project folders, and the difference in mental clarity is genuinely startling. I'd been dumping files into a single "Projects" folder for months—screenshots mixed with final exports, source files buried three clicks deep. Opening that folder felt like walking into a cluttered garage where you know the tool you need is somewhere.

Here's the system I landed on after testing three different approaches. First, I created a master template folder with these subfolders: 01-Research, 02-Assets, 03-Working, 04-Final, 05-Archive. The numbers force alphabetical sorting, so the structure stays consistent across every project. Then I duplicated that template for each active project.

The key mistake I kept making? Skipping the Archive folder. I'd finish a project and leave everything in Working or Final, thinking I'd remember which version was current. Two weeks later, I'm staring at "design-v3-FINAL-actual-final.psd" and questioning my life choices. Now, the moment a project wraps, anything that isn't the absolute final deliverable goes straight to Archive with a date stamp.

Stared at my browser this morning—forty-three tabs open across two windows. The fan kicked on with that soft whirr that means my laptop is working harder than it should. Half those tabs were articles I'd "definitely read later," the other half debugging pages from yesterday that I'd already solved.

Here's the quick system I built to fix it:

First, I installed a tab manager extension (I use OneTab, but Session Buddy works too). Then I created three rules:

Spent the morning reorganizing my project folders, and it reminded me why I keep coming back to the three-folder rule. The light from my desk lamp was catching all the dust on my keyboard—guess that's another task for later—but I stayed focused on the cleanup.

Here's what actually works: create three top-level folders in every project. Source for code and raw files, Build for compiled outputs, and Docs for everything else. That's it. The moment you add a fourth category, you start second-guessing where things go.

The checklist:

Spent the morning cleaning up my desktop workflow, and it reminded me why I keep putting this off—it feels tedious until you actually finish. I had seventeen browser tabs open, three different note files for the same project, and my downloads folder looked like a digital landfill. The light from my window kept hitting my monitor at exactly the wrong angle, so I finally moved my desk two feet to the left. Small change, huge difference.

Here's what actually worked: I picked one thing to organize first—my browser bookmarks. Not the whole system, just bookmarks. Took about fifteen minutes. I created three folders: "Daily," "Reference," and "Someday." Anything I hadn't clicked in two months went to Someday or got deleted. The mistake I almost made? Starting with everything at once. I've tried that before and quit halfway through when my lunch break ended.

Quick checklist if you want to try this:

Spent the morning reorganizing my project folders after realizing I'd been searching for the same file three times this week. The afternoon light coming through the window made the dust on my keyboard painfully obvious—a good reminder that digital clutter and physical clutter often go hand in hand.

Here's the system I settled on after testing two different naming conventions:

The 3-Layer Rule: