A Log Per Person

"Every question mark adds to our cognitive workload, distracting our attention from the task at hand." — Steve Krug, Don't Make Me Think

Two kids and the same reading log. Two cars and their fuel. Two people in one house need the same thing tracked, and the obvious build is wrong. The obvious build is one logger with a menu at the front, tap it, pick the person, then log the thing. It feels efficient, one Shortcut instead of two. And it just added a decision to every single capture, which is the exact disease this whole module exists to cure. A menu you answer forty times a week is a form wearing a trench coat.

The right build is duplication. The same log shape, copied once per person, each copy already knowing who it belongs to. Two tiles instead of one tile plus a question. The tap itself carries the answer.

Same shape, different name on the door

Everything about the per-person logger is the pattern you already built in The Ten-Second Log: a value, a timestamp, an append to a running note or file. The only change is the destination and the label. One copy appends to one person's log. The other appends to the other's. Nothing asks anything.

Build the first one however the thing you are tracking demands, a chore done, a kid's reading minutes, a practice session, a dose given, then duplicate it exactly the way Preset-Amount Buttons duplicates sizes. Open the copy, change the destination note, rename the tile. Total cost per additional person: about a minute.

Then arrange the tiles by person, not by task, in the widget stack from Swipe, Don't Hunt. In the real moment, you know who the log is about before you touch the phone, so the person is the natural first split. One swipe lands on their column, one tap logs it.

Why the menu version quietly fails

The one-logger-with-a-menu version fails on the worst possible entry, and every log has one. Here is the sharp version: at 2am, holding a thermometer, you tap the tile and answer the who question wrong exactly once. One mislabeled entry is worth negative ten right ones, because now the whole log needs an audit before anyone can trust it. The per-person tile cannot make that mistake. It writes where it writes.

Separate logs also keep the downstream clean. When a week of one kid's reading lines gets pasted into a review, or handed to an assistant that reads it (see Shortcuts That Feed AI), nothing about anyone else rides along. One log per person is one story per person, and every tool that reads the log inherits that tidiness for free.

Keep the household out of the shared copy

One rule if you ever share a Shortcut you built, and it is a hard one. Build the copy you share clean: a generic note name, a generic tile name, no real names, nothing about who lives in your house or what you track for them. The pattern travels, the specifics do not. Your own tiles can say whatever helps your thumb find them. The version that leaves your phone says Person A.

That is the whole piece, and the smallness is the point. A log per person is not a new system, it is the same three-part logger wearing name tags, which is exactly how this module compounds: one shape, learned once, duplicated at every seam of your actual life. When the same move shows up a third time, for a place or a project instead of a person, you will not need an article about it. You will just duplicate the tile.

Put this to work. The Shortcut files are a free download, just an email.