A colleague keeps all their files in a single folder and says 'I never lose anything — the search function always finds what I need.' What is the critical flaw in this strategy?
ASearch functions use excessive CPU and slow down the computer
BThe operating system cannot index files that aren't in organized folders
CSearch works fine for personal use, but the system breaks down when sharing files, backing up selectively, or reconstructing file relationships after data loss
DFiles stored in a single folder are more vulnerable to corruption
Search-based retrieval works until it doesn't: when you need to share a project's files with a colleague (who needs a coherent folder, not a search query), when you need to back up only one category of files, or when you're restoring from backup and need to understand what goes where. File organization is not about retrieval speed — it's about making the system legible to other people and your future self under adverse conditions.
Question 2 Multiple Choice
Why is '2024-03-15_tax-return-federal.pdf' a better filename than 'tax return final.pdf'?
AIt avoids using spaces, which can cause errors in some systems and scripts
BThe ISO date format at the start causes files to sort chronologically automatically in any file browser, and the content is identifiable without opening the file
CLonger filenames are indexed faster by the operating system
DThe hyphen separator prevents accidental overwriting of files with the same name
Both factors matter, but the key insight is the ISO date (YYYY-MM-DD): because file browsers sort filenames alphabetically, a date at the start means chronological sorting is automatic. '2024' comes before '2025'; '2024-01' before '2024-03' — no manual sorting needed. The descriptive name ('tax-return-federal') means you don't need to open the file to know what it contains. Together these properties make the filename do useful work even in a folder with dozens of similar documents.
Question 3 True / False
File organization exists entirely for human benefit — the operating system can retrieve any file regardless of where it sits in the folder hierarchy.
TTrue
FFalse
Answer: True
This is a key insight: the operating system tracks every file's physical location on disk and can find any file through search regardless of its folder location. The folder hierarchy does nothing for the computer — it exists so that humans can navigate, share, back up, and make sense of their files without running a search every time. Understanding this clarifies why 'I can find it with search' doesn't constitute a real organizational system — it outsources human decision-making to a tool that may not always be available.
Question 4 True / False
Keeping frequently-used files on your Desktop is a reasonable long-term file organization strategy because it keeps them immediately accessible.
TTrue
FFalse
Answer: False
The Desktop as permanent storage creates the same problem as any undifferentiated pile: files accumulate without hierarchy or naming convention, making the Desktop increasingly unusable over time. Each file placed on the Desktop without filing is a deferred decision that compounds. Good practice is to file immediately and use the Desktop only as a temporary staging area. Accessibility doesn't require Desktop storage — pinned folders, bookmarks, or 'Recent files' in apps provide fast access without the organizational cost.
Question 5 Short Answer
What makes a file name 'good,' and why does this matter more in a folder with many files than in a folder with only a few?
Think about your answer, then reveal below.
Model answer: A good file name identifies the content without opening the file, includes a date in ISO format (YYYY-MM-DD) for automatic chronological sorting, uses consistent structure across similar files, and avoids spaces in favor of hyphens or underscores. It matters more in crowded folders because scanning dozens of undifferentiated names ('document1', 'final', 'v2_revised') requires opening each file to identify it — whereas consistent descriptive names let you locate what you need at a glance. Consistency across a naming convention also enables pattern-based searches and batch operations.
The cost of a bad filename is low when a folder has three files and high when it has three hundred. Naming conventions become infrastructure: the investment in consistent names pays dividends every time you or anyone else needs to find, share, or back up a specific category of files.