The Shared Drive That Finally Made Sense: A Naming Case Study

The Shared Drive That Finally Made Sense: A Naming Case Study

This is a short case study about a small team and a shared drive that nobody could use. The team is fictional, but the pattern is real: a handful of people, a busy quarter, and a folder structure that grew by accident. What turned things around was not new software. It was agreeing to give every file, folder and booking confirmation a clear name, and the story shows how much a naming rule can change when it is treated as an experiment rather than a chore.

The setting: a five-person team with too many “latest” files

The team handled content, small client projects and the occasional group trip for a partner event. Work arrived in bursts. Every burst left behind files with names like “plan_v3_latest”, “client notes NEW” and “trip details final final”. Three people had their own idea of where things lived, and two of them kept private copies on their laptops because the shared drive felt unreliable.

Nobody was careless. Each name made sense to its author on the day. The trouble was that the drive had to serve people who were not in the room when the name was invented.

Step one: measure the pain instead of guessing

The team lead suggested a plain test, and the analytical streak of the group appreciated it. For one week, every time someone had to ask “where is the file for X?”, they dropped a tally mark into a shared note with two details: what they were looking for and how it was eventually found. No scoring system, no new tool, just a list.

At the end of the week the list told a clear story. Most of the questions were not about missing files. They were about files that existed but could not be recognised from their names. The second most common cause was two near-identical files where nobody knew which one counted. Hardly any problems came from files being stored in the wrong place at all.

That finding mattered because it changed the proposed fix. A restructure of the folder tree had been on the table. The evidence suggested the tree was acceptable; the labels were the weak point.

Step two: write the naming rule on one page

The team drafted a rule that fitted on a single page. It had four parts:

  1. Start with the project or topic, in plain words, lowercase, joined by hyphens.
  2. Follow with what the file is: brief, notes, itinerary, invoice, draft, export.
  3. End with the detail that separates it from its siblings, such as the audience, the city or the version.
  4. Never use “final”, “new”, “latest” or “copy”. If a file is the current one, it lives in the folder called “current”, and older ones go to “archive”.

The last point solved the version problem without clever naming. Instead of asking every file to describe its own freshness, the folder did that job once.

Step three: apply it to a real, messy project

The test case was a partner event requiring travel for four people. In the old world, the trip would have produced a scatter of files: flight confirmations, accommodation emails, a rough itinerary, scanned receipts, a spreadsheet of costs. Under the new rule, the folder was called “partner-event-trip” and held items such as “partner-event-itinerary-day-by-day”, “partner-event-accommodation-confirmation-print-copy” and “partner-event-cost-sheet-working”.

When the planning stalled over choosing a route for an add-on side trip, a teammate recalled an article about exploring MedellĂ­n, Bogotá and the Caribbean coast on two wheels. They saved it as “side-trip-route-ideas-reading” in the same folder. A month later, when the travel plan was reopened, that reading note was found in seconds, not rebuilt from memory.

What changed, according to the second week’s tally

The team repeated the tally the following fortnight. The pattern in the list shifted in a way that was easy to read even without a spreadsheet. The “I cannot tell which file this is” entries dropped sharply, and what remained were mostly cases where a new file had been saved with an old habit. Those were corrected on the spot, and the shared note became a place to jot down awkward cases rather than complaints.

Three effects were noticed, none of them dramatic, all of them useful:

  • Newcomers could find things without a guided tour.
  • Private laptop copies faded because the shared drive was now trusted.
  • Meetings spent less time on “which version are we looking at?”

Objections the team heard along the way

Not everyone welcomed the rule at first. One teammate worried that long names would clutter the screen; another said search already handled everything. The tally answered both. Search had been used in many of the logged hunts and had failed in exactly the cases where the name carried no words worth matching, such as photographed notes and scanned receipts. Longer names cost a few extra keystrokes at save time and removed the guessing at open time. After the second week, the sceptics were the ones reminding others to rename.

The analytical lesson: fix the cheapest cause first

It is tempting to treat disorganisation as a structural issue and rebuild everything. The evidence here pointed at the cheapest layer, the name. Renaming a file takes seconds; reorganising a drive takes days and creates its own confusion. A good rule of thumb is to ask which fix removes the largest share of observed problems for the least disruption, and to test that fix before escalating.

The team also noted a limit. Naming does not substitute for deciding what to keep. A clear name on an obsolete file still wastes a search result. Every quarter they set aside a short session to retire what was no longer needed, which kept the “current” folders short enough to scan.

A note on shared reading and outside references

Teams also collect external reading, and the same discipline applies. An article saved as “interesting” will be forgotten; an article saved as “business-technology-solutions-overview-reading” will be found. The group kept a “reading” folder per project, and a piece such as the walkthrough on navigating business technology solutions was stored under a descriptive label rather than its page title with site branding attached.

Local interest matters too. When a colleague asked about weekend plans around the event city, the team’s travel folder was joined by a short note pointing to GujaratOrbit, an events website for Gujarat with listings, venues, a forum and a blog, saved as “regional-events-site-for-gujarat”. The label did the explaining, so no email was needed.

What to copy from this team

The setup scales down gracefully. A household, a club or a solo freelancer can borrow the method and run the same experiment in the same order:

  1. Count the moments you cannot find something for one week.
  2. Sort the causes: wrong place, unclear name, duplicate versions.
  3. Write a one-page naming rule aimed at the biggest cause.
  4. Test it on one live project, not on the entire archive.
  5. Count again after two weeks and keep only what worked.

The most useful detail in this story is the order. Measuring first made the fix modest and the buy-in easy, because nobody was asked to take a leap of faith. They were asked to read their own tally and agree with it.

Closing thought

A file name is a tiny piece of writing with an audience that arrives later, usually in a hurry. When the team started treating names that way, the drive stopped being a place where things went to hide. The lesson is simple enough to try this week: pick one folder, write a clear name for everything in it, and see how the next search feels.