Almost every practice is looking for a better folder structure. But the thing they're actually struggling with isn't folders. It's that information has never been designed to flow through the business — so it ends up scattered, duplicated, named differently by everyone, and locked inside people's heads.
This free guide fixes the real problem: not where your folders go, but how information should move through your studio.
Free · the guide (PDF) and the Studio Structure template · unsubscribe anytime
Most folder structures aren't designed. They evolve.
A folder gets made because a project starts. Another because someone joins. Another because new software arrives. Five years later, no-one knows where anything lives.
The result is familiar: people can't find things, freelancers need constant guidance, consultants get inconsistent information, new staff take weeks to onboard, and AI tools can't make sense of a business whose information is inconsistent.
The problem isn't the folders. It's that the studio has never designed an information system.
When we built this, we stopped asking "what folders do I need?" and asked something better. That single change rewrites the answer: instead of organising around people, software or departments, you organise around the life of the information itself — so every piece has one logical home, every person instinctively knows where to find it, and every future system, human or AI, can understand it.
One source of truth · organised around the business, not the software · built so people and AI can find anything.
This is the foundation every DesignFlow OS product is built to sit on.
This isn't a folder template to copy blindly. It's a way of thinking you can apply to your own studio, built on five principles.
Every piece of information has one official home. No duplicates, no guessing.
Running the practice and delivering a job are different activities; the structure should show it.
Reusable things live in a shared library; project-specific things live in the project.
Files belong in folders, but tasks, risks, decisions, procurement and FF&E belong in a work platform; money in finance software; conversations in comms. Forcing everything into folders is the most common mistake there is.
Consistent naming and predictable structure aren't just tidy; they're what let a new starter, a freelancer, or an AI assistant understand your business on day one.
The thinking: ten steps and five principles for designing an information architecture that scales — written so you can apply it to your own practice rather than copy someone else's.
The ready-made foundation: a complete studio and project folder structure with naming conventions, built on exactly the principles the guide teaches. Use it as it is, or adapt it to your studio.
The guide teaches the why. The template gives you the what. Together they're everything you need to put your studio's information on a proper footing — for free.
Whether you're starting from scratch or untangling an established studio, the goal is the same: spend less time searching for information, and more time designing.
Folders are excellent for files, but poor at managing the information that changes — the tasks, risks, decisions, procurement and FF&E that move every day. That information needs more than a folder. It needs a system.
That's what Studio OS is: the operating system that manages everything the folders can't — projects, tasks, procurement, FF&E, CRM, decisions and studio knowledge, in one connected workspace, built to sit directly on top of this structure. The free foundation prepares you for it; Studio OS is where it comes alive.
We ask for your email so we can send them to you, and occasionally share how to build on top of them. Nothing you didn't ask for; unsubscribe whenever you like.
Free · Guide (PDF) + Studio Structure template · unsubscribe anytime