For the first four months of losing weight, I owned a metal kitchen scale and used it like a religion. Chicken thighs, oatmeal, almond butter, all weighed to the gram before it touched my plate, then typed into a food log by hand. It worked great — for about four days at a time. Then I’d leave the scale at my in-laws’ house, or order a burrito bowl I had no way to weigh, and the whole log would just stop. Not slow down. Stop, for a week or more, until guilt built up enough to start again.
I went back and actually counted this once I had the data: in those first four months I logged something on roughly 60% of days. Every gap correlated almost perfectly with a stall on the scale. It wasn’t that the food was wrong on the days I didn’t log — it’s that not logging meant I stopped noticing portion creep, stopped catching the extra handful of trail mix, and drifted right back to old habits within 48 hours of falling off the tracking wagon.
The fix wasn’t more discipline. It was fewer steps.
The thing that actually turned it around was embarrassingly simple: I stopped weighing food and started photographing it. Point the phone at the plate, snap it, get a calorie and macro estimate back in a few seconds. No scale to carry, no menu math, no guessing how many tablespoons of dressing are hiding in a salad. This is the exact reason I built photo logging as the default way to track in ZeroToHero (zerotoherofit.com) instead of bolting it on as a side feature — because the gram-accurate version of tracking was the version I kept quitting.
Why “close enough, every day” beats “exact, some days”
A photo estimate isn’t as precise as a scale. On a bad photo — bad lighting, a dish where the sauce is hiding under the rice — the estimate can be off by 10 to 15%. I used to think that margin of error would wreck my results. It didn’t, because weight loss isn’t decided by any single meal being exactly right. It’s decided by the trend across weeks and months, and a slightly-off number that gets logged every single day builds a far more honest trend than a perfect number that only shows up 60% of the time. The gap between the two methods isn’t accuracy. It’s whether you actually do it.
What changed, in actual numbers
Since I switched to photo logging as my default, I’ve logged 132 of the last 140 days — a little over 94%, up from that original 60%. My weight has come down steadily from 232 to 208 in that stretch, with noticeably fewer of the two- and three-week stalls that used to follow every missed week of logging. The stalls didn’t disappear because my metabolism changed. They disappeared because the data stopped having holes in it.
The practical difference shows up most at restaurants. A Chipotle bowl used to mean guessing at cups of rice and ounces of chicken, or just not logging it at all. Now it’s a ten-second photo before the first bite, and I’m on to eating. Same at my mother-in-law’s table, same on a plane, same at 9pm standing over the kitchen counter eating cereal I don’t want to think too hard about.
If you’ve bounced off food tracking more than once, my honest guess is it wasn’t a willpower problem. It was a friction problem — too many steps between deciding to log something and it actually being logged, especially anywhere outside your own kitchen. The scale wasn’t making me more accurate in any way that mattered. It was just giving me more places to quit.