Field notes
Building a protocol system you'll actually maintain
Most tracking setups collapse in week three. Here's how to design one that survives contact with real life — and real travel, refills, and busy weeks.
The hardest part of running any protocol isn't the first week. It's the forty-third day, when the novelty is gone, you're traveling, and your routine no longer reminds you of anything. Systems that depend on willpower lose. Systems that depend on structure win.
Start from the log, not the goal#
A good tracking system is a record first and a planner second. If the record is effortless to keep, everything downstream — reminders, inventory, trends — has something accurate to work from. If logging is friction, the data rots, and rotten data is worse than none.
Separate the three jobs#
Most abandoned setups try to do everything in one note. Pull them apart:
- Schedule — what's planned and when. This drives reminders.
- Inventory — what you physically have, and when it expires.
- Signal — how you're feeling and what you're measuring over time.
Each job has a different rhythm. Schedules change weekly. Inventory changes at refill. Signal accumulates slowly and only becomes useful in hindsight.
Make future-you the user#
The point of a record isn't today — it's the version of you reviewing a quarter from now. Write entries that will still make sense without the context you have in your head right now. Consistent labels, consistent units, consistent timing.
That's the whole game: lower the cost of an entry, raise the value of the history, and let the system carry the memory so you don't have to.
Share
Related
01