Wow, what a long title. Today I’m going to talk about a magazine article.
In this article in CIO Magazine, McCauley talks about how you can improve your career while still in the same job. I’m sure a lot of you have had that feeling when you’re stuck in your current position, at least for the short term. Alas, no amount of hard work is going to get you promoted twice a week, so how do you keep yourself on edge while sitting in that same job?
One way is developmental assignments. Basically, you take on responsibilities that challenge you, and expose you to not only new experiences, but new skills and risks. Like any venture, there will be differing levels of risk involved in each individual opportunity. Here are some examples:
- Go to your boss and ask to look after the team’s cheque account for a month. You’ll be exposed to dealing with processes you may never have seen before. Perhaps you’ll have more sympathy for the poor bugger who has to reconcile the account at the end of the month. Most importantly, you’ll learn about financial control and develop your skills, and your boss will hopefully notice that you are eager and trustworthy.
- Low risk: learn a new personal skills, such as a reflective listening technique, and practice it on your co-workers. Even if you stuff it up completely, there’s almost no downside! But it is still a case of you going a little outside your regular comfort zone, and gaining new skills
- High risk: volunteer to champion a new IT (information technology) program. Now that’s high risk. You’ll learn about project management, training, budgeting and, most likely, dealing with the sht hitting the fan. There’s a significant risk of failure, which would reflect badly on you professionally. However, the potential upside is far greater than the lower-risk example above.
There’s a couple of general templates for developmental assignments, which will work in most industries. Firstly, do something you haven’t done before, and learn what it takes to do it well. Usually there is a job in your area that nobody wants to do. Some industries have cleaning the deep fryer in the kitchen, other industries have the really menial bits of data entry, or the nasty clients that the company should be sued for putting you near! While the task in question doesn’t necessarily have to be a bad job, sometimes bad jobs provide particular opportunities.
For example, if nobody likes filing, then perhaps you can take on the filing job for a week, learn how to do it efficiently, and identify improvements. Perhaps you’ll write a set of instructions that allows a newcomer to perform the job efficiently and gain satisfaction from their speed. Or even better, perhaps you’ll improve the filing system or work out how to do away with the need for filing.
But as I said, it doesn’t have to be a bad job. Perhaps you could take a temporary assignment to the team across the floor (it helps if you’re in a large organisation with an open-plan office). When you learn to do their job well, you gain what your resume will refer to as “cross-functional experience”. Depending on the dynamics inside your organisation, you might discover new synergies between the teams.
The two main benefits I see in developmental assignments are: achievements, such as improving processes, which your peers and superiors will remember and hopefully reward you for; and new skills, which you can add to your arsenal for when it comes time to apply for that next promotion.
Article reference: C McCauley, ‘Developmental assignments: five tips for making progressing in your career while staying put’, CIO Magazine, <http://www.cio.com/career/boost/column.html?ID=29114>