Tracking Too Many Habits at Once? Cut to Three Numbers
A log rarely gets heavy all at once. You start with one number, because one question was bothering you. It works, so you add a second. A month later somebody mentions a field you had not thought of and it seems cheap to include, since you are already opening the file. Nothing you added was unreasonable on the day you added it. Then one evening you are sitting with fifteen fields in front of you, filling them in at speed so you can be done, and you notice you have not thought about a single one of them.
That is the failure mode. Not laziness, not falling off the wagon. The log became the day's last chore, and a chore gets completed rather than considered. The numbers keep arriving and the attention that made them worth anything has quietly gone.
Why the count matters more than any single field
Each field looks cheap in isolation. Twenty seconds, a slider, a tick. The cost is not additive, though. It sits in three places that only show up once the list is long.
- The ritual gets a length. Once filling in the log takes four or five minutes, it needs a slot in the day, and slots get skipped when the day goes badly. Which is exactly when the data would have been most interesting.
- Filling in beats noticing. With three fields you think about your answers. With fifteen you are working down a form, and a form invites the fastest plausible number rather than the true one.
- Nothing gets read. Fifteen columns is a spreadsheet you have to sit down with. Three is something you can take in at a glance on a Sunday. A log you never review is a log that cannot pay you back.
The one question that prunes a list
Put every field you currently track on one page, one per line. Include the ones you have not filled in for weeks, and the ones the app collects automatically. Then, against each, answer a single question in writing:
What decision would this field ever change?
Not what it might reveal, not whether it is interesting. What you would actually do differently depending on its value. Write the decision as a sentence, in the form "if this runs low for two weeks, I will..." If you cannot finish that sentence, the field is a passenger.
Four common ways a field fails:
- No decision is attached. The most common case. You track it because it was in a template, or because a tracker offered it. It has never once altered a plan.
- The decision is already made. You track a field to confirm something you have already concluded and will not revisit. That is not measurement, it is reassurance, and it does not need a daily number.
- You cannot act inside the horizon. Some things move so slowly that a daily reading is noise and a monthly one would do. Weight is the classic example. Daily readings of a slow variable mostly measure yesterday's salt and water.
- The answer is recoverable elsewhere. If your phone, your bank, or your calendar already holds it, you are copying data by hand. Pull it when you review instead of logging it nightly.
Most people run this exercise and find two or three fields with a real decision behind them, a couple that could be monthly, and a long tail with nothing written next to them at all. That tail is the chore.
Why three
Three is not magic; it is what fits in the gap between deciding to log and being finished. Three fields can be filled in from memory, standing up, on a bad night. That matters more than precision, because the entries you lose are never randomly distributed. You lose the worst days and the busiest ones, which are the days that carry the most information.
If you want a shape that usually survives, take one number for how you felt, one for the input you most suspect drives it, and one sentence of plain text. The sentence is the field that makes the other two readable a year from now. A 4 with no context is a mark. A 4 next to "third night of the deadline, ate at my desk" is something you can learn from.
We make Yesterself, a journaling app, and it is built around that last field rather than the first two. Your evening writing comes back to you as a letter the next morning, drawn from your own archive, so the sentence about a hard week gets read rather than filed. Any line can also be postmarked to a future date, which is a natural home for "check whether the sleep field is still earning its place." It is not released yet, so there is nothing to download, only a waiting list.
Yesterself is the journal that writes back. Every morning it sends you a letter from your own past writing, and your reply becomes tomorrow's. End-to-end encrypted, no account, no email — your archive is yours to export, free, forever.
Join the waiting listRetiring a field without deleting the history
Here is where people undo their own work. They prune, feel the relief, and then tidy up by deleting the columns. Six months later they want to know what the winter looked like, and the answer is gone.
Retire, do not delete. In practice:
- Stop adding, keep everything already added. In a spreadsheet, leave the column and stop filling it. In an app, turn the field off rather than clearing its data, and check first that turning it off does not erase the entries. Some do.
- Date the retirement. Add a line to a plain notes file: the field, the date you stopped, and the reason in one sentence. Future you will otherwise read the gap as an outage and wonder what broke.
- Write the one-line verdict now. While you still remember, record what the field showed during its run, including "no pattern I could see." That sentence is worth more later than the raw column, and it is the only thing you will realistically reread.
- Export before you touch anything. Get a copy out as CSV or plain text and put it somewhere that is not the app. Pruning is the exact moment to find out whether your data is portable.
- Mark the gap deliberately. If you restart the field later, treat it as a second run with its own start date, rather than a continuation. Two honest stretches beat one line with an invisible hole in it.
None of this is about tidiness. It is about keeping the option to change your mind, which is the thing deletion takes away permanently.
Guarding the list afterward
Lists refill. Two rules keep this one from growing back to fifteen.
One in, one out. If a new field is worth tracking daily, name the one it replaces. Almost every time, the exercise of choosing a victim tells you the new field was not that interesting.
Run fields for a season, not forever. Some questions deserve four weeks of close attention and nothing after that. Decide the end date when you start it, and let the field expire on schedule instead of quietly becoming permanent.
And keep the review honest about what pruning is for. You are not tracking less because you care less. You are tracking less so that on the evening when everything is going wrong, the log is short enough that you still open it, and short enough that you actually look at what you wrote.
If any of the fields you are weighing relate to symptoms, mood, sleep, or anything else about your health, a log is documentation and not a diagnosis. Take those questions, and the decision about what to change, to a clinician who can see the whole picture.
Common questions
How many things should I track at once?
Three daily fields is a workable ceiling for most people, because three can be filled in from memory in under a minute. The real test is not the count but whether you still fill it in on a bad day.
What is the fastest way to decide which fields to cut?
Ask what decision each field would ever change, and what you would do differently depending on its value. A field with no decision attached to it is a field you are collecting out of habit.
Should I delete the old data for a field I stop tracking?
No. Stop adding to it and leave everything already recorded in place, with a dated note saying when you retired it and why. Deleted history cannot be reconstructed, and a frozen column costs nothing to keep.
What if I need a retired field again later?
Restart it as a new stretch rather than pretending the gap does not exist, and note the date you resumed. Reading the old run and the new run as two separate periods is more honest than treating them as one broken line.
Is it a failure if I miss days after pruning?
No. A missed day is a missing observation, not a broken record. Fill in today and carry on, and if you are missing most days even at three fields, the problem is the ritual rather than your discipline.