The One-Variable-at-a-Time Feedback Loop

Troubleshooting Is Iterative, Not a Single Move

Adjusting approach based on feedback and results treats the actual output as evidence rather than a verdict. The loop has three steps:

1. Read the result against the intended outcome and name the specific gap.
2. Change one variable -- the instruction, an example, the context provided, the task breakdown, or the model.
3. Re-run and compare to confirm the change helped; keep it or revert.

Why One Variable at a Time

Changing a single variable per iteration is what makes the fix diagnosable. If five things change between the weak output and the next attempt -- a new instruction, a new example, a different model, more context, and a different task breakdown -- there is no way to attribute the quality change (better or worse) to any one of them. The next attempt becomes a fresh guess rather than a confirmed improvement.

Turning Lessons Into Standards

Over several tasks, patterns emerge: a certain kind of ask always needs a worked example, a certain report always benefits from a fresh chat rather than a long thread, a certain format only lands with an explicit schema. The payoff of disciplined iteration is folding those recurring lessons into standard prompts and Project instructions, so the next similar task starts from the improved baseline instead of repeating the same diagnosis from scratch.

Common exam traps

• Changing many variables at once to save time -- this feels efficient but destroys the ability to isolate what actually caused an improvement or a regression.
• Ignoring the feedback the output itself provides. A weak output usually points at its own gap (missing detail, wrong format, stale context); reacting to that signal is faster than guessing at an unrelated fix.