[BossingAround]

Same here. I like doing things nobody wants to do, especially when I'm new in the team.

The problem I've identified is that you're then the go-to person for the task you did in the beginning.

Example: You need to figure out how to deploy X. This is poorly documented and nobody knows how to do it.

Action: You read the code, understand what needs to be done, deploy it. Then, you document it. Finally, you create fairly basic but working automation for future deployment.

Result: Every time there's a need for redeploy, even when the code/procedure hasn't changed, you're the person the team immediately asks to do it. After all, you've automated it, shouldn't take too long, right?

[mdpye]

It happens at first. But point to the docs you wrote. Politely, but firmly, every time. People actually prefer being empowered to do it themselves, so they will pick it up, it just not our default when we're unsure.

[Too]

Except redeploying is something that always must be done last minute in a hurry because the last version deployed has a bug that will explode any moment and launch-demo is approaching, so managements blood hounds are pushing for someone who really knows how to do it to make sure it's done swift and proper!

15 minutes earlier corporate sent out an email about their values and how important knowledge sharing is! Right after deployment is done the work on documenting or automating the process is put at the bottom of the backlog since it's highly unlikely we have to do this in a such a rush again!

Make sure you have some kind of handover agreement in writing that you can point to when this happens. It sucks to be the "i told you so" guy but in situations like this you really need to protect your own back and as you say be very firm on not doing the job next time.

[tonyedgecombe]

I used to be quite happy to do all the dirty jobs that needed doing until I had an epiphany and realised I wasn't getting any credit for this. In fact it seemed to be doing my career some harm.

I stopped and refused any work that wasn't directly linked to bringing money in. Within a couple of years my salary doubled.

[kache_]

Pair with someone else and have them do it, and be explicit about your intention to share the knowledge.

[pilchard123]

Never become the guy who can fix the printer.