October 11, 2011, 8:17 AM —
Sometimes the things we want to do the least are exactly the things we need to do to get promoted. The issue is that there are many times in our life, both personal and professional, that personal advancement requires personal growth.
In some cases, personal growth is in the areas we love to pursue. For example, if you love playing tennis and want to become a nationally rated player, you have to practice, and maybe take lessons, to improve your game. If you love playing tennis, then personal growth in this area is welcomed and anticipated. As a counter example, if getting promoted requires learning to successfully manage projects, but delegating work to others is difficult for you, you have an issue. It doesn’t mean you can’t do it, it just means that you must step outside your comfort zone to acquire the skill.
As techies, or for that matter as human beings, there are a number of areas, both personal and professional, that we may not naturally be comfortable doing. Some of these items that follow, may be on your list.
Learning technologies you don’t currently know: This one may sound funny for a techie, but it’s very common. Maybe you are a COBOL programmer and would like to update your skills, but the needed body of knowledge seems too large to undertake.
Giving a presentation: For many people, the thought of standing up in front of the room and giving a presentation, particularly if their boss is listening, is petrifying, and seems like a fate worse than death.
Leading a project: Leading a project requires taking risk, taking responsibly, delegating work to others, setting objectives, and meeting deadlines.
Writing documentation: Many software developers hate to write documentation. Programming environments don’t have spell checkers. Maybe English is your second language. Many programmers believe that if you can’t read and understand the source code, you shouldn’t be trying to modify the software; therefore, documentation within the code has no value. Maybe for some people these are nothing more than reasons to not write documentation, because they do not feel comfortable doing it.
Training users: Training users on how to use the software you have written may feel frustrating and/or scary. First, training is like giving a presentation and we already talked about that one. Second, what if the users don’t like the software you created? Then what?
Cross Training other programmers to do your job: This may just seem wrong. It’s your job, why should you teach someone else to do it? Additionally, you have too much work to do to spend the time.
Follow Eric on Google+
