File naming: the smallest skill with the longest payoff

Every classroom with laptops accumulates the same sediment: Untitled(7).doc, asdfgh.png, my project FINAL final REAL.doc. Each is a tiny loan against the future — retrievable today by recency, irretrievable in June by any means. Naming is the rare skill that is trivial to perform, compounds for decades, and is almost never explicitly taught; it takes one lesson and a term of habit-holding.

The principle: a name is a message to your future self

The reframe that makes naming teachable rather than nagging: the file's name is the retrieval cue you're allowed to design (both retrieval tools run on it — browsing scans names, search matches them). The question at save-time is never "what is this?" (you know — that's the trap) but "what will June-me type or look for?" Future-self reasoning is a genuinely useful cognitive move children can learn young — this is its lowest-stakes training ground, and it's metacognition wearing overalls.

The child-sized rules

1. Say what's in it, findably: dragon-report beats my work; the test is whether a classmate could guess the contents from the name alone.
2. Words you'd search for — the name should contain the fragment future-you would type. (science won't find the volcano project among forty science files; volcano will.)
3. No mystery abbreviations — drgnrpt saves four keystrokes now and costs the file later.
4. Dates that sort: where dates matter, year-first (2026-07-sports-day) makes names sort themselves — a genuinely delightful trick to demonstrate live, and a first meeting with the idea that format choices have consequences.
5. Versions with names, not adjectives: v1, v2, v3 beats the final-FINAL-real death spiral — and naming the spiral for children (they've all seen it) is the fun way in. This is proto-version-control: the concept that revisions are a sequence, which real tooling will formalize for them years later.
6. The rename is always available — a badly named file isn't a mistake, it's a rename waiting (the explorer skills make repair cheap).

What the evidence doesn't say

• It doesn't support naming bureaucracy — mandated codes and prefixes children don't understand teach compliance, not retrieval design; the rules above are principles with reasons, not a scheme.
• It doesn't claim naming replaces filing or search — it's the bridge that makes both work.
• It doesn't come with effect sizes — it comes with every teacher's June testimony, offered as exactly that.

In the classroom

1. Teach the future-self frame in one lesson, then hold the habit at every save — the fifteen-second "what will June-you look for?" prompt is the whole maintenance cost.
2. Demo the sorting-dates trick live — format-affects-behavior is a deep idea at trivial cost.
3. Run a rename rescue: hand children a folder of Untitled(1..9) and have them open-rename-refile — teaches naming, renaming, and empathy for their own past selves in one activity.
4. Model your own names on the projector — children copy what the shared drive shows them daily.

How Wiz Kids applies this

Naming has its own File Forest lesson ("true names" in the fiction — things that are well-named can always be found again), rename is a first-class taught operation, and the search lessons close the loop by making the payoff felt: the buried file is findable because someone named it findably — and the fiction says so out loud.

References

• Bergman, O., & Whittaker, S. (2016). The Science of Managing Our Digital Stuff. MIT Press — retrieval cues and naming in personal archives.
• The PIM navigation/search literature (summarized here) — names as the substrate both retrieval routes share.

© Glu IO Pty. Ltd. — Wiz Kids (wiz.kids). Link freely; republication requires permission — see terms. Found an error in our reading of the research? We correct fast: tell any teacher piloting Wiz Kids.