Slashdot Log In
IBM Responds to Overtime Lawsuits With 15% Salary Cut
Posted by
samzenpus
on Thu Jan 24, 2008 07:55 AM
from the give-with-one-hand-and-take-with-the-other dept.
from the give-with-one-hand-and-take-with-the-other dept.
bcmbyte writes "IBM in recent months has been hit with lawsuits filed on behalf of thousands of U.S. employees who claim the company illegally classified them as exempt from federal and state overtime statutes in order to avoid paying them extra whenever they worked more than 40 hours per week.
The good news for those workers is that IBM now plans to grant them so-called "non-exempt" status so they can collect overtime pay. The bad news: IBM will cut their base salaries by 15% to make up the difference."
Related Stories
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
Hmm (Score:5, Informative)
Re:Hmm (Score:5, Informative)
Parent
Re:Hmm (Score:5, Insightful)
It's a short term monetary gain (in the form of a settlement), for a net loss in wage security
Depending on the job, wage security is often less of a concern than schedule security, ie the possibility that the boss will tell you you're working 80 hours next week. Now he has to account for extra overtime over the usual in his budget, and that's a heck of a deterrent.
Each may very well be more important to different people. As another respondent said, this probably is best for the quality employees who always find themselves overcommitted and working hard, and maybe less good for clockwatchers.
Parent
Re:Hmm (Score:4, Insightful)
I have to disagree. The best employees may be the one who are smart, effective, and efficient, and can get their work done in forty hours. They'll get screwed.
The problem is that there are some jobs where time spent is the most important metric. Working the help desk, for example, or being a cashier. More productive employees (in theory) should make a better hourly wage, but there's a pretty close correlation between time spent and work accomplished. However, that's not the guideline for what makes an "exempt" employee. That has more to do with issues of self directedness. If the boss says "this week your setting up these servers", your probably not an exempt employee However, some people might take 8 hours, some might take all week. In that kind of work, the difference in efficiency between people can be enormous. It's a lot less if you're delivering packages.
If IBM hired these people with the understanding that this would be a forty hour a week job with "occasional" overtime, than this is an admission that they lied. Which stinks. It also smacks as a power play against people who complained. Which also stinks. My sympathies to everyone affected by this - I'd be mighty pissed if it was me.
Parent
Re:Hmm (Score:4, Informative)
It may be advantageous in a few cases, but the effected employees know that in this case, it won't be.
First, while we're allegedly going to be making up the loss in overtime, we've been here long enough to know the other shoe will eventually drop. When management wants to make cuts, they'll start with cutting OT hours. They do that with contractors already. This effectively means you aren't going to be seeing that 15% again.
Second, consider your vacation pay, bonuses, and other bennies, are figured on your base salary, not on what you earn with overtime.
Any way you look at it, this is a pay cut.
Parent
Re:Hmm (Score:4, Insightful)
Parent
Re:Hmm (Score:5, Interesting)
My experience has been that in an environment where you may be expected to put in extra hours the exempt employees are usually paid a little more than they normally would. In most cases if you are an exempt employee there is no need to fill out a time-sheet and while you may be expected to put in extra time on occasion the flip side is that no one will be looking for you if you take a long lunch or leave early on the "slow" days.
While non-exempt employees do get paid overtime you usually need to fill out a weekly time-sheet (or even punch a time-clock)-: and sign under penalty of perjury that you did in fact work the hours listed.
Give me exempt status anytime - if I don't like the hours I can always go elsewhere.
Disclaimer: I'm not aware of IBM's work policies having never worked there.
Parent
Re:Hmm - OT Denied (Score:5, Interesting)
That way, you get a good paycheck, you are in charge of your OWN money/retirment, and you NEVER work for free. You get paid for every hour you work.
I swear, if possible, I'd NEVER go back to working as a W2 employee again...
The only thing needed for a mass transition to this, is to make it easier for single person corps to be able to buy into a group insurance scheme, or make it easier for individuals to get insurance for themselves (it isn't THAT expensive, but, hard to get if you aren't in 100% top health).
Anyway, doing this would cut companies' HR expenses, cut all the overhead of benefits, and then they could easily pay the bill rates required.
I mean, in todays world of "at will" employment, and the lack of loyalty from either employer or employee, why not just get the formalities of W2 employment out of the way, and call the workforce of today, what it is, and pay for it that way.
Parent
Re:Hmm - OT Denied (Score:4, Funny)
Parent
Re:Hmm - OT Denied (Score:4, Interesting)
If you're working on an hourly consulting basis, sure, if you can get the job done in 20 hours when a slow person gets it done in 40 hours, the slow guy is actually going to get paid more for you to get the same job done slower. But once a company realizes you are reliable and efficient, you're going to get the jobs in the future--not the slow guy.
I used to think like you. Even as a consultant I'd try to spec a project and come up with a fixed-price bid. That way both the client and I could focus on getting the work done rather than stressing about counting hours. But last year I got burned by two projects that, through no fault of my own, ended up being significantly more complex than could be known in the quoting process--but since the complexity wasn't known, it wasn't specifically limited in the contract. So it wasn't specification creep (which would definitely be billable), it was just more complex to get the things done than either the client or I recognized. So I had a tough year.
Having learned from that, I have to protect my own rear end. I've come to the conclusion that billing on a strict hourly basis is in everyone's interest because:
So now I give clients a good-faith estimate of how long certain things will take, but the actual billing amount is based on the actual amount of time I spend on them. The estimate is just that: An estimate so they can have a reasonably accurate idea of what they're getting into. If it takes less time, they pay less. If it takes more time, they pay more. And they know that up front. And if, as I proceed, it's becoming clear that my estimate was low, I immediately let the client know why and how much more I think it will end up costing. Then they make the decision. Of course, I virtually always come in at or below the estimate so the client is actually pleased to pay less.
The only reason a per-hour arrangement might not be ideal is if 1)You are not honest about the hours you work--in which case you shouldn't be billing by the hour or, 2) The client is suspicio
Parent
Re:Hmm (Score:5, Insightful)
Don't get me wrong, there are super-producers out there who get a ton done in a 40 hour week and then work another 40 hours every week. (Although I'd argue that this isn't really sustainable long term.) But for every one of those, there's at least one person who works a ton overtime and makes a lot of drama about what a hard worker they are, but doesn't actually get shit done, and there's also at least one person who works hard and busts out more than their fair weekly share of work but manages to do it within 40 hours.
A lot of company cultures reward the high hours low output employee over the 40 hours high output employee, and it's their loss when those people leave.
Parent
Re:Hmm (Score:4, Insightful)
Parent
Stapler (Score:5, Funny)
Re:Stapler (Score:5, Funny)
Parent
Typical. (Score:5, Insightful)
Re:Typical. (Score:5, Funny)
Parent
Re:Typical. (Score:5, Funny)
By golly, I think you really are a Presidential candidate!
Parent
Re:Typical. (Score:5, Insightful)
Parent
Re:Typical. (Score:4, Insightful)
More importantly, without knowing the weekly hours range as well. Personally, I would jump at the opportunity of taking a 15% paycut if I could get OT pay, because my take-home would go up considerably.
For everyone calling IBM evil bastards over this, consider - Working hourly rather than salaried, a 15% pay cut translates to a mere 4.7 hours of overtime. After that, you make more than you did before.
So, if this involves only an extra hour or two here and there, IBM sucks. If more like 10 hours, these people will make quite a chunk of extra change each week.
Parent
Re:Typical. (Score:5, Interesting)
I've been "exempt" for the past 10 years, and wouldn't trade it for hourly wages + overtime for anything. The fact I'm "exempt" pretty much assures that I have a strong salary and needn't worry about those extra 5 overtime hours per pay period to make rent. I realize that sounds snobbish, but TFA gives examples of jobs in the 80k per year range...hardly the types of jobs that worry about making the rent payments.
A better solution than the labor unions would be for these 80k/year salaried folks to take their skills elsewhere, like to a company that values their contributions. I've never understood how a union supporter could go back to work for the same pricks they were fighting with in the first place.
Parent
Some reference materials (Score:4, Interesting)
29 CFR Part 541, Defining and delimiting the exemptions for executive, administrative, professional, outside sales and computer employees, final rule [dol.gov]
IBM may very well have been legally justified to not reimburse these folks the overtime pay in the first place. However, since it was found otherwise, I think the 15% pay cut to compensate is just spitting in the face of their employees. How many good engineers and other employees will they lose as a result of this move? It seems to me that if you have good people working for you, willing to stay after hours to keep things moving, you should reward them for the extra effort. Too bad if it happens that computer employees rack up lots of overtime, but it's the nature of the business and should be considered cost of doing business.
Parent
Re:Some reference materials (Score:5, Insightful)
Previously, their annual salary would've been approximately 2000*x. It is now about 1700*x. Assume overtime is time and a half, they would get paid 1.275*x for each hour of OT. This means they would need to work about 236 hours of OT a year, or about 4.5 hours per week. If they were working so much OT that they were willing to sue, then this should be easy to make up and in the end they are making more money, since they weren't getting paid OT before.
Their only other option would've been to unionize; however, if these are programming and/or engineering jobs, you can bet IBM would've outsourced them in a second to save the money and the hassle of dealing with a workers union. Also, don't think there aren't plenty of engineers in the US who are willing to "scab". Most the engineers I know (myself included) absolutely abhor unions.
Parent
Re:Typical. (Score:5, Insightful)
Parent
Re:Typical. (Score:4, Insightful)
The union is only as good as the members that care enough to get involved. If all you do is sit back and complain you get the union you deserve.
Parent
Re:They need a Union (Score:5, Insightful)
Parent
Re:They need a Union (Score:4, Insightful)
The problem with Detroit is that they design and sell a shitty product. The line worker doesn't control the quality of the parts he/she bolts onto the car as it passes by. All he/she can do is his/her job to the best of his/her ability, but a poorly designed engine mated to a shit transmission inside an ugly-ass package can't be improved by paying the worker less. Detroit is a victim of their own mis-management.
Now I'm not saying that the UAW doesn't share some of the blame for Detroit's financial woes; I'm sure they protect incompetent workers all the time. The problem is, if they're going to protect the competent ones, they have to protect everyone.
Parent
Again. (Score:5, Informative)
Re:Again. (Score:5, Insightful)
The end result is exactly what IBM did. Suddenly starting to pay for overtime means IBM is raising effective salaries by 10-20% or more, so naturally IBM lowers base salaries. The end result is that we are exactly where we started - people work the same hours, and get the same pay.
Well, at least on average; for individuals who work more or who work less, there will be some change. There are also motivational issues - if you are paid for overtime, you have less incentive to work efficiently (one reason why hi-tech managers, and many workers, don't like paid overtime and prefer to raise the base pay). Overall, it is hard to say that the change is for the better. The old salaries and norms were already 'working' - they were comparable to industry norms, were arrived at after years of haggling, corrections, and so forth, and most importantly people knew what they were getting when they signed on.
Parent
Lawsuit? Prepare for Other Pain... (Score:5, Interesting)
Sounds about right, actually (Score:5, Interesting)
Re:Sounds about right, actually (Score:5, Interesting)
In my experience, the biggest drawback to being an hourly employee is that the company tells you when you can't work. If you're really enjoying a project or on a roll, it's extremely frustrating to be told that you have to stop for the day/week. You can't just not record any extra hours worked either as it's a liability for the company.
Parent
It's stories like this... (Score:5, Insightful)
The bad thing about being a contractor is I only get paid for the time I work (no sick leave, public holidays, annual leave etc)
The good thing about being a contractor is I get paid for _every_ hour I work.
Strangely enough, once I was working on a strictly per-hour basis, the boss found far fewer 'emergencies' that required me to work all weekend.
Re:It's stories like this... (Score:5, Insightful)
The bad thing about being a contractor is I only get paid for the time I work (no sick leave, public holidays, annual leave etc)
The worst day working for yourself is better than the best day I've ever had as an employee...ever. There is a lot of detail work necessary: Invoicing, collecting on the invoices, insurance, license fees, expense tracking, quarterly taxes. And there are liability issues to consider. But as more and more employers keep pushing responsibility and accounting issues down to the lower ranks, the amount of paperwork really isn't that different. Many employers expect you to process all that paperwork on your own time and travel on your own time. Plus a lot of them are getting dickishly intrusive monitoring and spying on their employees.
Besides, cubicles suck ass.
IBM gets caught breaking the rules and responds by cutting salaries. Nice. Just keep pulling stunts like that and your turn over will remain painfully high.
Strangely enough, once I was working on a strictly per-hour basis, the boss found far fewer 'emergencies' that required me to work all weekend.
Funny how that works, isn't it? Want me to work all weekend? No problemo! Just sign this invoice...right there...here's a pen.
Parent
Re:It's stories like this... (Score:5, Insightful)
I'm sure someone will soon reply to this insisting that I'm a socialist and I'd like to see everyone's taxes go up as high as possible. Neither is true. IMHO we can provide every American with access to health care universally without increasing taxes. This might sound impossible, but work with me here: The unemployed/underemployed don't stop needing health care just because of their work situation. Hospitals can't refuse to treat people based on their insurance coverage (or lack thereof). The taxpayer is already paying for their health care through programs like Medicaid. Making health care universal only requires repurposing of tax revenue, not increasing it.
I'm sure someone will respond to that by pointing to the Canadian system, and how the quality of coverage is perceived as low as compared to the US system, where you get as much health care as you can afford. The rich don't need more health care than the poor; as much as they'd like to insist that it isn't the case, we're all the same on the inside, despite someone's bank acount being larger than someone else's. If we all receive the same level of care, and it's perceived as poor, then we can work to improve it for EVERYONE, not just the rich.
Parent
Penny wise and pound foolish (Score:5, Insightful)
Re:Penny wise and pound foolish (Score:4, Insightful)
Parent
Salary + Commission + Overtime? (Score:3, Interesting)
The fact that they were collecting commission on top of their salary, and still trying to demand OT pay is simply greedy IMO. Sales has always been a "You'll make as much as you want to" position.
Re:Salary + Commission + Overtime? (Score:4, Insightful)
It's fine that for you the slow weeks compensate for the crunch ones, but if you are at your desk for at least 40 hours a week (working or not) then there's no compensation whatever, you are still giving away your free time.
I must say that I'm also willing to work more than 40 hours (any reasonable number of hours) when needed, but I'm actually getting my time back (in time, not in cash - which I actually prefer).
Parent
Where did they think... (Score:4, Insightful)
Personally, if it were me, I'd be happy about the change. Less guaranteed money, but for quite a while I've wished I could work -less- than 40 hours a week, even if it meant a pay cut. SO much other stuff I want to experiment with and no time to do it. So to have that overtime on the books instead of just being expected...
I'd guess many of these people will find newhires in their departments and 40hr/wk jobs again, too.
There are some who only lose in this story, though... The 1/3 of the affected workers who were -not- working overtime and were not involved in this lawsuit. They get paycuts anyhow. I can imagine how nice the workplace will be for the next year... Assuming any of those 1/3 stay. I sure wouldn't in their shoes.
What about "undertime"? (Score:5, Interesting)
Re:sounds about fair (Score:5, Interesting)
Parent
Re:sounds about fair (Score:5, Insightful)
Wrong. Harm done. Sure, you keep working overtime and your take-home remains about the same. Except when you take a vacation or go on maternity or other medical leave, and suddenly your income drops 15% for the duration. Also, the company's annual pension payout to you drops 15% because that amount is based on your base salary, not overtime.
Parent
Re:Free market (Score:5, Insightful)
Parent
Re:regulated in contract or law? (Score:5, Informative)
When I used to work for IBM (10 - 8 years ago), it was standard U.S. practice: each year, your manager calls you into a meeting and tells you what your new pay level is. You can accept it, or quit your job, or treat it like the beginning of a negotiation, which will in most cases get you labeled as a difficult employee.
It's pretty laissez faire, except that they can't base your pay level / pay level changes on race, religion, etc.
Parent
Re:Free Market (Score:5, Insightful)
Parent
Re:Free Market (Score:5, Informative)
Parent
Re:Free Market (Score:5, Interesting)
This does sound like a slap in the face, but the first slap was by the employees -- suing your employer (or anyone) "means war".
No, the first slap was IBM breaking the law by classifying employees as exempt when they were not. The employees are totally in the right here, and IBM 100% on the wrong side.
Companies like to claim exempt vs. non-exempt is a "gray area." Its only gray when you're trying to screw your employees out of overtime pay.
My personal belief is that salary pay should be made illegal except for strickly management positions. That would solve this problem nicely.
Parent
Re:I don't understand (Score:4, Funny)
With an attitude like that, you'll never make it into management. Read more Dilbert cartoons.
Parent
Re:Seriously (Score:5, Interesting)
You have obviously not thought that through to completion. You decide to form a union, and your employer does not like it. One of several things can happen:
1) Your employer takes it on the chin and suffers from a significant loss in net earnings (usually gets executive types all fired up, pun intended).
2) Your employer accepts it after fighting about it and is then undercut by union free competitors, typically using H1B labor, or worse yet simply outsourcing to another country altogether.
3) Your employer gets smart and simply outsources your job, thereby skipping all of the intermediate steps.
Our economy has become a service economy because those are the only jobs that cannot be outsourced easily, but a service economy can't survive indefinitely without outside support. Either way, unionization is not the answer, the only viable answer is to accept that you will suffer a significant drop in standard of living to adjust for the fact that you were way far above the median to start with. Don't like it? tough, welcome to the global economy, there isn't a damn thing you or I can do about it. If you shut down all foriegn trade, there goes your cheap goodies from china, and your standard of living plummets. Imagine if you had to pay $30,000 for a low end car, because it was made using exclusively american labor? How about $120 for a pair of jeans? What about $5,000 for an entry level PC? If you need proof, just look at the cost of housing. It is hideously expensive because there is no good way to offshore the labor needed to build the houses, and as such the cost of these things has been rising at many times the rate of inflation. It is a no-win situation. Americans are not going to enjoy their standard of living much longer, but there isn't anything we can do to stop it. Maybe slow it down a little, or speed it up, but there is no stopping it.
-=Geoskd
Parent
Re:Seriously (Score:5, Insightful)
Not bad. Not bad until you got to the part about housing.
US housing costs are dramatically cheaper (on average) than those in western Europe. The primary reason for the difference is that housing costs in the US reflect the fact that land on which to build is cheap, so the cost of buying an existing house has to compete with the fact that you could, if you were willing, simply build a new one. This option is generally unimaginable for inhabitants of most of Europe, where land prices make this option absurd. As a result, house/apartment/rental costs there are not competing with the "i'll do it myself" option, and can climb to levels contained only by median salaries.
Your inevitablity stance on a global economy is also a little sad. Things like the "global economy" don't just happen. They happen because a specific (if large) set of vested interests arrange/push for it to happen. In this case, owners of capital who stand to see huge benefits from the free flow of their property, have pushed hard for it while telling everyone that the whole world will benefit from it. They have resisted similarly free flow of labor, while relying on the fact that moving labor around is much harder than moving capital. It was never inevitable - its the result of power and money seeking more power and more money, just like so much of human history has been.
Parent