I used to think the problem was that I wasn't organized enough.
I had screenshots going back years. Bookmarks in folders I hadn't opened since I made them. Notes app entries with titles like "idea" and "idea 2" and "idea (this one is good)." Every so often I'd try to fix it. Rename things. Build a folder structure. Sort it all into categories that made sense at 11pm on a Sunday.
Two weeks later it would look exactly the same as before.
For a long time I thought that meant I was bad at this. It took longer than I'd like to admit to realize the tools were the problem, not me. I was trying to force something that doesn't want to be forced.
Memory doesn't arrive labeled
Think about the last time something actually stuck with you. A color in a film. A sentence in an article you can't fully remember but keep thinking about. A photo someone sent you that you didn't do anything with, you just didn't want to lose it.
None of that arrived with a category attached. You didn't think "I should file this under inspiration, subfolder color palettes." You just noticed it. It mattered, and then you moved on with your day.
That's how memory actually works. It comes in pieces. A moment, an image, a phrase, something that catches on the way past. Not a filing system. Fragments.
The tools we use to save things assume the opposite. They assume that if you cared enough to save something, you'll also care enough to name it, tag it, and put it somewhere sensible. But those are two completely different kinds of effort, and the second one is work in a way the first one never was. Noticing something is easy. Filing it is a chore. Most of us are willing to do the first and not the second, which is exactly why the screenshots pile up.
The gap isn't a discipline problem
Here's the part that took me a while to sit with: the issue was never that I lacked a system. It's that the systems all assume memory is something you manage. Something you keep on top of, like email.
But you don't manage a memory. You have one, or you don't. When something matters, you keep it. When it stops mattering, you forget it. There's no step in between where you're supposed to sit down and organize your own mind.
So when something matters enough to save, I think the right move isn't to file it. It's to leave a trace of it. Keep the thing, keep a bit of its context, and let it go. Not because you're lazy, but because the alternative (deciding right now, in advance, exactly how you'll want to find this again in eight months) is a bet you're almost always going to lose. You don't know yet what word you'll search for later. You'll remember the color, or the feeling, or roughly when you saved it. You won't remember the folder.
Building for rediscovery, not filing
This is the whole idea behind Trase. When you save something, you don't have to decide where it goes. You don't tag it, you don't file it, you don't build a structure it has to fit inside. You just keep it, and Trase quietly remembers enough about it that you can find it again later, the way you'd actually think to look. By color. By roughly when. By what it was about.
That's not because organizing is bad. Some people genuinely like it, and that's fine. It's because requiring it up front is a bad trade for most people, most of the time. You end up doing work today to save time later, except the "later" almost never comes the way you expected, and the work you did today mostly goes to waste.
The traces you leave aren't supposed to be sorted. They're just supposed to still be there when you need them, and easy enough to find that looking for them doesn't feel like opening a drawer you're dreading.
That's the whole bet. Memory isn't a system. It's fragments, held loosely, until you need one of them again.
If this is the first thing you've read about Trase, here's the short version of why it exists.