Stop Giving Every Project Its Own Folder

There is a moment in most growing businesses where somebody does the sensible thing. A new project comes in, so they give it a place to live. A folder, a board, a channel, a shared space. It is tidy, it is obvious, and everyone knows where to go. Do that forty times over four years and you have forty places, none of which talk to each other.

We saw this recently at a firm that does housing policy work and also provides the staff for a separate nonprofit. Two organizations, one set of people, and a system that had grown a separate space for every engagement. These were not disorganized people. They had been organized in exactly the way that causes the problem.

How it starts

Nobody decides to fragment a business. It happens one reasonable decision at a time. Giving a project its own container is the right call on day one, when there is one project and two people. It is still defensible at project five. Somewhere around project ten it quietly becomes the thing stopping anyone from seeing the whole picture, and because no single decision caused it, no single decision reverses it.

The habit survives because it keeps working at the level of one project. Open the folder and everything about that job is there. The failure only shows up when you try to look across projects, which is exactly what owners and managers spend their time trying to do.

The moment it breaks

At the firm we worked with, their largest live engagement existed in four places at once. Its own space. A row in a projects list. A group inside a meeting notes database. A row in a research tracker. Four records for one piece of work, and none of the four agreed with each other.

Nobody had done anything wrong. Each of those four had been created by a different person, solving a real problem, on a different day. That is what makes this hard to catch. Every individual piece of it was somebody being responsible.

What it actually costs

The obvious cost is the one that rarely happens. Files do not usually get lost. They sit there, findable, in a place somebody remembers.

The real cost is quieter. Nobody can answer where something stands without going and asking a person. That makes the owner, or whoever holds the most context, the reporting system for the business. Coming back to a project after a few weeks away means rebuilding the picture from documents, spreadsheets, chat threads, email and PDFs, and the rebuild happens in somebody’s head rather than on a screen.

Why tidying does not work

The instinct when a system feels messy is to clean it. Rename things consistently. Archive what is finished. Write a convention down and ask everyone to follow it.

All of that helps, and none of it touches the actual problem. A fragmented system that gets tidied is still a fragmented system. You can only compare, total or filter things that live in the same place, and tidying does not move anything. It is the same reason a business outgrows its spreadsheets without the spreadsheets ever getting messier: the limit is structural. We wrote about that failure mode separately in Signs Your Business Has Outgrown Spreadsheets.

Three people wanted three different things

The interesting part of this engagement was not the sprawl. It was what we found underneath it.

Three people needed three different things from the same system. One wanted a single page per project he could open cold after three weeks away and immediately know where things stood. One wanted room to work loosely, because every engagement is genuinely different and a rigid form gets in the way. One wanted a checklist, and a status view that nobody else could disturb.

Read as preferences, those compete, and most teams try to settle them by negotiating or by letting everyone keep their own system. Read correctly, they do not compete at all. They are three views of the same records.

One set of records, many views

The fix is not a better folder structure. It is moving the structure to one place and letting everyone look at the slice that is theirs.

One set of records holds everything. Each team, each person, each project page shows a filtered view of that one set. Nothing is copied, so a record exists once. Change it anywhere and it changes everywhere, because there is no anywhere else for it to be. The person who wants a checklist gets a checklist. The person who wants loose space gets loose space. They are looking at the same underlying rows.

That also settles the fight nobody enjoys having, about whose system everyone should use. Once the structure is shared and the display is personal, the question stops mattering.

The part nobody expects

Before building any of that, we audited what was actually in use rather than what existed. Most of the databases turned out to be untouched sample data that had arrived with templates somebody bought and never filled in. The real work was concentrated in a handful of places.

That is the most common finding in this kind of work, and it is good news every time. The sprawl is usually smaller than it looks. What makes a workspace feel unmanageable is rarely the volume of real work. It is the volume of empty structure sitting next to it, which is why the first move is counting what is live, not reorganizing what is there.

How to check your own business

1. Count the placesList every place a piece of work can currently live: folders, boards, channels, trackers, inboxes. Most people are surprised by the number before they get to the end of the list.
2. Pick one live project and find all of itNot the files. The decisions, the open work, the last conversation. Note how many places you had to visit and whether any two disagreed.
3. Ask who has to be askedIf the answer to “where does this stand” always runs through one person, that person is the reporting system, and they are also the bottleneck.
4. Separate what is shared from what is freeThe fields other people’s views depend on should be locked and few. The space where someone thinks, drafts and takes notes should be wide open. Most systems get this backwards.
5. Move the structure, not the peopleIf the change requires everyone to work differently, it will not hold. If it requires them to work the same way and see more, it will.

What changes when it works

The visible result is a shorter list of places. The real result is that the business can see itself without anyone having to narrate it.

Nobody reports status upward, because status is already on the screen. Nobody rebuilds context after time away, because the context never scattered. Nobody argues about whose system wins, because there is one system and several windows into it. That is a quieter business to run, and it is almost always reachable with the tools a team already pays for.