A folder system works when you can decide where the next file belongs. You do not need a folder for every file type or every week. Start with a small set of ordinary documents you control, and leave the rest of your computer alone.
Download the practice ZIP and the example directory tree. The ZIP contains four harmless text files, including its README, under one top-level folder. All workshop details are fictional.
See what is mixed together
The fictional “before” folder below mixes an unfinished note, a reference list, and an older revision:
Desktop pile/
2026-11-10_workshop-notes_v02.txt
reference/packing-list.txt
2026-11-03_workshop-notes_v01.txt
Ask what each file is for. A document you are editing belongs with its project; a reusable checklist belongs in reference; a finished older revision can go in the project’s archive. File extensions alone do not answer that question.
Make four destinations
Digital-desk/
00-inbox/
10-active/
community-workshop/
20-reference/
90-archive/
The numbers keep these four folders together in a Name sort. They are a convenience, not a requirement. The inbox is a temporary decision point, not a second permanent Downloads folder.
On macOS Tahoe 26, open the location where you want your practice folder in Finder, then use File → New Folder or Shift-Command-N. Name it Digital-desk and create the child folders inside it. If New Folder is unavailable, check whether you are in a writable location rather than changing system permissions.
Place the practice copies
- Extract the practice ZIP into a temporary learning folder. Read its README and confirm the four files open as text.
- Copy
2026-11-10_workshop-notes_v02.txtinto10-active/community-workshop/. Keep the extracted source set intact for comparison. - Copy the packing list into
20-reference/and the earlier note into90-archive/. - Put an undecided disposable note into
00-inbox/. At your next review, choose a real destination or intentionally remove the copy. - Add a short README if another person needs to understand the structure. A folder’s purpose should not depend on its creator remembering it.
Your completed practice folders should contain these exact samples. The added inbox note is one you create; the ZIP’s README stays with the protected source.
Digital-desk/
00-inbox/undecided-note.txt (your new disposable note)
10-active/community-workshop/2026-11-10_workshop-notes_v02.txt
20-reference/packing-list.txt
90-archive/2026-11-03_workshop-notes_v01.txt
Do not move the computer’s own working files
Do not apply this structure to application libraries, system folders, mail databases, or assets that an open application locates by path. Do not move a cloud-synced folder without checking the sync service’s documented process. The exercise is for ordinary documents, not a migration of your user account.
If a file is linked from a spreadsheet, design project, or shared workspace, moving it may break the reference. Work on copies first and confirm the application can still find its inputs before reorganizing real work.
Check whether the system helps
Close the folder and try to retrieve the latest workshop note without using Recents. You should be able to explain why it is in Active rather than Reference. Compare the practice source against your new folders: every moved or copied item should have an intentional destination.
If you need more than a few seconds to choose a location, simplify the rule before adding more subfolders. A shallow structure with clear purposes is easier to maintain than a beautiful tree nobody uses.
References & scope
These official references support the software instructions. Practice documents are original, fictional teaching examples; labels can vary by release.
- Organize files in folders on Mac
Create folders and copy or move files in Finder; cross-disk moves can copy instead.