2026-06-29
Coaching without giving answers: a feedback pattern that grows problem-solving
Give the answer and your report solves it now but can't think for themselves next time. A feedback pattern that grows problem-solving by prompting with questions, and how to practice it in the daily report.
The more you hand over answers, the less they think
Hand a stuck member the answer and the moment is solved fast. But repeat it and a dependence grows: 'if I'm stuck, I'll just ask.' Development looks like the long way around, yet letting the person think is ultimately the shortcut. Managers, too, easily keep handing over answers for the comfort of being relied on, so deciding in advance when to hold back helps you stay steady.
A growth mode that returns questions
Return questions, not answers: 'where did you get stuck?', 'what do you think caused it?', 'how will you change next time?' Have the person write the report's A (improvement) and next-day P, while the manager prompts thinking with questions. Keeping the person as the one who thinks is the foundation of problem-solving. The knack is not to throw many questions at once but to return one at a time and wait until the person puts an answer into words. Not rushing to fill silence also protects thinking time.
Add scaffolding only on stuck days
Push back every time and the person can break. Have them think for themselves as a rule, and add a hint as scaffolding only on the days they're truly stuck — that balance of burden and development is the knack of coaching you can sustain. Make the hint not the answer itself but only a direction to think in, such as 'try recalling the steps that worked in a similar situation,' so the sense of clearing it yourself remains.
Put growth into words weekly
In the weekly review, put into words the moment they thought it through and improved, and reflect it back. Once they realize 'last week I cleared that wall myself,' the success sticks and the will to think for themselves next time grows. Rereading the report records, you can notice that something they used to consult about, they now handle on their own. Conveying that difference concretely builds their confidence.
Common stumbles and how to avoid them
A common stumble is questions that sound like an interrogation. 'Why couldn't you do it?' easily sounds like blame, so rephrasing toward the next action, such as 'what would have let you move forward?', is easier to receive. Also, continuing to ask right up to a looming deadline can hurt the outcome. As a guide, for urgent matters show the answer first and organize the way of thinking together later in a review, using each approach as fits. In the review, having the person also describe why something worked, not only why it failed, makes it easier to reproduce next time.
A tool for a culture of improvement and fair evaluation that implements these ideas.