+1 I used to be very helpful, very capable even if something wasn't my area until I realized people were taking advantage. I sadly learned I had to sometimes play clueless. No, I'm not sure how to run xyz report, I think this may be the document or the underlying data structure, so sorry I wish I could help more. Oh, you don't gave access to do x, oh let's make sure you get the request in to John. Oh, I learned after people had me doing stuff they COULD do themselves but it was easier to ask me to do it, meanwhile I could work overtime every weekend and still not be done because I was the new person coming into an area that had the most issues. So bottom line, I will always share documentation, I will answer questions, but I will not do what you can do yourself or spend inordinate amounts of time helping if they don't seem inspired to help themselves and it can't be to the detriment of meeting my deadlines. |
|
+1 to above.
I think of pointing people to documentation, etc. as "teaching people how to fish" rather than "giving them a fish"--more efficient use of my time, and builds their problem-solving skills. I think it also depends on the group / organization--in some settings, the time spent on training / mentoring others is acknowledged and valued in various ways. In other settings, not so much. Regardless, it's a balancing act... |