Created by the First Role Skills Editorial Desk. This lesson uses a fictional workplace scenario and links to primary product documentation where the interface or feature matters.
Start with the work
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.
Avoid rework
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
The method
Complete it in six controlled steps
- 01
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.
- 02
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.
- 03
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.
- 04
Assign ownership
Name the person or role responsible for each shared area. Personal drives should not be the only home of team records.
- 05
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.
- 06
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.
See the difference
Before and after
Project X/Stuff/Old/Final/FINAL2_really-final.docx
Projects/Orion/03_Approved/2026-08-03_Orion_Launch-Brief_V03.pdf
Original practice
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.
Explain your decisions
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.
Quality gate
Check your own work
- Retrieval questions defined
- Hierarchy is shallow
- Pattern documented
- Owner assigned
- Permissions reviewed