The team below is invented, yet its troubles will sound familiar. Picture four volunteers who put together a monthly visitor guide for a coastal city: a writer, a photographer, a map maker and someone who handled bookings with local contacts. They all worked from one shared drive, and for the first year it worked well enough. By the second year it did not. Here is how their naming habits changed, step by step, and what any small team that produces guides, itineraries or event notes for visitors to Chennai can borrow from them.
The month everything went sideways
The turning point was a deadline week. The writer needed the final map for a walking route, the photographer needed to know which pictures had been approved, and the booking coordinator needed the latest list of confirmed contacts. Each of them asked the group chat. Each got three answers. The map maker had uploaded two files called route-map-final and route-map-final-v2. The photographer had a folder named approved and another named approved-new. The contact list existed in four places.
The guide went out a day late, and one walking route listed a stop that had been cut in the second version of the map. Nobody was angry. They were just embarrassed, and a little tired of searching.
The one-hour meeting that changed things
They set aside an hour on a weekend and asked a single question: what would a stranger need to see in a file name to know what it was? The answer, after some back-and-forth, turned out to be short. A name should say what kind of thing it is, which issue of the guide it belongs to, and what state it is in.
From that, they drew up a pattern written on one page and pinned to the top of the shared drive:
- Kind of item first: text, map, photo, contact-list, booking-note.
- Then the issue and subject: the month of the guide and a plain description of the content.
- Then the state: draft, approved or printed.
A map file became map-march-issue-harbour-walk-approved. A text file became text-march-issue-first-time-visitors-draft. None of the names needed explaining, and all of them sorted into sensible groups.
What the writer noticed first
The writer felt the benefit within days. Drafts used to be named after her working titles, which changed as the piece evolved. Now every draft carried the issue and a descriptive subject, so a piece that started as “ideas about the first day” and ended as a full primer kept a stable name. When she wrote about planning a first visit, drawing on pieces like this overview of planning a first trip to Chennai, she could place related notes beside the text file with matching names, and everything for that piece sat together.
She also stopped worrying about overwriting. Each time she sent a version to the group for comment, she saved it with the date and the word sent, and carried on in a fresh copy. When a reviewer said “I preferred the opening in the earlier draft”, she could open it in seconds.
What the photographer changed
The photographer’s folders were the messiest. Camera numbers, edited copies and rejects mingled. Under the new rules, only approved images went into a folder called photos-march-issue-approved, each renamed with a short description of what it showed: photo-march-issue-beach-promenade-morning. Rejects stayed in a separate folder, plainly named photos-march-issue-not-used.
The effect on the writer and layout person was immediate. They no longer had to ask what a picture showed or whether it was cleared for use. The name carried the answer. Pieces like a roundup of experiences for first-time visitors are the kind of content where good pictures matter, and being able to pull the right one in moments sped the whole layout stage.
The map maker’s quiet fix
The map maker adopted one extra rule: every map file carried a revision date and kept the older ones in a subfolder named maps-superseded. That ended the “final-v2” era. A glance at the main folder showed only current maps. If someone needed history, it was one click away.
It also solved a subtler problem. Because every map name included the walking route it covered, the team could reuse a route from a previous issue without wondering which of several similar files was the right base. They simply searched for the route name.
The booking coordinator and the contact list
For the coordinator, the big change was consolidating four copies of the contact list into one, named contact-list-local-partners-current, with a dated archive copy made at the end of each issue. Booking notes got names that began with the type and ended with the date and the status: booking-note-harbour-walk-guide-confirmed. Everyone else could tell at a glance which arrangements were firm and which were still pending.
The coordinator also added a plain-text read-me file at the top of the contacts folder, in two lines, explaining how the list was updated. It was a small gesture and the most cited in later retrospectives, because it meant a newcomer could join without a briefing call.
What they did about the old mess
They did not try to rename two years of files. They agreed on a cut-off: everything from the current issue onward followed the pattern; older material stayed untouched in a folder called archive-before-naming-rules. When someone needed an old file, they renamed it on the spot and moved it into the current structure. After six months the archive was rarely opened, and nobody missed the time not spent cleaning it.
Six months on: what the team reported
The group described the changes in their own words in a short review. They said the number of “where is that file?” messages dropped sharply, that new volunteers got productive faster, and that deadline weeks felt calmer. They did not claim any dramatic transformation; the guide was the same guide, with the same writer and the same city. It simply took less effort to produce, and the effort that was saved went back into the content.
One other change deserves mention: from then on the volunteers counted naming as editorial work in its own right. A file that cannot be named clearly often has an unclear purpose, and the discussion about the name sometimes led to a better decision about the content itself.
A look at how public sites do it
Teams who produce visitor material can pick up ideas from sites that organise lots of material for the public. GujaratOrbit is a Gujarat events site that lays out its event listings, venue pages, discussion forum and blog as separate areas, each title announcing what waits inside. The story team in this article, in effect, gave their drive the same treatment.
Lessons any small team can use
- Hold one short meeting to agree the pattern, and keep the result on one sheet of paper.
- Lead with the kind of item, then the subject, then the state.
- Replace words like “final” with a date and a status word.
- Keep one current copy of anything shared, and move older versions to a clearly named archive.
- Do not clean the past in one go; apply the rules from today and rename old files when you touch them.
The team’s story is fictional, and its numbers are not the point. The point is that a few plain words at the front of a file name can spare a group a surprising amount of friction. If your own drive feels like the one in the opening scene, an hour with your colleagues and a single page of rules might be all it takes to begin changing it.