Monday, April 2, 2012

An good example of an overly broad social media policy


Reuters is reporting that a union representing employees at a New York grocery chain has asked the NLRB to investigate whether the store’s social media policy is violates employees’ rights to engage in protected concerted activity under the National Labor Relations Act.

According to the article, the policy in question “forbids employees from disclosing confidential information—including salaries—on social networking sites like Facebook or Twitter, and from discrediting the store’s practices or products.” For its part, the employer commented that “the store’s policy is meant simply to remind employees to use ‘reasonable guidelines’ when posting to social media sites.”

The employer’s goal is commendable, and reminiscent of my four word social media policy, “Think before you click.” But, if the article is correctly reporting the scope of the challenged policy, it goes well beyond reasonable. The clearest example of protected, concerted activity is conversations about wages. You cannot have a policy that prohibits employees from talking about how much they make, and that rule doesn’t change whether the conversations are at the water cooler, in the break room, or over the Internet. If I was the company’s lawyer, I’d be telling them to change the policy ASAP, before the NLRB orders them to do so.

[Hat tip: Delaware Employment Law Blog]

Friday, March 30, 2012

WIRTW #219 (the “recap” edition)


The Labor & Employment blawgosphere nearly blew itself up this week, with Facebook passwords and the Supreme Court’s healthcare argument dominating the headlines. In case you were under a rock this week, here’s my 140 character summary, fit for you to copy and paste into Twitter: “Requiring Facebook passwords from job applicants is bad, but, it looks like S Ct might think individual health insurance mandates are worse.”

Looking for more details?

Facebook Passwords

Health Care Law Oral Argument

Here’s the rest of what I read this week:

Discrimination

Social Media & Workplace Technology

HR & Employee Relations

Wage & Hour

Labor Relations

Thursday, March 29, 2012

What’s on your tombstone?


At his Work Matters blog, Mike Maslanka asked the following question: “What will be on your tombstone?” Don’t get me wrong. I love my job and would not trade what I do for a living for any other profession. But, please kill me again if my tombstone is work-related. I’d much prefer, “He was a great husband and dad,” or, “He loved his family,” to, “He could write a great brief,” or, “He could oral argue with the best of them.”

That’s my tombstone, but what about yours? A tombstone is your legacy. It’s a phrase that is supposed define you for all eternity. That’s why it's etched in stone. So, if you could pre-write your own tombstone as an employer, what would it say? How does this sound? “A company that treated everyone fairly.” Or, “Employees loved to work there.” So, what does your tombstone say? Leave me a comment below, or, post on Twitter with the hashtag #HRtombstone.

Wednesday, March 28, 2012

Courts are finally starting to apply ADAAA—and it ain’t pretty


It’s taken awhile for courts to start applying the ADAAA—the January 1, 2009, amendments to the Americans with Disabilities Act that rendered everyone with a medical condition disabled for purposes of the disability discrimination law. With one glaring exception, courts have concluded that the amendments are not retroactive, and only apply to personnel decisions taken on or after January 1, 2009. After a bit of a waiting period, courts are now starting to weigh-in on disability cases under the ADAAA, and, as expected, for employers it is not pretty.

Consider Wells v. Cincinnati Children’s Hosp. Med. Ctr. (S.D. Ohio 2/15/12). Elizabeth Wells, a nurse at Cincinnati Children’s, suffered from gastrointestinal problems. When she returned to work following gall bladder surgery and FMLA leave, she committed various errors (e.g., pulling morphine for a patient that had no orders for it) that called into question her fitness to work as a nurse in a Critical Airway Transplant Surgery unit. The hospital believed the errors were related to her post-surgical medicine, Lotronex, which can cause confusion, sedation, and equilibrium disorders. The hospital placed Wells on administrative leave and referred to her its employee assistance program. The hospital refused to reinstate Wells to the transplant unit after her doctor cleared her to return to work. Ultimately, it found her a position in a bone marrow transplant unit, albeit at reduced hours and with a pay cut.

The trial court concluded that Wells’s disability discrimination claim relating to the hospital’s failure to reinstate her to her old position should go to a jury. Notably, the court pointed out that she need only prove that the hospital “regarded her as having an impairment,” and, in contrast to the pre-amendment ADA, under the ADAAA’s “regarded as” prong, “a plaintiff … only has to prove the existence of an impairment…; she no longer is required to prove that the employer regarded her impairment as substantially limiting a major life activity.” In other words, as long as Wells could prove that the hospital believed she was impaired, the ADA covers her. That burden was easy for her to meet: “The gastrointestinal problems which caused Plaintiff nausea, vomiting, and diarrhea clearly qualify as a physiological disorder. Moreover, to the extent that the side effects of Plaintiff’s proper use of prescription medication adversely affected her ability to work, it would contribute to a finding that she was disabled.” Because the hospital essentially demoted her following her leave, her ADA claim survived.

The hospital’s only sin was that it did not want a nurse who blacks out and becomes confused when treating and administering narcotics to critically ill children. Perhaps, however, the hospital doomed itself by re-employing Wells at all. Because the bone marrow transplant unit also involved critically ill children, the court was skeptical of the employer’s rationale.

The ADA has become one of the most dangerous statutes for employers to administer. It covers virtually any medical condition, actual or perceived. Any time you are making an employment decision concerning any employee about whom you know, or believe, to have a medical condition, you will be best served to take a step back, take a deep breath, and take a few minutes to consult with your counsel. You do not want to shoot first and have to answer questions later.

Tuesday, March 27, 2012

I (usually) hate unemployment challenges


