Weekly Check-In Triage: The 30-Minute Insulin Rule

Weekly Check-In Triage: The 30-Minute Insulin Rule

Decision quality beats volume when the week’s data are noisy, small, and easy to overreact to.

Justin Harris’s coaching note in the Joe Webb check-in is blunt: after a high day, the same insulin dose that had been fine the week before produced a noticeable blood sugar dip, and the fix was simple—reduce the dose and move the next meal up about 30 minutes. That’s a mechanism problem, not a motivation problem: shifting insulin sensitivity changes the timing of the meal, so the right response is a small timing-and-dose correction, not a wholesale rewrite. The falsifiable thesis is straightforward: better weekly check-ins are triage tools for rate-of-change, not scorecards for perfection, and the highest-value coach decision is the one that changes the fewest variables while fixing the actual constraint.

The check-in is not the program

A lot of coaching noise comes from treating the weekly check-in like a referendum on the whole plan. It usually isn’t. The useful check-in is narrower: what changed, what moved first, and what deserves an immediate adjustment versus a note for later?

In the Joe Webb thread, the signal was specific. On a high day, the same insulin dose as the prior week dipped blood sugar more than expected. It wasn’t a full hypo, but it was enough to require meal 2 to come 30 minutes sooner. Joe reduced the dose by 1 IU and still saw the same pattern on another shot, then planned to reduce further next time. Justin’s response was not to panic or redesign the whole day; it was to accept the data and keep the meal cadence aligned with the response.

That is good triage. The coach is not trying to prove foresight. The coach is trying to keep the athlete inside a workable window while the trend is still small.

Decision quality starts with variable control

The practical value of the weekly check-in is that it tells you which variable is actually driving the problem. If one thing changes—same high day, same meal structure, same general routine—and the response shifts, then the intervention should stay local.

That matters because coaches are tempted to bundle problems. Blood sugar dipped? Add food, change carbs, alter the day, tweak the dose, and maybe change the schedule too. But when a small dose change plus a 30-minute meal adjustment resolves the issue, broad changes just add noise. The athlete loses the ability to tell whether the problem was dose, meal timing, appetite, or the day’s total load.

This is the decision-quality part of check-in triage: preserve signal. If you can fix the issue with one small correction, you get a cleaner read on the next week. If you change six things, next week’s outcome belongs to nobody.

Weekly triage is about sequencing, not drama

The best check-ins follow a sequence:

1. Identify the immediate constraint.
2. Change the smallest variable that addresses it.
3. Observe the next response.
4. Escalate only if the same problem persists.

That sequence shows up again in the Rory Lazowski exchange about retatrutide. Justin’s first reaction to a 2 mg trial was not to romanticize the appetite suppression. He noted that he was trying it himself for first-hand experience, but he also said he didn’t love the idea of forcing appetite lower. Then he anchored the next decision to the body comp context: with the athlete already leaning out, run with it while it’s easy, because that would also create a better example of how it behaves when gaining. Again, the principle is triage. Get the immediate context right before making the larger judgment.

That is the same logic that should govern weekly check-ins. If the week reveals a new appetite change, a new fatigue pattern, or a new blood sugar response, don’t leap to a philosophical debate about the tool. First ask: what’s the least disruptive correction that keeps the athlete functioning?

Appetite, fatigue, and the cost of over-adjusting

The Rory thread also shows why check-in triage has to be skeptical of “nice to have” effects. The athlete reported that the retatrutide felt dramatically appetite-suppressing, almost unlike prior semaglutide experience, but also mentioned more fatigue than normal. That’s exactly the kind of mixed response where a coach can get sloppy.

A weak check-in says: wow, appetite is down, so it must be working. A better check-in says: appetite is down, fatigue is up, and the next decision depends on where calories need to go over the coming phase. If more food is about to be added, the dose may need to be paused or reduced. If the athlete is in a phase where leaner is the goal, maybe the current state is useful. But the point is not to celebrate the signal. The point is to decide what to do with it.

That’s the broader lesson for AI-assisted coaching too. AI is not valuable because it produces more notes. It’s valuable when it helps a coach classify the note: urgent, watch, or ignore.

Why weekly check-ins fail: they confuse observation with action

Many coaches are already collecting enough information. The failure is not data scarcity. It’s triage quality.

A good weekly check-in should sort into three bins:

• Immediate action: something is clearly affecting execution now.
• Short-horizon watch: the trend matters, but a single response is too small to overreact to.
• No change: the issue is interesting but not decision-relevant.

The Joe Webb insulin example lands in the first bin. The effect was repeatable enough across shots that meal timing and dose were adjusted. The Rory retatrutide example sits between the first and second bins depending on phase: appetite suppression was immediate, but the actual decision depends on whether the upcoming plan needs more intake or less.

That sorting discipline matters because it prevents the classic coach error: acting like every deviation is a crisis. It isn’t. Some deviations are just the cost of living inside a changing protocol.

What coaches should ask on check-in day

If the goal is decision quality, the check-in questions should be boring and specific:

• What changed first?
• What stayed the same?
• Did the issue repeat, or was it a one-off?
• Can the fix be local?
• Will the adjustment preserve next week’s signal?

Those questions force the coach to stay close to the mechanism. In the Joe case, the mechanism was improved insulin sensitivity on a high day, producing a stronger-than-expected glucose drop. The fix was local: reduce dose, bring the following meal closer. In the Rory case, the mechanism was appetite suppression with fatigue; the fix depended on phase, but the immediate read was that appetite-lowering may be useful when leaning out and potentially annoying when trying to push intake.

That is the level of precision weekly check-ins need. Not a mood report. Not a spreadsheet trophy. A decision.

The coach’s job is to reduce uncertainty, not eliminate it

A lot of bad coaching comes from pretending uncertainty is failure. It isn’t. The best coaches in the KB are comfortable making a small call with incomplete information if that call keeps the athlete moving and preserves the next data point.

That’s why the “30-minute rule” matters as a coaching habit even beyond insulin. It represents a broader discipline: when a variable shifts, respond in the smallest way that solves the current bottleneck. Then reassess. The athlete does not need a grand theory every week. The athlete needs the next adjustment to be correct enough that the following week is interpretable.

In practice, that means AI coaching should be used less like a content generator and more like a triage assistant. It should help surface the one thing that changed, the one action that matters, and the one variable that should be left alone.

If your weekly check-in produces ten comments and no decision, it failed. If it produces one small correction that keeps the plan readable, it worked.

Sources Used

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