01 Mar A fan of HR, but please nix the tower of babble!
I just read an interesting and enlightening article in a recent issue of Workforce Management (on Workforce.com). Called “Kill the HR Speak,” the article is about the confusing terms that Human Resources departments use to try to get their point across.
I’m a big fan of HR. They are a strategic partner in today’s world of work, where qualified candidates are hard to find and keeping high-potential employees is a challenge, and that’s without generational challenges thrown into the mix!
HR departments have a tough job, and their partnership with the business is vital to the ultimate success of the company.
But please, enough with the following:
• The HR babble.
• The made-up words to follow flavor-of-the-month fads.
• Cute, “creative” code names for secret projects.
Communication is the name of the game, so let’s try to speak the same language.
More meeting matters
A good friend and colleague just got back from a VERY frustrating meeting. It wasn’t the subject matter that frustrated her. Rather it was the behavior of the attendees and the person who called the meeting that made her crazy. Here’s why:
• People in the meeting were constantly looking at their blackberries — rather than paying attention.
• Several brought their laptops to catch up on e-mail while pretending to be engaged in the meeting subject matter.
• A few cell phones rang (perhaps I need to post a lesson on turning phones off, or at least setting them on vibrate!)
• The presenter didn’t know how to set up his PC to project his slides on the screen, so time was wasted getting the meeting started.
• Then, the presenter forgot his power cord, so his PC went dead in mid-meeting.
Our lives are busy and you could consider our time very precious. Don’t waste it with poor meeting planning and even worse meeting etiquette.
I’ve been doing some research for a panel I’m moderating in a few weeks at an IT gathering. The subject is — you guessed it — the talent shortage.
Some of the IT statistics I’ve found are a bit scary (if you’re an IT manager) and could be considered encouraging if you’re looking for IT work or if you’re a student.
So if you’re a potential employee I have some advice:
• Keep your skills current and take personal responsibility for learning new things.
• Specialize, if possible. The higher-end network analysts, architects, and systems analysts are what many employers are seeking.
• Study business and management. I’m finding that most employers want a well-rounded IT professional who understands the business, can communicate well with internal customers, and has management potential.
Does anyone have more to add to this advice?
Is there a correct answer to this conundrum?
You’re sick – sneezing, blowing, coughing — you know the drill. You’d like nothing better than to spend the day in bed watching daytime TV, but you’ve got important stuff to do at work. Should you:
• Stay home, rest and get well soon?
• Go to work, be a martyr, and infect everyone else?
The answer for your individual situation might depend on your boss or your company culture. But think carefully about whether or not demonstrating your never-ending loyalty by coming in sick makes up for infecting your co-workers.
What do you think?
Other columns by Melanie Holmes
• Melanie Holmes: Telecommuting: It takes discipline to work from home
• Melanie Holmes: Can’t resist the temptation of more “Celebrity” lessons
• Melanie Holmes: So many business meetings, so little time
• Melanie Holmes: Career dos and don’ts: Do your homework on the job search
• Melanie Holmes: On wimpy handshakes and other business etiquette pet peeves
• Melanie Holmes: She’s baaack! Avoiding the etiquette pitfalls of Omarosa
Holmes began her career with Manpower 26 years ago as a temporary employee. In 2005, at the age of 55, she earned an MBA from Northwestern University’s Kellogg School of Management.
This article previously appeared on the Manpower Web site and was reprinted with its permission.
The opinions expressed herein or statements made in the above column are solely those of the author, and do not necessarily reflect the views of Wisconsin Technology Network, LLC.
WTN accepts no legal liability or responsibility for any claims made or opinions expressed herein.