A Google Doc per person works, until you can’t find anything.

When a doc-per-person stops working

A doc-per-person stops working the moment retrieval becomes the bottleneck, usually around the time each doc is long enough that you scroll instead of read. The notes are all still there; you just can’t get to the right one fast enough to use it in a 1:1 or a review.

Here’s the shape of the failure, and it’s well documented in how managers actually keep notes. You open a fresh Google Doc per report, drop in dated lines, and for a few weeks it’s perfect. Then the docs grow. By month six, the “@Maya running doc” is four pages, half the dates are missing, and the line you remember writing about the billing migration is somewhere in the middle. You stop trusting the doc, so you stop opening it, so you stop writing in it. The system quietly dies.

None of that is a Google Docs defect. It’s what happens when a free-form document is asked to be a structured, dated, per-person memory. A few specific failure modes show up again and again:

• No structure. A doc is a blank page. Every line is whatever you typed, with no enforced date, no person field, no topic. Consistency is on you, every single time.
• Retrieval degrades as it grows. Find-in-doc works on one doc. Across twelve people’s docs, finding “every time Sam covered on-call” means opening twelve files and searching each.
• Manual maintenance. One doc per person, named consistently, dated consistently, archived each year: you build and tend the whole filing system yourself.
• No per-person timeline or recall. A document has no concept of a person. There’s no “show me Maya, last quarter”, only scroll, skim, and hope.
• Easy to forget where you wrote it. Did the migration note go in Maya’s doc, the team standup doc, or a quick scratch doc? Six months later you can’t remember, and neither can a folder.

What changes with a per-person memory

The fix isn’t a better document. It’s a different model. Instead of choosing a file and a spot in it, you write one line and tag who and what it’s about. The notebook does the filing.

In Notivo you type a quick note and mark it with @person and #topic. That note files itself onto that person’s dated timeline automatically, with no document to pick, no date to remember to type, no folder to maintain. A few weeks of notes about Maya look like this, on their own:

• Feb 9: @Maya led the billing migration with zero downtime #delivery
• Mar 9: @Maya covered on-call for @Sam, handled it cleanly #reliability
• May 14: @Maya mentored the new hire until they could solo on-call #growth
• Sep 30: slow stretch for @Maya, scope kept shifting under her #blockers

When the quarterly review comes, you open Maya’s timeline and the whole arc is there, in order, with dates: no scrolling a four-page doc, no wondering which file. Because every note is also tagged by person and topic, “every time someone covered on-call” is a search, not a half-day of opening files. The same note about the March on-call shows up under both @Maya and @Sam, because you can mention more than one person in a line.

For the line that was getting lost in a long doc, the one you knew you wrote but couldn’t find, here’s the difference in shape. The DIY version drifts toward this by September:

# @Maya running doc
Feb 9: led billing migration, zero downtime
Mar 9: covered on-call for Sam, smooth
...
Sep 30: ...where did I write the migration note?

In Notivo there’s no “where did I write it”; the note lives on Maya’s timeline by date, and search finds it by topic. You can also ask the AI assistant, in plain language, “what did I write about Maya this quarter?” and it drafts a recap strictly from your own notes. It reads what you actually wrote, so it never invents anything, and it doesn’t train on your data. Use it to inform your own judgment. The call is still yours.