Recovery Signal Quality: 3 Coach Checks Before Changing Food, Training, or Waiting
When fatigue shows up, the next move is not always more food or less work. In coaching logs and voice examples, the useful question is whether the recovery signal is clear enough to justify action.
Recovery Signal Quality: 3 Coach Checks Before Changing Food, Training, or Waiting
When fatigue shows up, the next move is not always more food or less work. In coaching logs and voice examples, the useful question is whether the recovery signal is clear enough to justify action.
A 2 mg retatrutide dose produced no appetite in one coach log and was followed by more fatigue than normal; in the same exchange, the coach flagged a pause or dose reduction if food intake was about to rise. The mechanism is simple: appetite suppression can reduce intake before the body has settled into the new load. That makes recovery signal quality the decision point, not just the number on the scale. If fatigue is paired with muted appetite, the next change is usually food, training, or patience in that order, and the right order depends on which signal is actually clean.
The problem: bad recovery signals create bad coaching changes
AI coaching systems love to turn every check-in into a tidy recommendation. But recovery rarely arrives as a single metric. Hunger, sleep, pump, performance, mood, soreness, and blood glucose can all move in different directions. The coach’s job is not to reward the loudest signal. It is to decide whether the signal is trustworthy enough to act on.
That matters because the wrong intervention can add noise. If an athlete feels flat because appetite is suppressed, pushing training harder can deepen the problem. If blood sugar is unstable after a large carb day, adding more food may be the wrong first move. And if fatigue is just the cost of a recent stimulus, changing three variables at once makes the next check-in nearly useless.
Justin Harris’ own coaching examples repeatedly point to this logic: look for the mechanism, identify the bottleneck, and change one thing at a time.
Food first when the bottleneck is intake
In the Rory Lazowski log, retatrutide at 2 mg produced a dramatic appetite drop and more fatigue than usual. That combination matters because recovery can’t improve if intake is quietly shrinking. If a client is supposed to be in a growth phase, appetite suppression is not a minor side note; it is the mechanism that can turn a planned surplus into an accidental deficit.
That is why the coach did not romanticize the “helpful in gaining” idea. He said he was holding judgment until there was more data, and in the meantime he preferred to lean out while it was easy. That is a practical coaching move: if the compound lowers appetite and the athlete is already reporting fatigue, the first question is whether the problem is insufficient fuel rather than insufficient discipline.
TroponinIQ take: if intake is the constraint, the cleanest intervention is nutrition. Increase food, reduce an appetite-suppressing lever, or both. Do not rewrite the training plan before you know the athlete can actually eat to support it.
Training next when performance says the dose is wrong
Another log shows a client whose high-day insulin sensitivity improved so much that the same insulin dose caused a noticeable blood sugar dip. He did not overeat; he simply had to bring meals closer together and planned to reduce the dose on the next high day. That is a useful recovery example because it shows how a seemingly small performance-related change can reveal a real shift in tolerance.
The implication for training is straightforward. When performance markers fall in a way that lines up with a recent change in fueling, insulin handling, or overall load, the next step is not to wait forever and hope. It is to identify whether the current work is now too expensive.
But the order still matters. If the blood sugar issue is caused by the nutrition setup around the high day, then training is not the first variable to touch. Fix the fuel pattern first, then evaluate whether the training dose still matches what the athlete can recover from. In practice, that means:
- if appetite is down, address food before training;
- if glucose handling or meal timing changed, fix the carb/insulin setup before assuming the program is too hard;
- if the athlete is eating well and still underperforming, then the training dose deserves scrutiny.
AI can help here if it is disciplined enough to separate cause from coincidence. A check-in that says “tired” is not enough. A check-in that says “tired, eating less, and appetite is gone” points somewhere. A check-in that says “tired, eating well, stable appetite, and performance has slid for two weeks” points somewhere else.
Patience when the signal is just late
The most common coaching mistake is to make the athlete pay for transient noise. A rough week is not automatically overreaching. A low-motivation day is not automatically under-recovery. A noisy sleep report is not automatically a deload.
This is where the “recover signal quality” idea earns its keep. If the athlete is within a known transition — post-show rebound, prep, diet break, or a new food load — the signal is often delayed. The body needs time to normalize appetite, digestion, and substrate handling. Justin’s off-season comments about teaching the body to digest and assimilate a massive amount of clean food fit that model: the goal is not just to add calories, but to make high intake tolerable enough that later phases work better.
That means patience is not passive. It is a decision to preserve signal purity. If you change food, training, and supplements all at once, you may get an immediate change, but you will not know what caused it. If the athlete is not crashing and the trend is still ambiguous, hold steady long enough to see the real pattern.
A simple decision tree for coaches
When recovery looks off, ask three questions in order:
1) Is intake the bottleneck?
If appetite is blunted, food quality is fine, and fatigue is rising, nutrition comes first. Don’t ask the program to solve an intake problem.
2) Is training now too expensive?
If intake is stable and the athlete still cannot recover output, assess whether the current workload is the wrong size for the current phase.
3) Is this just too early to call?
If the athlete recently changed food, insulin timing, bodyweight, or a compound that alters appetite, wait for a clean signal before making a second change.
That order matters because it preserves interpretability. Every unnecessary adjustment makes the next week harder to read.
What AI should do here, and what it should not do
AI is useful when it summarizes trends without pretending every trend is causal. It can notice that appetite fell, fatigue rose, and meal timing shifted. It can flag that a high-day insulin dose now behaves differently. It can surface when the athlete’s data looks more like a nutrition problem than a training problem.
What it should not do is over-automate the decision. If the signal is muddy, the right answer may be to wait. If the appetite signal is clear, the right answer may be to feed. If the workload is clearly mis-sized, the right answer may be to back off. The tool should help the coach rank those options, not blur them together.
The practical lesson is boring and useful: recovery is a signal-quality problem before it is a programming problem. Clean signals tell you whether the next move is nutrition, training, or patience. Dirty signals just create expensive confidence.
Sources Used
raw/_consumed/2026-05-31/kahunas-export/2026-05-31-w13-18m/clients/rory_lazowski___members-c5balaovjbdoeefqmfuqdhh2tbpmfdu16lnf0tnrtmw.jsonraw/_consumed/2026-05-31/kahunas-export/2026-05-31-w13-18m/transcripts/rory_lazowski___members-c5balaovjbdoeefqmfuqdhh2tbpmfdu16lnf0tnrtmw.mdraw/_consumed/2026-05-31/kahunas-export/2026-05-31-w19-24m/clients/rory_lazowski___members-c5balaovjbdoeefqmfuqdhh2tbpmfdu16lnf0tnrtmw.jsonmodules/03-knowledge/kahunas-coaching-deep-nutrition.mdmodules/08-voice/kahunas-coaching-deep-voice.mdraw/Justin_TT1.txt