When I coach, I can often see the missing observation before the team can. They have been stuck for twenty minutes. One sentence would unlock the problem.
Giving the sentence feels efficient. The team resumes work, writes the solution, and may even remember the technique. The session appears saved.
But the hint changed the object being measured. We no longer know whether the team would have found the observation, how it would have escaped the dead end, or which teammate might have exposed the flaw. Immediate progress came at the price of diagnostic evidence.
Know what the session is for
A hint has different value in an instructional session, a targeted drill, and a contest simulation. During instruction, withholding a needed definition can waste time. During a simulation, supplying it can invalidate the exercise.
Before practice, decide what should remain unaided. If the target is implementation, reveal the main idea and protect time for coding. If the target is recognition, naming the technique defeats the session. If the target is team recovery, let the team experience being stuck long enough to reveal its recovery habits.
Without a target, coaches tend to optimize for motion. Motion is easy to see. Learning is harder.
Wait for useful evidence
Silence is uncomfortable, especially when the coach already knows the route. I watch for a distinction: is the team still producing new information, or is it repeating the same move?
Productive struggle changes the state of the problem. The team tests an example, revises a representation, proves a smaller claim, or rules out an approach. Unproductive struggle loops without a new question or observation.
The coach should usually wait through the first kind. The second kind may justify an intervention, but the intervention should target the loop rather than reveal the exit.
Use the smallest intervention
I think of hints as an escalation ladder:
- Ask the team to state what it knows and what remains uncertain.
- Ask for the smallest example that separates two beliefs.
- Point to the assumption or representation that deserves inspection.
- Reveal a partial structural fact.
- Give the central observation only when the purpose of the session now lies beyond it.
Move one rung at a time. After each intervention, return the work to the team. A chain of leading questions can encode the full solution while preserving the appearance of discovery.
Make the hint visible afterward
Teams often remember a hinted solution as one they nearly solved. Record the intervention. What did the team know before it? Which sentence changed the path? Could the team reconstruct why that sentence mattered?
Then assign a transfer problem where the same idea appears without the hint. The accepted solution from the first problem shows that the team could finish with support. The second problem tests whether the support became knowledge.
Repeated rescue is a curriculum signal. One hint may be appropriate. The same hint across a month is evidence that the practice plan needs to change.
If the team repeatedly needs help turning constraints into complexity, practice that decision directly. If it cannot abandon an attractive wrong approach, design short sets where the goal is early falsification. If one teammate always waits for the coach before voicing doubt, the problem may be team safety rather than algorithms.
A hint log does not need to be elaborate. Record the problem, the stuck state, the intervention, and the next exercise. Over time, the pattern is more informative than the count.
Measure coaching by future independence
The purpose of a hint is not to protect the completion rate of a practice session. It is to change what the team can do later.
A useful intervention should leave a residue: a question the team begins asking, a test it runs sooner, a representation it can now derive, or a recovery move it owns. If the same rescue remains necessary, the hint produced progress without transfer.
Coaches should help teams get unstuck. They should also preserve enough of the struggle to learn why the team was stuck. The right hint is the smallest one that restores productive work and makes itself less necessary next time.