Using Employee-Owned Technology in the Workplace?
digitalvengeance asks: "As of Monday, my company is initiating a 'no cell phone' policy at all of our offices, including the IT department, where I work. I consider my cellular phone a necessity both in my personal and work lives. I have a number of servers and custom applications configured to notify me by text message, in the event of a problem. I am considering refusing to take work calls or text messages on my personal cell phone, and even quitting in protest of the new policy. How have other Slashdot readers dealt with policies regarding use of employee-owned technology at work? Any suggestions as to how I can get this policy overturned without looking like someone who wants to spend my working time on my cell rather than coding?"
If they stonewall and ignore your concerns, then by all means, raise a stink. In the interests of civility, job security, and conservation of energy, though, you may want to try the easy way first. Don't break out the elephant gun before you've tried the flyswatter...
Obliteracy: Words with explosions
Have them pay for an alpha pager and move your alerts there. Really, quitting over the use of a device you've become addicted to is not the smartest reason to terminate employment.
"Draco dormiens nunquam titillandus."
then they should pay for it. Plain and simple. My office has no idea I have a cell phone number. They know I have a phone, but they are not gonna get the number unless I see part of the bill being paid by them.
-------------------------------------------------
Seems pretty obvious to me: ignore their silly rules, set your phone on vibrate and go about your business.
Quit over this? What, are they going to fire you if you check an occasional text message on your (silent) cell phone?
Some rules are made to be broken, not fought.
No joke. I could post for pages and pages with antecdotal evidence, from my own experience and that of fellow geeks, that the quickest way to eliminate a policy or new set of particularly stupid regulations is to follow them to the letter. For instance:
POINTY-HAIRED BOSS: Why didn't you know that Server X, Application Y, and Cubicle Drone Z were all hosed and not responding to requests?
YOU: Well, sir, I get these notifications, see, and when I'm working in another part of the office or not sitting right at my desk, I know instantly if something goes wrong with anything that I'm responsible for and then I can fix it.
PHB: But...that doesn't explain why you didn't know about XYZ!!
YOU: Well, these alerts all come on my cell phone, you see, and since it's company policy that Cells Are Not Allowed...
The dumber it is, the more religiously you should follow it, and make darned sure that all of your buddies fall in line with the company's new direction as well. I'm assuming, of course, that you've already presented your case to a supervisor or HR person or something, and that you're not a Super Executive VP of Something. If you're at that level in the organization, just say "no" and have your department behave differently from everyone else...apparently this works in the real world if you're high enough on the food chain.
"Linux doesn't exist. Everyone knows Linux is an unlicensed version of Unix"- Kieren O'Shaughnessy
I agree. I see so many posts saying something to the effect of: "Stop bringing it, they'll see how important it is when servers go down because nobody got the pages". Wow, what's happened to our work force? Here are a few ideas that might actually look like you give a shit. It sounds like we're stuck in a "Clerks" version of IT!
1.> Have a little frigging back-bone, people. state the issue to your boss in an e-mail. Document it. Be sure to be detailed on the risks.
2.> Contact HR explain the above.
3.> If the above doesn't work (as American AC in Paris has also suggested the 1st two). Contact internal customers who have jobs running on the impacted systems. Explain the situation and the risks.
4.> Be willing to help develop either a more defined policy (i.e. no private calls, no digital cameras) or accept an alternative (alpha-pager).
5.> At the first issue of an outage because no-one got notified, bring this up. Don't wait for all hell to break loose.
Following these steps with the right tone, enthusiasm, and tact, you'll at worst look like you actually care about your job and the company you work for. Unless maybe, you prefer to live on welfare, unemployment, and bitch about how the internet stock bubble saturated the job market with IT guys. Be a "stand-up geek" and do the right thing.
www.facebook.com/DareDefendOurRights
www.fairtax.org
You do as they say w/o too many questions. If you don't like the working conditions you find another place that is more towards your liking.
:)
India?
Seriously, though, the whole "like it or lump it" attitude always bugs me. How in the world do employers manage to brainwash people into thinking that they're gods? Who says that I have to do what my employer says? If their policy is really that bad and the situation is really that serious, go over their heads, make some sort of formal complaint and encourage others to do the same, talk to your union (if you have one), illustrate the consequences of that bad decision (as an earlier poster suggested, "The server's down, who knew?"), and/or threaten to quit (as a next-to-last resort). There are alternatives to quitting if you're clever enough to use them and if the situation justifies using them.
If all that doesn't work, _then_ you quit, but even then only if it's worth it. Remember the perks of your job, the friends you've made at work who you won't see as much anymore, the extra effort which you'll have to put into finding a new job and making a new routine for yourself, and so on.
I think the real risk of the interference is low, but it would actually be funny if it looked like everyone on the floor flatlined at once, as someone walks by talking on their cell phone.
I had an incident where one employee left a cell phone at their desk, it rang (one of those really annoying music rings) on and off for nearly an hour. Another employee (next cube over) turned it off. The first employee went ballistic about that. That was fun. Once in a while I'll have an employee who just spends wayyy too much time talking on their cell phone. Lovely to deal with that as well.
The reason companies never wanted people making personal calls at work was not the cost of the (mostly local) calls, but the cost of their NONPRODUCTIVE EMPLOYEES. When employees have cell phones (as most do now), they feel much more justified in sitting around on the phone since the "cost" is theirs. People who know not to spend hours on personal calls on their desk phones seem to have no compunction about doing the same thing on their cell phones.
So what's the solution? In my experience, the RATIONAL answer is to speak to each person when you feel that they've crossed a line, and make a decision suited to the problem. In my experience, the rational answer will get you reamed. Employees who care so little about their responsibilities to their work and to their co-workers tend also to have no compunction about arguing "disparate treatment" (as though cell-phone users are a protected minority). We are forced to make inane blanket policies that hurt the decent employees who probably ARE contributing their personal cell minutes to the company, in order to stop the bad behavior of a few. I've been told by HR that I cannot tell ONE employee to "leave the cell phone in your car" I must make the rule for EVERY employee in the department (not that I have, I'd rather lose the productivity of the lamer employees than disgruntle the better ones).
Anyway, there are two sides to every story.
~
"A foolish consistency is the hobgoblin of little minds." -Emerson
I don't see what you can possibly do in this situation, short of quitting. If they don't trust their own employees, then they're not going to be receptive to employee feedback. If you dissent politely, they'll smile and ignore you. If you dissent rudely, you'll just reinforce their patronizing attitude.
And playing work-to-rule games ("I didn't know the server was down because my cell was switched off, as per policy") isn't going to help either. It's just another way of communicating something the bosses don't want to hear, except that it also makes them look stupid. Which is not likely to make them receptive.
Sometimes management falls into the mode of treating employees like spoiled children -- people who can't be communicated with, only bullied into a semblance of correct behavior. If you can figure out a way to change that attitude, you've really got something (like a nomination for the Nobel Peace Prize!). If you can't, there's not a lot you can do.