← Back to book home

Field Notes: How I Made Keto Stick

1. Day Zero: Food Diary Reality Check

I didn't start with macros or ketone strips. I started with a food-diary app and logged everything for two weeks. Then I looked for the biggest repeat in my day, the item that showed up most often, because I suspected the 80/20 rule applied here: remove the biggest repeat, get the biggest early impact. Seeing the logs in one place stripped away any ambiguity, this wasn't "a few treats," it was a conveyor belt of sneaky glucose spikes.

The diary gave me two wins: it showed my actual baseline, and it became the comparison point once I switched to keto-friendly meals. Without that baseline it's impossible to tell whether fatigue is diet-related or just lifestyle noise.

Why the diary mattered more than motivation

Before I logged properly, I had the usual fuzzy story people tell themselves: my diet was "not that bad," the treats were occasional, the coffees barely counted, and the rough afternoons were probably just stress. The diary demolished that story in about three days. Once every snack, drink, and convenience extra had a timestamp, the pattern stopped being negotiable. I was not dealing with rare indulgences. I was dealing with repeated, normalised carb hits spread across the whole day.

That honesty was useful because it turned keto into an engineering problem instead of a self-esteem problem. I did not need a more inspiring identity. I needed a clearer measurement system. Logging gave me that. It also made the later wins easier to trust, because when energy improved or cravings dropped, I had something concrete to compare against instead of relying on vibes.

What I was looking for in those first two weeks

That last category matters. A lot of the problem foods did not look dramatic on their own. They looked small, sensible, and easy to justify. But once the log showed them side by side, the cumulative effect was obvious. The diary did not just show what I ate. It showed how often I repeated the same mistake.

What counted as an honest log

I found out pretty quickly that a food diary is only useful if it is mildly annoying. If the log feels too flattering, it is probably incomplete. So I counted the little things that are easy to blur out of memory: the second coffee, the handful of nuts that turned into two handfuls, the dressing, the snack grabbed while standing in the kitchen, the "healthy" bar bought because lunch got delayed. Those details were not noise. They were the whole point.

That honesty changed the mood of the exercise. I was no longer trying to produce a respectable-looking meal journal. I was trying to catch the exact points where convenience overruled intention. Once those moments were visible, they stopped feeling random. I could see that the rough patches in the day were usually preceded by something predictable: too little protein, a liquid carb hit, or a long gap followed by whatever was easiest to grab.

The first useful pattern is usually boring

I think people expect a food diary to reveal one dramatic villain, but often the first real insight is much duller than that. It is not "sugar is bad" in the abstract. It is "I keep repeating the same three easy carbs because they fit my schedule." That is useful because boring patterns are fixable. If one pastry caused the whole issue, you would just stop buying the pastry. The real job is noticing the routine that keeps recreating the same outcome.

For me, that meant the diary was already doing its job before I changed a single meal. It had turned the problem from a vague feeling into a shortlist. Once the shortlist existed, the next move was not to overhaul my whole identity. It was to remove the most frequent item and see whether the rest of the day got quieter.

How I turned two weeks of logging into an actual plan

A diary only becomes useful once you review it with a slightly ruthless eye. I was not looking for the most sinful food or the meal that made me feel the worst. I was looking for the easiest point of leverage. Which item showed up often enough that removing it would quiet the whole system a bit? Which situations kept producing the same bad choice? Once I framed it that way, the log stopped being a guilt scrapbook and became a shortlist.

The practical review was very simple. I scanned for repeat items, but I also scanned for repeat contexts. Late morning coffee runs. Mid-afternoon convenience snacks. The gap between finishing work and figuring out dinner. Those contexts mattered because they explained why certain foods kept returning. A plan based only on food names is incomplete. A plan based on food names plus recurring situations is much easier to execute.

That review step stopped me from making a fake-clean plan built around foods I rarely ate anyway. It kept the focus on the habits that were doing the most damage while pretending to be normal.

What the baseline exposed about "normal" eating

One thing I found genuinely useful was noticing how many foods had become invisible through repetition. Not because they were tiny, and not because they were harmless, but because they were familiar. A biscuit with coffee, a cereal bar on the run, a second milky drink in the afternoon, a bit of fruit because it sounded responsible. None of those choices felt dramatic enough to trigger concern in isolation. The diary made clear that isolation was the wrong lens.

Once the entries stacked up, the pattern looked less like random indulgence and more like a conveyor belt of socially approved carbs. That mattered because it changed where the work was. I did not need to hunt down rare excess. I needed to interrupt the ordinary things that were adding up quietly. In practice, that is much better news, because ordinary habits are easier to redesign than occasional blowouts.

I think that is why day zero matters so much. It is not just about gathering data. It is about getting your own defaults to stop wearing camouflage. Once the repeated carbs are visible, the first chapter of the plan writes itself.

Day zero is about observation, not heroics

I think this is where a lot of diet attempts go sideways. People feel disgusted by the baseline, then try to fix everything in one burst of enthusiasm. That usually produces a short run of perfection followed by rebound chaos. The better move is to treat day zero like reconnaissance. Get the data first. Find the biggest repeat. Make one high-leverage cut. Then watch what changes.

That slower start felt almost too boring, but it set up the whole book. The food diary gave me a map. Once I had that, the next step was obvious: deal with the repeat offender that kept showing up over and over, which turned out to be lattes.