Rod Masney believes it's a key part of his management role to encourage his employees to really disengage from their in high-pressure IT jobs -- to take a week or two at the beach or that long-awaited European tour.

Only problem, the global director of IT infrastructure at Owens-Illinois doesn't follow his own advice much.

"I believe people should strive for work/life balance, but I'm not very balanced," admits Masney, who is also the immediate past chairperson of the Americas' SAP User Group . "My PC bag is like my purse; it goes everywhere I go, and so does my BlackBerry. They're my safety blankets."

He's not alone. IT employees rank high among professionals most likely to contact the office when they're on vacation, second only to salespeople. According to the 2008 Vacation Survey conducted by CareerBuilder.com, of nearly 7,000 U.S. workers polled, 37% of those identified as IT employees plan to contact the office while on vacation, compared with 50% of sales professionals and just 15% of retail workers.

And some 19% of IT workers said their employer expects them to work or check voice mail and e-mail during their time off. (See Guilty pleasure for more statistics.)

Other tech professionals never even make it that far. Data from NFI Research in Madbury, N.H., found that 75% of IT workers have four weeks or more of vacation coming to them, but that only 39% of that group takes their allotted time.

Tips for taking off

Clearly, when the goal is to take time off without checking into the office, tech employees have the deck stacked against them (see Why IT stays home). Nevertheless, according to IT pros and human resource experts, it is possible to stay in the loop and recharge during your precious time off. Just follow this formula:

Do the prep work before you leave -- let people know in advance the dates you'll be away and finish up key deliverables before you go.

Surround yourself with good people who can reliably step up to the plate and solve problems when they occur. Encourage your staff to "backstop" one another so expertise is interchangeable and the department doesn't rely solely on one individual to get any one task done.

Establish escalation and problem-solving policies and document them well so there's clarity on what to do and who to call in the event of an emergency -- say, a network outage or any other type of system crash.

For more enterprise computing news, visit Computerworld. Story copyright Computerworld, Inc.