Mentoring is something I do quite often as part of leading a developer group, but I rarely do it consciously, it mostly just happens in 1on1s and code reviews. I notice many times that I’m not fully satisfied with the end results of a project, but kind of let it slide and settle on the produced results. I do give feedback etc. but if it’s still not right, I just go on.
Giving feedback is a form of mentorship but it’s not enough in many cases, and explicit 1on1 time on a specific project is required in order to bridge that gap. By that I mean really spending time and working on the project together. It might be that the persons task relevant maturity is just not there yet, and he needs clear and specific guidance and it could be that I’m looking at it the wrong way, anyway, time is needed to bridge that gap.
So, what I should do instead is to notice that this is the case and set aside time with that person, until I feel we reached a point where he can advance independently and produce high quality results. This needs to be time that is off the regular meeting cadence.
Beside improving the results of that specific task, it can also improve our relationship, build knowledge that the dev and myself will take to other tasks (without meeting again), and improve the dev satisfaction by hopefully feeling he is learning new stuff as well as being seen.