Recovery Signal Quality: The 2-Question Coach Check

Recovery Signal Quality: The 2-Question Coach Check

When fatigue is the signal, the next move is not always more food or less training. The better question is whether the recovery readout is clean enough to justify a change.

Justin Harris called a 2 mg retatrutide trial “definitely lowering my appetite” and noted he had been “a bit more fatigued than normal too,” then suggested pausing or reducing the dose if food intake was about to rise. The mechanism is simple enough: appetite suppression can pull down intake faster than the body can adapt, and fatigue is often the first noisy signal that the mismatch is becoming real. That creates a testable coaching rule: when recovery gets worse after an intervention, do not assume the fix is always nutrition or training—first ask whether the signal is clean enough to change anything at all.

Recovery is not a vibe; it is a decision gate

AI fitness coaching is getting better at summarizing check-ins, but most systems still fail the same practical test: can they tell the coach what to do next when recovery gets fuzzy? If an athlete reports worse energy, more hunger, worse pumps, flatter training, or lower tolerance for usual work, the next move is not automatic. The next move depends on whether the change is actually producing a clear signal or just more background noise.

That distinction matters because recovery is not one thing. It is a bundle of signals: appetite, fatigue, blood glucose stability, training performance, and the athlete’s ability to execute the plan without drifting. The wrong AI summary can turn that bundle into a single bland label like “low recovery,” which is almost useless. The better output is narrower: what changed, how soon, and whether the new pattern points to more food, less training, or patience.

Justin’s guidance across the KB is consistent on this point. He does not treat every bad check-in as a reason to immediately change the plan. He watches for mechanism and timing. When appetite drops hard on retatrutide, fatigue follows. When insulin sensitivity improves enough that a normal dose starts pulling blood sugar lower than expected, the immediate issue is not “push harder,” it is dose adjustment and meal timing. When food volume, digestion, and adherence are the real limiting factors, he leans toward solving the bottleneck before blaming the program.

The cleanest signal usually wins

A practical recovery framework starts by ranking the signal quality.

1. Objective performance trend: Are loads, reps, bar speed, or session completion actually worsening?
2. Physiological change with timing: Did appetite, blood sugar response, or fatigue shift right after a known change?
3. Execution quality: Is the athlete missing meals, forcing food, or compensating in ways that blur the picture?
4. Context: Is this a stable hard block, a rebound phase, a high day, or prep stress?

The more of those boxes you can check, the more confident you should be about changing something. If only one box is checked—especially if it is the athlete’s mood about the week—patience becomes a valid intervention.

That sounds obvious, but most coaching tech still gets it wrong. A lot of AI check-ins are built to detect distress, not causality. They can flag that someone is tired. They are much worse at deciding whether the tiredness is coming from underfueling, excessive training density, poor digestion, or simply the first week of a new manipulation that needs time.

When the fix is nutrition

Justin’s off-season nutrition stance is blunt: teach the body to digest and assimilate a massive amount of clean food. His logic is not mystical. If someone can consistently process more food, they have more room for growth and better support for future contest prep. In other words, nutrition solves the recovery problem when the limiting factor is intake capacity, not a broken training plan.

The same logic shows up in the fruit discussion from the nutrition module. The point is not that banana vs. blueberries is magic. The point is that most outcomes come from nailing macros, and small food-source differences only matter when the bigger variables are already controlled. That is a useful recovery lesson too: if an athlete’s fatigue is clearly linked to inadequate intake, the answer is often more or better-structured food, not a dramatic rewrite of training.

In the Rory Lazowski exchange, Justin’s reaction to retatrutide is especially useful for coaches. Appetite suppression was strong. Fatigue was up. His response was not “this is always bad” or “this is always useful.” He said he was not sure he liked forcing appetite lower, and if food was about to increase, he’d consider a pause or dose reduction. That is a clean example of nutrition-first decision-making: if appetite suppression starts competing with growth, the tool stops being a recovery aid and becomes a bottleneck.

When the fix is training

Training changes are justified when the issue is workload mismatch rather than fueling mismatch. If an athlete is eating adequately but still accumulating fatigue, the first suspect is often too much density, too much frequency, too much failure work, or too much total stress for the current phase.

Justin’s coaching style in the KB rarely treats fatigue as a reason to panic. It is a reason to identify the bottleneck. If the athlete can eat, recover between sessions, and still cannot maintain performance, the smarter move is to adjust training stress before adding more food just to prop up an excessive workload.

This is where AI can be genuinely useful if it is disciplined. Instead of saying “recovery low,” it should say something like: “Performance is declining across two sessions, food adherence is stable, appetite is unchanged, and the last training increase was seven days ago. Nutrition is not the obvious first fix.” That kind of output doesn’t make decisions for the coach; it narrows the causal field.

When the fix is patience

Patience is not passive. It is a decision not to confuse adaptation lag with failure.

If a change is recent and the signal is mixed, the safest move is often to hold steady long enough to see whether the pattern stabilizes. That matters in both directions. An intervention can temporarily worsen fatigue while still serving the longer-term plan. It can also feel “good” immediately while quietly making the next block worse.

The Rory retatrutide note is a good example. Justin sees a possible advantage in leaning out while appetite is low, but he also says he wants more data before deciding what the gaining context looks like. That is the right standard. If the athlete’s body composition is improving and the fatigue is tolerable, you may not need to chase every sensation with an immediate intervention. But if fatigue keeps climbing and intake keeps falling, patience stops being prudent and starts being avoidant.

What coaches should ask before changing anything

Use these three questions in order:

• Did the signal change after a specific intervention? If yes, name the intervention.
• Is the signal strong enough to trust? If appetite, fatigue, performance, and adherence all point the same way, confidence rises.
• Which lever matches the mechanism? Intake problem means nutrition. Workload problem means training. Unclear timing means patience.

That order matters because most bad AI coaching lives in the opposite direction: it starts with a recommendation and works backward. Good coaching starts with signal quality.

If the athlete is more fatigued but still eating well and training performance is holding, you probably do not need to rewrite the program. If appetite collapses and fatigue rises after a suppression tool, the nutrition lever is probably the first one to touch. If performance decays without a clear intake issue, training stress deserves a look before food gets pushed higher. And if the data are thin, the best move is often to wait and collect a cleaner week.

Recovery is not a single score. It is a set of clues. The coach’s job is to decide which clue is real enough to act on.

Sources Used

• raw/Justin_TT1.txt
• raw/_consumed/2026-05-31/kahunas-export/2026-05-31-w13-18m/clients/rory_lazowski___members-c5balaovjbdoeefqmfuqdhh2tbpmfdu16lnf0tnrtmw.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