Sixty Days Later — The Photo-Logging Habit Update

Sixty days ago I wrote an article on this site called "Photo Logging: The Food Tracking Habit That Finally Stuck." At the time I was 67 days into a photo-based food tracking habit, after four previous failed attempts at tracking over six years on four different apps.

I am now 127 days in. I have not missed a day.

This is the sixty-day update I promised myself I would write, because the most useful thing about a habit-formation article is not the first-success post — it is the did-it-actually-last-a-few-more-months post.

The Short Answer

Yes, the habit held. That is the lead. If you read only this paragraph, you have the article.

The longer answer is more interesting, because what I actually expected at day 67 was that I would eventually drift, and the question was whether I would drift at day 80, day 100, or day 150. At day 127 I am not drifting. I am also not, at this point, consciously sustaining anything. The logging has moved from "a thing I am doing" to "a thing that happens" — which is the actual signal that a habit has formed.

What Changed Since the Original Article

Between day 67 and day 127, a few things shifted in ways I did not expect.

Adherence Stayed High

I expected adherence to decay. It did not. My per-meal logging rate over the 60-day period was 98.4% — only 11 meals out of roughly 700 were not logged, and all 11 were the same category of thing: I ate something at someone else's house and felt socially weird about taking a photo of the plate. I am not counting those against myself.

For comparison, my previous longest tracking attempt was MacroFactor at 24 days, where my logging rate by day 24 had dropped to roughly 60%. The contrast is not subtle.

The Magnesium Pattern Held

In the original article I mentioned that my rolling 30-day magnesium average was running at 71% of RDA. I tried to fix it. Sort of.

I added a small evening snack rotation of pumpkin seeds, dark chocolate, and almonds — foods I knew were dense in magnesium. My rolling 30-day average has come up to 83% of RDA, but it has not reached 100%. What the tracking surfaced is that my baseline diet is magnesium-poor at the level of the foods I choose, and no realistic amount of supplementation-adjacent snack foods closes the gap to RDA without a change in main-meal composition I have not made. I now know this. That would not have been visible without 127 days of logging.

Protein Stabilized

The biggest behavior change came from setting a flat protein target. In the original article I flagged that I was averaging 140 g protein on training days and 92 g on rest days. That gap was costing me recovery.

I set a flat daily target of 140 g regardless of training status. Sixty days later, my rest-day protein average is 138 g and my training-day average is 142 g. I am hitting 140+ g on 91% of days. The data made the problem visible; once visible, it was a mechanical fix (an extra protein shake or a larger dinner-protein portion on rest days). This is the strongest behavior change the habit has produced.

The Sunday-Wednesday Gap Narrowed, Sort Of

I also flagged a roughly 380-calorie gap between my Sunday intake and my Wednesday intake — the kind of weekly pattern that would quietly cost a pound a month if untracked.

Sixty days later, the gap is roughly 180 calories. I closed about half of it by shifting my Sunday breakfast from a higher-calorie weekend pattern (croissant and butter, three-egg omelet with cheese, large coffee with cream) to a protein-forward pattern (Greek yogurt with berries, two poached eggs on one piece of sourdough, black coffee). The remaining 180 calories are honest weekend-eating behaviors I do not want to change — a larger dinner with my partner, usually — and I have decided the answer is to accept the 180 rather than engineer it further. The data allowed me to decide where the line was, rather than drifting into a gap I did not know about.

What Did Not Change

I want to be careful here, because a sixty-day update article is very tempting to frame as a triumph narrative. It is not one.

My Weight Barely Moved

I am down about 4 pounds over the 60-day period, mostly in the first three weeks, flattening after that. The logging did not produce dramatic weight loss because dramatic weight loss was not my goal. I was not in a meaningful caloric deficit for most of the period — just slightly, on average, across the week.

This is the honest version of the "tracking works" story that most articles do not tell. Sustained tracking does not cause weight loss by itself. It creates a substrate that makes intentional weight management possible. Those are different claims. I only wanted the substrate. I got the substrate.

Some Days Are Still Ugly

My logs include a real entry, on a real day in late April, that was a large slice of birthday cake, a pint of beer, and nothing else between 6 PM and 11 PM. I logged it. I did not pretend it did not happen. I also did not adjust anything the next day to compensate. That is what sustained tracking looks like at day 107 — you log the birthday cake the same way you log the morning oatmeal, and you stop treating individual days as moral events.

I Still Do Not Look at the Calorie Total Most Days

This was true at day 67 and it is still true at day 127. I open the app, take the photo, confirm the entry, and close the app. I look at the weekly averages on Sundays. The daily total is not a number I interact with. Past-me would have assumed this was impossible — that anyone logging food every day must be staring at the totals. Present-me is surprised by how little the totals matter when the point of the habit is pattern data rather than daily score-keeping.

The Friction Point Still Holds

My median log time over the 60-day period, sampled from the app's own timing data, is 2.9 seconds per meal. My fastest logged meal was 1.4 seconds (a protein shake, already in a frequent-items list). My slowest was 7 seconds (a plate with seven different ingredients the AI needed a moment to resolve). Across an average 3-meal-plus-2-snack day, my total logging time is about 14 seconds.

This is not a small observation. The entire reason the habit survived past day 30 — the death zone for all my previous attempts — is that the friction cost is structurally too low to rationalize skipping. I cannot construct a plausible "I didn't have time to log" story when logging takes 14 seconds across a full day. The floor is low enough that my brain does not try.

What I Would Tell Someone Starting Today

If you are thinking about starting a food-tracking habit in May 2026 and you have failed at it before, the only piece of advice I would give you is this: the workflow is the entire variable.

Not the app you pick. Not the motivation you bring. Not the accountability buddy. Not the goal. The workflow. Specifically: how many seconds of your attention does a single meal log cost?

If the answer is more than 30 seconds per meal, you will eventually stop. Maybe not on day 14. Maybe on day 30. Maybe on day 90. But you will stop, because your life will eventually contain a day where the logging cost is not worth the perceived benefit, and that day will break the streak, and once the streak is broken you will not restart.

If the answer is under 10 seconds per meal, you probably will not stop. The cost is too small for your brain to bother producing a skip-rationalization for. At some point the habit stops being something you sustain and starts being something that happens.

That is where I am at day 127. I am not sustaining anything. It happens.

The Point of the Article

The original article was about how photo logging finally made food tracking stick for me. This update is about the fact that "stuck" is actually the right verb — the habit is not being held in place by willpower or novelty or discipline. It is running on the infrastructure of the workflow itself.

The broader principle, which applies well beyond food tracking: the habits that survive are not the ones you are most motivated to sustain. They are the ones whose friction cost is low enough that sustaining them stops being a decision you revisit every day.

For me, with food logging, the answer was a 3-second workflow. For you, with whatever habit you are trying to build, the answer might be different. What is the same is the principle: the habit will last exactly as long as it stays under your personal friction threshold, and no longer.

I will write another update at the 180-day mark, which lands sometime in early July. My prediction is that the habit will still be running. My fear is that by writing this update I have somehow made the streak into a self-conscious thing, and self-conscious things break in ways automatic things do not. We will see.

Last updated: May 2026.