3 ms·
Try the whole "teach them to fish" vs "give them a fish" approach. So give positive feedback for asking, show them how to find the answer online or in documenta
by ghufran_syed 4y ago
Try the whole "teach them to fish" vs "give them a fish" approach. So give positive feedback for asking, show them how to find the answer online or in documentation, and then over time, your first response to their question will become "ok, what have you tried so far?" and hold them accountable for following the (informational search) algorithm you showed them previously.
Some people have trouble turning your advice into a skill they perform routinely (partly because they don't take notes). So you can help them with that by asking them to make notes on what you are showing them, then getting them to send them to you for review.
And if the things really isn't online because it’s proprietary and it’s not explained in the documentation yet, then you get them to write the notes with the view to making that the documentation. So they take up your time on a task that helps them in the company, they pay it back with another task that helps others by reducing the chances that someone else gets stuck in future
- jjice 4y agoThis is what I try to do, and I believe it works out well. Sometimes I can tell that someone is a bit annoyed that I'm not showing them just how to add CSRF protection to a page, but also why we do it and how it works, but I do believe that showing them how to do it and why is where leaning comes in and trumps raw repetition/memorization.