HP To Cut Back On Telecommuting
Makarand writes "Hewlett-Packard, the company that began
making flexible work arrangements for its employees starting in 1967, is cutting back on telecommuting arrangements
for its IT employees. By August, almost all of HP's IT employees will have to work in one of 25 designated offices during most of the week. Those who don't wish to make this change will be out of work without severance pay. While other companies nationwide are pushing more employees to work from home to cut office costs, HP believes bringing its information-technology employees together in the office will make them swifter and smarter and allow them to be more effective."
That's what really pissed me off when I was in the biz. I would ask to work from home and I was ALWAYS told that, "No, we need you here to do your work."
So, I would commute in every fucking day. Then, you guessed it, my job (and others'), were sent over seas to India. Yep, they needed their IT workers there all right!
What's interesting is their non-IT employees can continue to telecommute. I would guess that the IT folks being forced to relocate and physi-commute aren't too happy about that.
DRM 'manages access' in the same way that a prison 'manages freedom'
Before I get hammered this is the right thing to do. Flexibility is great and being able to work for a few hours on Friday from home when taking comp hours for the rest of the day is efficient and great. Or working from home when you are waiting for the guy of the telecom. Great that's good for the firm and the worker.
But telecommuting for most of the time is stupid and neither good for worker nor firm.
1) My problem is distraction, when I have to finish something I can work from home, that's ok. But if nothing is pressing on me hard I'm simply not disciplined enough. For this a work environment is great to keep focussed.
2) Teamwork. I'm working in an international firm and it is working by and large, but Messanging, calls, emails only get you so far. Being able to walk 5 meters and chat someone up is completely different. It is very complicated to coordinate work over three continents and too many timezones.
3) Teamwork Part 2, how will you develop something like Teamspirit and good cooperation if you have only seen most of your team a couple of times?
4) line between work and home. I do work enough, when I'm coming home and can say so it's over let's go drink a beer or watch some TV, that's refreshing.
So I'm all for flexibility but please don't overshoot.
Telecommuting is good when the job is not emergent and requires a high amount of concentration (architecting, engineering, designing, given you have the tools at home).
The very sort of people HP is calling in from the home.
However if your job is routine, technical, and requires lots of work, associated with stress, telecommuniting can make you lazy, slack often (having no control) and doing a bad job overall.
The very sort of people the new HP manager behind this move is used to dealing with in his previous job at Wal-Mart (no, that's not a joke. RTFA).
KFG
From TFA:
In an office, ``you're able to put teams together that can learn very aggressively and rapidly from each other,''
Agreed, IMO lower skilled work environments are much better suited to home working. For example call centre work etc. The only reason I say this is that everyday I go into work and I learn something new from the people around me. Not to say this is "agressive" but if I get stuck on a bit of code, or perhaps a general concept I know that others around me may be able to help, and if they cant then we have discovered something that we as a group are lacking in.
Otherwise these thing go unnoticed, you recieve no critism and do not learn as effectively. Ideally in a team the stronger members of the group can carry the weaker members until they have caught up with the rest.
I cant see how this could be as effective in homeworking, in fact some animosity may occur towards weaker members due to percieved "lazyness" when actually they are just have legitimate trouble with their task.
If anyone can give me a citation for the following story, I'd be really grateful.
Some time prior to 1990 I read a story about research done at HP on employee performance. They decided to find a correlation between employee performance and school performance. They found no correlation. It didn't matter where you went to school. It didn't matter how many degrees you had. It didn't matter what your marks were. That wasn't surprising. The Navy had discovered the same things many years previously. What was surprising was the discovery that the highest performing employees were the ones who hung around the water cooler.
Gregarious people make better employees. If you put people together, you get better work. Laying off the people who won't come in to the office seems like quite a good move.
Should singles who deliberately choose that lifestyle to be frugal receive less benefits?
I feel fantastic, and I'm still alive.
WallyWorld manager moves to HP and starts treating IT professionals like illegal immigrants and sub-minimum wage unskilled workers. That is an absolutely beautiful, crystal clear look into the future, because in the US, corporate managers and CEOs are being trained, or conditioned, to think of all workers in precisely that way.
In the US today, employees and customers are the enemy as far as corporate management and CEOs are concerned.
"In a time of universal deceit, telling the truth is a revolutionary act!" -- George Orwell (Eric Arthur Blair)
I've been on two sides of the issue.
First, as a 'worker' I was allowed to telecommute occasionally. I know that for myself (reasonably well motivated) the temptations at home were too strong for me, and I ended up screwing around about 4 hours a day. Add a wife/kids to the mix, and I would not consider this time to be productive. My co-workers all reported the same thing.
Now as a manager, I run into similar problems with my employees. It took a while for one guy to figure out that Xbox Live lets me know exactly how much screwing around he is doing. (Hmm...he had Oblivion running all day, AND got 5 achievements...) Yet of course he claimed to be working all day. He is no longer eligible for telecommuting.
Now I only support telecommuting with other employees occasionally, and only if there is a very defined project with a definite deliverable at the end. For instance, "You need to have this help file completely finished tomorrow." (Knowing that it is probably a 4 hour job that would be stretched to 8 even if they were at work.)
I'm not trying to be an asshole, but it's just the reality for the people I work with. Given the opportunity, they would sit at home and play games- while making excuses why things didn't get done. They did that when I was part of the team, and they tried to do it when I became the boss.
(Truth be told, when they are AT work, they are very effective, highly productive, and a great team. They are not a bunch of clowns, they just get distracted. But being distracted at work is what lets them see problems from many angles, so it is a good trait if focused on productive issues, instead of deciding which armor to wear.)
No reason to lie.
Japan, S. Korea, and many European countries are imploding because too few choose to pass along the investment (food, housing, education, time) they received as children. There is a large economic payoff to childless individuals, yet a high cost to society overall if too many take that route. Families are what keep society going, so society has a vested interest in promoting family. No reason to turn it into a religious debate, just look at the demographics.
If you're the type who needs a work environment to keep focused it would be better not to telecommute, but I bill less when the customer lets me work at home and get more done. It's not that hard to monitor performance in a remote development environment. Either someone is making their milestones or not, closing trouble tickets or not. I can look at their code and tell how long it should have taken vs the actual billing. What I save in clothes, gas and commute time is invaluable. My equipment, my dev environment, my work space at home are all set up for how I work.
A phone list and a speaker phone is all I need for quick consults, fax machine for paperworks, we keep code libraries in common access areas accessible via VPN if I need something. I find interaction at work actually detracts from production more often than helping it. There are times when face to face meetings are unavoidable, like gathering requirements and monitoring user interaction on betas, but other than that I'd say a full 75% of interuptions at the office are at best unproductive and frequently just plain annoying. If I have to forward my office phone, my productivity tanks. If I can check messages a couple times a day that's better.
For people interested in playing politics or needing interaction with other people, an office is necessary. For me the more you leave me alone, the more I'll get done. Sometimes I'll collaborate with other developers...I work with a graphics guy in California regularly. We can work together almost like we're in the same room. We've had three way phone confernces where we've all been hammering away on our part of the app, yapping back and forth on the speaker phone. It was very much like being in an office.
That's our life, the big wheel of shit. - The Fat Man, Blue Tango Salvage
Carly Fiorina was the strongest proponent of sending American jobs to India, effectively creating an entire industry of telecommuting.
Now HP is saying telecommuting is bad?
Face it. Corporations want to be slave-drivers, and it's only through democratic lawmaking that we keep them from getting their wish.
(ObDisclaimer: I work for HP IT. But if you're looking for a "Randy Mott/Mark Hurd Sucks" message, this isn't it. HP has a very vocal set of internal fora for bitching at management. I do my whining through the media which might actually effect change. Slashdot, I'm afraid, isn't it).
Firstly, the policy of colocation is not just tied to telecommuters - the idea is to centralise a highly distributed IT workforce. So, eventually, nearly all IT workers will need to relocate to a few central locations. The teleworkers are just first on the list for relocation.
Secondly the problem for many IT firms is not telecommuting per se, it's the fact that we've just sleepwalked into teleworking without a clear business analysis as to whether the business operations can effectively sustain this model of working in each case. Sometimes they can, sometimes they can't. Now, this is a historic failure of management - senior employees get sufficiently pissed off with life in the Bay Area, or Houston, or Atlanta, and feel the need to get a quieter life in Dogshit, Nebraska. Fine and dandy - but it's effective management to say "Sorry, we can't have you in your current job doing that". Neither mean, nor incorrect - just a manager doing his/her job in keeping the department going. But we don't do that - we just say "Yeah, sure. Get an ADSL line, we'll be cool". Sometimes it's true - sometimes it's not. Now - how do you pull that position back into line? In HP, that's Randy Mott's problem. He's got a system that's been allowed to grow wild in many areas and is, to all intents and purposes, out of control.
Randy Mott has an extremely aggressive set of targets in trying to push up the efficiency of HP's IT. Maybe he's going about it the wrong way - if so, he'll pay with his job.
--Ng (not in any way speaking for HP, HP IT, or Randy)
It's funny, because I see just the opposite with my once-a-week telecommute. I get interrupted all the bloody time when I'm in the office, which makes it very hard to work on the "big picture" projects we've got going. On my telecommute day, I don't get the walk-in or phone-in interruptions - it's much easier to focus and get work done.
At the end of the day, I send my boss a list of what I've worked on.
The only downside for me is I have a tendency to work extra hours those days, because there'll be one or two things that I know will be difficult to finish with the "one interruption every 10 minutes" atmosphere that pervades our computing group (most of which are not relevant to my actual job).
#DeleteChrome