

A Two-Minute Note Title Formula That Improves Search Later. Bad titles hide good notes. A two-minute formula makes search boringly reliable.
Weak title: Notes sync
Search hit: maybe the right note, maybe three meetings named sync. Future-you sees a dateless blob. Colleagues duplicate the doc because nobody trusts search. The title failed as a user interface.
Weak titles cluster in shared drives as Roadmap sync (1)(2) final FINAL. Everyone pays the tax in duplicate work and chat archaeology.
Rename policy: if you create a duplicate because search failed, rename the original before copying. Copying is a symptom; vague titles are the disease.
When three docs share a keyword, schedule a ten-minute rename sprint that day—collision tax compounds every week you wait.
Strong title: Draft contractor onboarding FAQ — legal review by 4/15
Verb, object, context, optional deadline. Future-you knows the job without opening the note. Teammates converge on one doc instead of spawning copies.
Spend up to two minutes at capture close. Renaming fifty notes in a quarterly panic is the tax for skipping the formula when the note was born.
Optional deadline in title helps when work is time-bound—skip it for evergreen ref notes titled as questions.
Weak title: 2026-04-08
Dates as titles are filenames for robots. You have hundreds of days; you do not have hundreds of distinct memories tied to date-only strings. Ban titles that are only dates, sync, or meeting.
Strong title: Why did March pilot slip? — vendor API limits
Question plus anchor fact. Retrieval matches how you ask the question in chat three weeks later. Titles meet search boxes first; tags carry status, not hidden verbs.
The two-minute formula at capture close
Before saving:
- Verb or question — what is this note for?
- Object — what thing does it touch?
- Context — team, customer segment, quarter
Pair with one tag for status—not a second hiding place for the verb. Do not hide the verb in a tag while the title stays poetic.
Priya sets a phone timer when saving a new note. Timer fires → title must include verb or question plus object. Two minutes at birth beats fifty-note rename panics during quarterly cleanup.
Title work fits waiting-for-build cracks; rename marathons do not fit deep work blocks. Small friction at capture saves team-wide search tax later.
Repair sprint: fifteen old notes in one sitting
Rename fifteen vague notes, then try keyword search tomorrow morning. Failed finds mean titles still vague—or the note should have been a task. Move pure tasks out of notes; titles cannot fix work that belongs on a calendar.
Shared docs should use the same formula so team search converges. Measurable signal: duplicate docs created per month—should fall after rename sprint.
A culture of Q3 roadmap decisions — open questions only beats a folder of filename theater.
Teams that adopt the formula report fewer duplicate docs—not because people become virtuous, because search starts working. When search works, copying feels stupid.
Individual adoption works without policy: rename your notes first, then model in shared docs when you create them. Culture follows retrieval wins, not lectures.
Weak title audit: search sync and meeting in your vault monthly—rename hits before they duplicate.
Side-by-side rename: four notes in ten minutes
Meeting 3/8 → Decide API v2 scope — platform leads 3/8
Ideas → Candidate standup formats — no decision yet
Sam stuff → Waiting on Sam — vendor MSA redlines
Notes → delete or merge; title Notes is a confession of avoidance.
Renaming four notes takes ten minutes. Finding them tomorrow takes seconds. That asymmetry is the whole argument.
Do the repair sprint on notes you searched for this month—not random spring cleaning. Pain-guided renaming sticks.
Team rollout: one shared doc, one rule
Priya’s team adopted one line in their handbook: No new shared doc without verb + object in the title. Not enforced by bot—enforced by rename in PR comments. Duplicate doc count dropped in six weeks because search started returning the first doc.
Rollout took one standup explanation and three renames as examples. No workshop. Titles are culture expressed in search boxes.
Measurable signal for teams: duplicate filenames containing final or v2 per month. Should trend down after the rule sticks.
Repair sprint tip: rename the fifteen notes you failed to find this month—not random spring cleaning. Pain-guided renaming sticks because retrieval success is immediate feedback.
Context collision — when two notes share an object
Two notes titled Onboarding FAQ and Contractor onboarding FAQ collide in search. Priya adds context: Draft contractor onboarding FAQ — legal review by 4/15 versus Employee onboarding checklist — HR version. Same object family, different audiences—context prevents merge confusion.
When teammates ask which doc is canonical, the title should answer without opening. If it cannot, rename before replying in thread.
Collision test: search the object keyword; if more than one hit, differentiate titles the same day—not next quarter.
Priya posts rename diffs in chat when fixing collisions—canonical doc is X, archived Y. One message prevents a third duplicate from well-meaning teammates.
Titles are retrieval engineering, not poetry
Pay the two minutes upfront. Search is how teams share memory; titles are the UI.
Gentle enforcement in shared spaces beats a wiki no one reads. Correct a vague title when you link to someone else’s doc—it is kindness, not pedantry.
Two minutes at birth beats a quarterly rename panic. Search is shared memory; titles are its UI.
Vague titles tax every teammate who searches. Your two minutes at capture is a team gift, not personal fussiness.
Search boxes do not read minds. Titles must speak the words you will type when stressed—that is the whole formula.
Rename collisions the day you notice them—waiting a quarter triples duplicate docs and meeting confusion.
Questions as titles beat topics for ref notes; verbs as titles beat nouns for work notes.
Two minutes at capture is cheaper than a quarterly rename panic—pay upfront.
Titles are how future-you searches; write for that person, not for tidy folders.