Design a shared structure that makes current work easy to find without creating an endless maze of folders.
Created by the First Role Skills Editorial Team. This lesson uses a fictional workplace scenario and links to primary product documentation where the interface or feature matters.
A realistic scenario
A small project has files named FINAL, FINAL2, and latest-new. People store duplicates in personal folders and cannot tell which version was approved.
DeliverableA one-page folder map, a naming convention, and rules for ownership, permissions, and archiving.
Three beginner mistakes
- Creating deep folders for every possible future case
- Putting status words such as FINAL in filenames
- Giving edit access to everyone by default
Complete it in six controlled steps
Map how work is retrieved
List the questions people ask when searching: which project, document type, reporting period, owner, or approval state? Build around retrieval, not an organization chart.
Keep the hierarchy shallow
Use a small set of stable top-level folders and no more than two or three useful levels for routine work. A search-friendly name is often better than another folder.
Choose a naming pattern
Use a predictable order such as YYYY-MM-DD_Project_Document_V01. Define allowed separators, version format, and examples for drafts and approved copies.
Assign ownership
Name the person or role responsible for each shared area. Personal drives should not be the only home of team records.
Apply least-needed access
Use Viewer for reading, Commenter for feedback, and Editor only for people changing the file. Review inherited folder permissions before sharing links.
Test with retrieval tasks
Ask a new user to find three files and save a new version. Record confusion, simplify the map, then publish the rules beside the root folder.
Before and after
Before:
Project X/Stuff/Old/Final/FINAL2_really-final.docx
After:
Projects/Orion/03_Approved/2026-08-03_Orion_Launch-Brief_V03.pdf
Complete the exercise
Design a folder map for a fictional event project, then use the file-name builder for five document types. Give one collaborator Viewer access and explain why.
Use only fictional or fully anonymized data. Never upload an employer’s confidential information to a portfolio.
Turn the exercise into credible evidence
Create a single-page folder map and a naming-rules card with five examples. Add three retrieval tests such as ‘find the approved launch brief’ and record how many choices the user makes. Explain one folder you removed after testing and one permission you reduced from Editor to Viewer. This turns an arbitrary hierarchy into evidence that you considered retrieval speed, ownership, inheritance, least-needed access, and archiving.
Check your own work
- Retrieval questions defined
- Hierarchy is shallow
- Pattern documented
- Owner assigned
- Permissions reviewed
Primary reference: Google Drive Help: share files and understand access
Why this matters in your first job
New employees often inherit shared drives that grew without a plan. Knowing how to find, name and store files properly saves you time every day and protects you from embarrassing mistakes, such as sending an old version to a client. Offering to tidy a small corner of a messy drive, with your manager’s agreement, is also a practical way to add value early.
Common questions
Should I reorganize the team drive on my own? No. Propose changes first, start with a small area and agree the structure with the people who use it. Moving files can break links and confuse colleagues.
What about version numbers in filenames? Many cloud tools keep version history automatically, so words like “FINAL” are unnecessary. If you must use versions, use a consistent format such as v01, v02 and keep the current file clearly marked.
Where do personal notes belong? In your own approved workspace, not in shared team folders. Our guide to taking notes in your first weeks suggests a system, and our article on remote work tools explains cloud storage habits.