High-Day Timing and the 1 IU Trap

High-Day Timing and the 1 IU Trap

When insulin sensitivity changes, the win is smaller, earlier adjustments—not more reactive tinkering.

The clearest pattern in the Joe Webb log is simple: after a high day, the same insulin dose that worked the week before started dipping blood sugar enough to force meal 2 about 30 minutes sooner, and a 1 IU reduction only partly solved it. The mechanism is changing insulin sensitivity, not some mysterious “bad day” swing. The coaching thesis is blunt: adjust nutrition and insulin timing only after you have a repeatable signal, then change one variable at a time; otherwise you end up chasing noise and creating your own instability.

That matters because the actual problem here was not overeating, under-eating, or a dramatic failure of the plan. Joe reported that he did not overeat for the day; he just had to bring meals closer together. That is a timing issue first, not a macro crisis. And Justin’s response was equally plain: there was no need to panic, only to recognize that bodyweight, blood sugar, and meal spacing had shifted enough to warrant a measured correction.

This is where a lot of coaches and athletes overdo it. They see one changed variable — a lower glucose reading, a flatter look, a hungrier client, a worse pump — and start adjusting three other things on the same day. But the evidence in this log points the other way. The useful move was not “fix everything immediately.” It was to note the new response, trim the dose slightly, and keep watching the next high day.

That approach fits Justin’s broader nutrition philosophy in the deep nutrition notes: the biggest returns come from nailing macros and execution, while the last few percent lives in the details. In the fruit example, he makes the same underlying point in a different domain. On medium days and around training, there is flexibility; on high days, carb load and elevated insulin make the source less important because the bottleneck is overall execution and food volume. Translation: timing matters, but only after the foundation is stable. If the day is already structured well, the marginal gain from endlessly optimizing one meal source is small.

The practical coaching lesson is to separate three questions that people routinely mash together:

1. Did the body respond differently?
2. Was the response repeatable?
3. Does the change require a timing fix, a dose fix, or both?

Joe’s message gave a clean example. The same dose as the prior week caused a noticeable dip in blood sugar with meal 1, which forced meal 2 earlier than planned. He reduced the dose by 1 IU and was fine with meal 3, but the same reduced dose as the third shot still repeated the issue. That is enough signal to justify a further reduction on the next high day. It is not enough to justify rewriting the whole setup.

That distinction is where AI coaching systems can be genuinely useful — or completely useless. A good system should detect the pattern, flag the repeatable deviation, and recommend a small next-step change. A bad one will overreact to the first data point, then over-correct when the next check-in looks different. In other words, the coach is not supposed to optimize every datapoint in real time. The coach is supposed to decide when the datapoint is worth acting on.

Justin’s reply to Rory’s retatrutide note shows the same restraint from another angle. Rory reported that 2 mg crushed appetite and made him more fatigued than normal, then wondered whether a pause or dose reduction made sense if food was going to be increased. Justin’s answer was not to cling to a pharmacology dogma or make a philosophical statement about whether appetite suppression is good or bad. He looked at the direction of the phase: if body comp work is moving toward adding food, then the appetite-suppressing tool should be reevaluated; if the plan is to lean out, you run with it while it is easy. That is timing logic again. Don’t lock in a change from the wrong phase of the plan.

For coaches, the mistake is usually one of sequence. They change the nutrition target before the trend is established, or they change the meal timing before they know whether the new insulin response is temporary, dose-related, or just a one-off. The better pattern is:

• observe the change on the same day and in the same meal slot,
• wait for a second similar exposure,
• adjust the smallest effective lever,
• then give the new setup enough time to show whether it actually solved the problem.

That’s not passive coaching. It’s disciplined coaching.

This also explains why “more frequent updates” is not automatically better. Faster check-ins can help if the client is actively missing the target, but they can also invite over-adjustment. Joe was already planning to check in the following Tuesday, and explicitly noted that changes made too close to the check-in would not have much time to take effect. That is exactly the point: if you change too soon, you lose the ability to tell whether the prior change worked. You have no read on cause and effect, just a pile of edits.

The stable version of nutrition adjustment timing is boring but powerful. Keep the meal structure intact long enough to see the response. If blood sugar is dipping earlier than expected, move the meals closer only as needed and lower the relevant dose incrementally. If appetite is getting crushed while calories are going up, don’t pretend the appetite tool is neutral — reassess it in the new phase. If the day already works, don’t go hunting for phantom improvements in fruit swaps or micro-optimizing every carb source.

A lot of AI coaching products sell the fantasy that more data automatically means better coaching. The evidence here says the opposite. More data only helps if the coach knows when to stop touching the system. The real skill is not recognizing every fluctuation. It is knowing which ones deserve a change and which ones deserve a note in the log.

That is the difference between coaching and chaos: make the change late enough to trust it, and small enough to read it.

Sources Used

• modules/03-knowledge/kahunas-coaching-deep-nutrition.md
• raw/_consumed/2026-05-31/kahunas-export/2026-05-31-w13-18m/transcripts/joe_webb___members-rksigkykimaxwmo_t4_e8nwvbtc2j0etleutkyysads.md
• raw/_consumed/2026-05-31/kahunas-export/2026-05-31-w13-18m/clients/rory_lazowski___members-c5balaovjbdoeefqmfuqdhh2tbpmfdu16lnf0tnrtmw.json