As an advocate for businesses, you might assume that I stand behind an employer’s decision to challenge an ex-employee’s claim for unemployment compensation. You’d be wrong. In fact, I believe that employers are better served not challenging the unemployment compensation claims of most ex-employees. Just because an employer can win an unemployment challenge doesn’t mean it should file the challenge in the first place. In most cases, employers should simply chalk unemployment up to the cost of doing business, and having to hire (and fire) employees.

Of course, for every rule there exists the exception. Some employees lose their jobs for misconduct that cannot be tolerated and must be challenged. Case in point: Clucas v. Rt. 80 Express, Inc. (Ohio Ct. App. 3/26/12) [pdf]. Rt. 80 fired Clucas, a truck driver, after he tested positive for marijuana following a minor accident. Needless to say, the court of appeals upheld the denial of his unemployment.

Clucas is a great example of when an employer should challenge an employee’s unemployment claim. A business cannot have truck drivers under the influence while on duty. Other examples of when it’s appropriate to challenge unemployment are egregious intentional misconduct such as theft, harassment or other discriminatory conduct, or assault. Unemployment is another example of the maxim I discussed a few weeks ago—just because you have a legal right to do something doesn’t mean it’s the right business or HR decision. The legality of an action is one factor in the decision-making calculus, but not the only one.

Monday, March 26, 2012

Can we all agree that requiring Facebook passwords is a bad idea, and move on?


A lot of ink has been recently spilled in both the popular media and the blawgosphere over the apparent trend of employers requiring job applicants to turn over their Facebook passwords as part of the hiring process. The coverage has been so thick and the outrage so great that United States Senators are calling for action to outlaw this supposed practice, and Facebook officially weighed in, via a post on its blog by its Chief Privacy Officer:

If you are a Facebook user, you should never have to share your password, let anyone access your account, or do anything that might jeopardize the security of your account or violate the privacy of your friends…. That’s why we’ve made it a violation of Facebook’s Statement of Rights and Responsibilities to share or solicit a Facebook password. We don’t think employers should be asking prospective employees to provide their passwords….

If you believe all of this coverage, you would think that this practice is rampant. In reality, I would be surprise if one-percent of one-percent of all employers have even considered asking a job applicant for access to his or her Facebook account, let alone carried through on the thought by making it a hiring requirement. Simply, this is not a problem that needs fixing.

Moreover, this supposed problem isn’t even new. I covered it almost three years ago, when the city of Bozeman, Montana, made headlines by implementing, and quickly rescinding, just such a requirement. It was bad HR policy then, and it’s bad HR policy now. And, the risks of such a policy are well-documented:

    1. EEO Risks: Mining Facebook and other social sites for information on job applicants can reveal a wealth of protected EEO information (age, religion, protected medical information, genetic information). The risk is great enough when the information is publicly available; it is exponentially heightened when you gain unfettered access to information shielded by a password. For some thoughts on best practices on conducting Internet searches on applicants or employees, click here. I’ve also expansively covered this topic in my book, Think Before You Click….

    2. Stored Communications Act Risks: At least one court has concluded that an employer who requires employees to disclose passwords to social media sites violates the federal Stored Communications Act, which extends liability to parties that exceed authorization to access electronic communications. While this area of the law might be unsettled, testing it could prove a costly mistake.

      Legal issues aside, this story raises another, more fundamental, question—what type of employer do you want to be? Do you want to be viewed as Big Brother? Do you want a paranoid workforce? Do you want your employees to feel invaded and victimized as soon as they walk in the door, with no sense of personal space or privacy? Or, do you value transparency? Do you want HR practices that engender honesty, and openness, and that recognize that employees are entitled to a life outside of work?

      Social media provides a lot of benefits to employers. It opens channels of communication between employees in and out of the workplace. And, when used smartly, it enables employers to learn more about potential employees than ever before. You can learn if an employee has good communication skills, is a good cultural fit, or trashed a former employer. But, this tool has to be used smartly to avoid legal risks. Requiring passwords is not smart.

      Social media is still new, and the rules and regulations that govern it are still evolving. The government is looking for opportunities to regulate social media. If a small minority of business continues pursuing this poor HR practice, Congress will continue pursuing legislative and solutions and calling for regulatory action. Do not provide the government the opportunity. Can we all just agree that requiring Facebook passwords is a bad idea, and move on?

      Friday, March 23, 2012

      WIRTW #219 (the “madness” edition)


      Workforce Management is celebrating in 90th anniversary. To commemorate this event (and to cleverly tie-in to March’s favorite non-green event), the magazine is running its own bracket challenge. It is asking its readers to vote on two different brackets — The Pop Culture Bracket (which features such intriguing first round match-ups at Seinfeld vs. Taxi and Murphy Brown vs. Monsters, Inc.) and the Workforce Impact Bracket (which pits the FMLA against the FLSA, Gloria Steinem against Background Checks, and Social Media against ERISA, among others). Voting is being done in stages every two weeks, with round 1 open until April 1.

      For the curious:

      • In the Pop Culture Bracket, my final four vies The Office vs. Network and The Mary Tyler Moore Show vs. Philadelphia, with The Mary Tyler Moore Show taking down The Office in the finals.
      • My Workforce Impact Bracket advances The Internet to face Title VII, and AFL-CIO Teamsters to face Sexual Harassment, with The Internet edging Sexual Harassment in the finals.

      How do your brackets play out? Let me know in the comments, or on Twitter @jonhyman.

      Here’s the rest of what I read this week:

      Discrimination

      Social Media & Workplace Technology

      HR & Employee Relations

      Wage & Hour

      Labor Relations

      Until next week…