Why Your Folder Structure Is Fighting You
Why Your Folder Structure Is Fighting You
At some point, every team has the folder reorganization conversation.
Someone suggests the current structure "doesn't scale." A few people agree. Someone draws a proposed hierarchy on a whiteboard. There's a vote, a migration, and a brief period of clarity — before the new structure starts developing the same problems as the old one.
Then, six months later, the conversation happens again.
The reorganization isn't the fix. The folder model itself is the problem. And until you understand why, you'll keep having the same conversation on a longer cycle.
The Assumption Folders Make
Folders assume that every piece of information has one correct home. One place it belongs, one path to find it.
That assumption is clean and intuitive. It's also wrong for almost everything worth documenting.
Think about a product spec. Does it belong in the product folder? The engineering folder? The roadmap folder? The folder for Q2 projects? All of those answers are right. So you pick one, and then you get questions from everyone who looked somewhere else.
Or a post-mortem document. Is it an engineering artifact? An ops document? A company-wide reference for how to handle incidents? It's all three, depending on who's asking.
Folders force you to resolve this ambiguity permanently, at the moment of creation, when you know the least about how a document will be used. And then they punish you for getting it wrong by making the document invisible to anyone who looked in the logical but incorrect place.
How People Actually Find Things
Watch how people actually use a shared workspace for a week. Almost nobody opens the sidebar and browses through folders. They type something into search, or they click a link someone sent them, or they navigate from a task to the doc linked inside it.
The folder tree is mostly decorative. People use it for two things: filing new documents (because they have to put it somewhere) and occasionally reorganizing it when it gets too cluttered. Almost never for finding.
If the navigation model you've built isn't how people actually navigate, why are you spending time maintaining it? And more importantly — why is finding something contingent on knowing which folder someone chose six months ago?
Spaces Work Differently
Closot organizes information using spaces instead of folders. The shift sounds subtle. The practical difference is significant.
In a folder model, a document exists in one place. In Closot's space model, a document can be referenced in multiple contexts simultaneously. The product spec lives in the product team's space and is linked from the engineering project board and appears in the Q2 project overview — not because it was copied, but because each of those contexts links to the same document.
When the document changes, every context reflects the update automatically. No version drift. No "wait, which copy is current?"
The underlying structure is a graph of connections rather than a tree of containers. That maps much more closely to how information actually works — ideas reference each other, decisions connect to their context, projects link to their documentation.
What This Means for Search
When everything is connected through explicit links rather than implied folder proximity, search gets dramatically better.
In a folder model, finding something requires knowing roughly where to look. In a connected workspace, you can start anywhere and follow links outward. You find the project board, and from there you find the spec, and from the spec you find the decision doc, and from the decision doc you find the meeting notes where that decision was made.
That's institutional memory that actually works — not because someone designed the perfect folder structure, but because the connections between pieces of information are built as the work happens.
The Practical Shift
Switching from folders to spaces doesn't mean abandoning all structure. It means building structure around how your team actually navigates information — by searching, by following links, by jumping from a task to its context doc to the wiki page that explains the background.
In Closot, you still organize content into spaces. But spaces don't have to be exclusive. A document isn't trapped in the space where it was created — it can be linked from anywhere it's relevant.
The result is that you stop designing folder hierarchies and start building something closer to how your team actually thinks. The right answer to "where does this live?" becomes "wherever it's relevant" — not "wherever we decided to put it six months ago."
Closot replaces rigid folders with connected spaces — so your team can find what they need by searching or following links, not by guessing where someone filed it. Explore Closot.