Start with a map, not a cleanup
A scattered digital setup can make every search feel like a decision: was that idea in a notes app, a document, an email, or a message? The temptation is to pick a new tool and move everything into it. First, make a map of what exists. An audit shows which spaces are useful, which overlap, and which hold information you rarely need.
Set aside a short session and create a plain list or table. Add a row for each place you store or receive information: your computer, cloud drives, notes apps, email, chat, bookmarks, task lists, photos, and shared team spaces. Include paper if you regularly photograph or transcribe it. At this stage, name the places rather than sorting their contents. You are building a view of the system, not fixing it in one sitting.
Record what each place is for
For each location, note the kinds of material it contains and why it ends up there. A cloud drive might hold finished documents and drafts; chat might hold decisions that never made it into a project file. Add who can access the space, whether you control it, and whether you still use it. Shared folders and accounts deserve attention because moving their contents may affect someone else.
Keep the descriptions broad enough to finish the audit. You do not need a catalog of every file. Labels such as “meeting notes,” “receipts,” or “project references” are enough to reveal patterns. If one place serves several purposes, list them separately rather than forcing it into a single category. That distinction can help you see whether the space needs a clearer role or simply a better way to find things.
Trace a few real retrieval paths
A location list tells you where information sits; a retrieval check tells you whether the setup works. Pick a handful of things you recently needed, such as a draft, an attachment, a meeting decision, or a useful reference. Without moving anything, write down where you looked first, where you found the item, and what made the search easy or difficult. Use ordinary examples from your work rather than staging a perfect test.
Notice repeated friction. Perhaps you search email for files that belong with a project, or keep checking two task lists because neither feels authoritative. Also note what works well. A folder that seems untidy may still be easy to search and familiar to everyone who uses it. The goal is not a uniformly neat system; it is a system in which you can find what you need and understand where new material should go.
Mark overlaps, risks, and unclear ownership
Once you have the map and retrieval notes, mark each location as keep, review, or retire later. “Review” can mean that its purpose is unclear, not that it must go. Highlight places where the same kind of information appears in several forms: a decision in chat, a personal note, and a shared document, for example. Ask which version people are expected to use. A simple source of record can be more helpful than copying everything into another app.
Before deleting or migrating material, check practical constraints. Is a folder shared? Does an app have an export option you can use? Are files available elsewhere if a move goes wrong? Some accounts or records may need to stay where they are for reasons outside your personal workflow. If you are unsure, leave them in place and label the uncertainty. An audit should reduce accidental loss, not create pressure to make every decision immediately.
Choose one small change to test
Turn the audit into a short list of changes, ordered by the problems you actually noticed. You might give active project files one home, add a link from a task to its reference document, or write down where your team records decisions. Choose one change that is easy to explain and reverse. For new material, set a simple rule such as “project notes go in the project folder,” then try it during normal work before moving older material.
Keep the map somewhere you can find it and update it when a tool or routine changes. It does not need to become another elaborate system. Its value is in making the current arrangement visible, so future reorganizing is a deliberate response to a real problem rather than a fresh start that leaves the same confusion behind.
