Monday, December 2, 2013

Sometimes, employees get what they deserve


At 10:35 Saturday morning, I was stopped at an intersection on my way home from dropping my daughter off at her band rehearsal. From the passenger seat of the car stopped next to me in the left-turn lane emerged a guy, mid-twenties, clad in Ohio State gear and holding a beer. After he slid out of the open door, he proceeded to start dancing in the middle of the intersection while “Hang on Sloopy” blared from the car’s radio. After a minute or so of this folly, the red light turned to a green arrow, he jumped back on the car, and it spend around the turn with his door still open.

My thoughts of what an ass this guy was quickly turned to cheers for justice as I saw the blue-and-reds of a police car fly past me to pull over the dancing fool. I didn’t stick around to see the end of the story, but my hope is that he missed Ohio State’s last-second victory over Michigan from the confines of the police station’s lockup. 

This guy clearly got what he deserved. No one should feel any sympathy that this early-morning partying clown likely missed the Ohio State / Michigan game. Yet, everyday, employers take pity on poor-performing employees. 

It’s okay to fire an employee. If expectations are communicated and not met, if an employee understands what needs to be done to succeed and misses the mark, or if an employee does not improve after a sufficient number of chances, then it‘s okay to let an employee go. Employers, however manage from a culture of fear. They fear lawsuits, which, in turn, paralyzes employment decisions. As a result, mediocre employees (or worse) keep their jobs. 

As we approach the new year, I’d like employers to resolve to break this chain of mediocrity. It’s okay to fire someone, as long as you’re not motivated by an illegal reason. Communicate your expectations, give your people a fair and reasonable chance to meet them, and, if they fail, cut bait. No one feels bad for the dancing Ohio State fan; don’t feel bad for the poor employee who has’t worked out. 


Tuesday, November 26, 2013

It’s a four-peat—ABA Journal again names the Ohio Employer’s Law Blog to its list of the top 100 legal blogs #Blawg100


The list of pro sports teams that have four-peated their respective championships is a short one:

  • New York Yankees
  • Boston Celtics
  • Montreal Canadiens
  • New York Islanders

It’s a rare feat indeed.

Thus, I am humbly honored that the ABA Journal has, for the fourth year in a row, named me to its list of the top 100 legal blogs, simply known as the Blawg 100.

According to the ABA Journal, the criteria for inclusion are “blawgs that are regularly updated, contain original content, opinion and/or analysis. Many are also on our radar because the Journal staff finds the posts useful in terms of tipping us off to news or generating posts we consider worthy of coverage.” As for me, the ABA Journal says that I’m included because of my “frank and conversational style of writing, and “the quality of analysis.” Yes, ABA Journal, I’m blushing.

My blog is listed alongside six others in the “Labor & Employment” category (the most robust blawging community, if you ask me), each of which is very deserving of inclusion (in no particular order): Dan Schwartz’s Connecticut Employment Law Blog (and congrats to Dan for his enshrinement in the Blawg 100’s Hall of Fame), Molly DiBianca’s Delaware Employment Law Blog, Eric Meyer’s The Employer Handbook, Jeff Nowak’s FMLA Insights, Donna Ballman’s Screw You Guys, I’m Going Home, and Seyfarth Shaw’s Trading Secrets. I am particularly proud to be in this group because I consider many of these people to be friends, friendships which developed out of our blogs.

So, as we move towards Thanksgiving, I am especially thankful to all of you who have read what I’ve written for the past six and a half years. Cheers! I’ll see everyone back on Monday, as we start the march to number five.

(If you are inclined to cast votes for your favorites among the Blawg 100, you can do so here, registration required).

Monday, November 25, 2013

Social media background checks as discrimination


I’ve long argued that employers take a risk when they use social media to vet job candidates without putting in place sufficient controls to prevent the disclosure of protected EEO information. Now, we have the empirical evidence to back me up.

Last week, the Wall Street Journal reported on a research study conducted by Carnegie Mellon University:

The study, … involving dummy résumés and social-media profiles, found that between 10% and a third of U.S. firms searched social networks for job applicants' information early in the hiring process. In those cases, candidates whose public profiles indicated they were Muslim were less likely to be called for interviews than Christian applicants. The difference was particularly pronounced in parts of the country where more people identify themselves as conservative. In those places, Christian applicants got callbacks 17% of the time, compared with about 2% for Muslims.

Thus, even though employers avoid asking applicants about taboo hiring subject such as religion, social media profiles, which might contain information such as quotes from religious tests or a “like” for one’s place of worship, could lead to the inadvertent discovery of an applicant’s religion, opening the door to unconscious and unintentional biases. 

What is the answer to this problem? According to one lawyer quoted in the WSJ article, “[I]t’s not a good idea to use social media as a screening tool.” 

That view, however, is short-sighted. It ignores all of the valid, legal information one can learn about an applicant from their social media pages—references to illegal drug use, posts of sexual or racist nature, poor communication skills, the disclosure of confidential information, or the trashing of an old boss or employer. The trick is discovering this “good” information while, at the same time, screening out the “bad” protected EEO information. How does a company accomplish this task? My answer to this question hasn’t changed:

Don’t let anyone in the chain of hiring view candidates’ social media profiles. Train an employee who is insulated from the hiring process to do your social media searches, scrub all protected information, and provide a sanitized report to those responsible for making the hiring decision. That way, no one can argue that protected information posted on a social network illegally influenced a hiring decision.

For more information on this timely and important issue, please join me on December 5 at 1:00 pm, when I’ll be the special guest on a webinar hosted by Newton Software, entitled, Avoiding the Biggest Pitfalls of Social Recruiting.

Friday, November 22, 2013

WIRTW #298 (the “thankful” edition)


medium_6643935221

My daughter’s homework last night was to interview five people about what they are thankful for, and summarize the interviews in a short book. She chose to ask her brother, her grandparents, her guitar teacher, and our dog (bonus points for second-grade creativity). Since I did not get the chance to participate, I thought I’d use this space to list what I’m thankful for this year.

A loving and supportive wife, two amazing children, health and happiness, that my children still have all four of their grandparents, doggie daycare, my firm (which has been overwhelmingly supportive of this blog for six and a half years), and all of my subscribers, readers, and followers.

If you’re so inclined, feel free to share your list in the comments below, or on Twitter with the hashtag #OELBThankful

Happy Thanksgiving to everyone. I’ll have fresh content Monday and Tuesday, and will be taking the rest of next week off.

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

Discrimination

Social Media & Workplace Technology

HR & Employee Relations

Wage & Hour

Labor Relations

photo credit: rustiqueart via photopin cc

Thursday, November 21, 2013

Are graduate assistants employees or students?


In Al-Maqablh v. University of Cincinnati College of Medicine (11/5/13), an Ohio federal court answered the question of whether graduate assistants are employees entitled to the protections of Title VII. As with most legal question, the answer depends.

The case concerned the race and national origin claims of a grad student placed on academic probation and ultimately dismissed from the University. Al-Maqablh sought Title VII’s protections as an employee because he “received a paycheck from the University and rendered services to the University by performing extensive research through lab work.” The court, however, disagreed:

Plaintiff received a stipend and/or scholarship after being accepted into the Program. Plaintiff has failed to show that this pay stub was based upon is employment with the University and not a portion of his stipend award. Furthermore, the fact that Plaintiff performed extensive research, as required under the Program, does not make him an employee under Title VII.

Instead, the court looked to the “economic realities” of the relationship between Al-Maqablh and the University to determine whether he was an employee or a student:

Plaintiff participated in the Graduate Program as a student engaging in “courses, seminars and laboratory research during the academic year.” … More importantly, the dominant purpose of Plaintiff’s relationship with the University was educational. Plaintiff’s complaint against the University asserts claims solely related to his academic activities as a graduate student…. [T]he undisputed evidence establishes that the University’s decision to dismiss Plaintiff from the Graduate Program was an academic decision unrelated to Plaintiff’s alleged employment with the University. As such, the undersigned finds that Plaintiff should not be considered an employee under Title VII....

Thus, in this case, the graduate assistant was a student, not an employee. The court made the point, however, that this rule is not universal; the status of a graduate assistant must be analyzed based on the “economic realities” of each individual. If the University had paid Al-Maqablh for his services (as opposed to providing him an academic scholarship), or if the University had dismissed him for an employment reason, as opposed to an academic, reasons, this case likely would have turned out differently.

If you are an educational institution using the services of graduate assistants, do not make this mistake of reading this decision as providing carte blanche to discriminate against graduate assistants (indeed, Title IX would instruct you differently). Instead, understand that these rules are fact specific, and seek legal counsel to guide your actions accordingly.

 

Wednesday, November 20, 2013

The email curfew for wage-and-hour compliance


small_5145406269As a company you’re doing everything you can to attract and retain young talent, including implementing a broad BYOD policy enabling your Gen-Yers to connect their iDevices to your network. If those employees are non-exempt under the wage-and-hour laws, how do you prevent them from claiming overtime wages for the off-the-clock time they spend receiving, reading, and sending work-related emails?

Have you heard of an email curfew? Me neither, until I read this article in the Kansas City Business Journal (h/t Today’s General Counsel). Here’s the concept:

The law requires employees to be paid for work that their boss either knew or should have known they were doing. If the boss had no reason to know or suspect employees weren’t complying with the curfew, they could be protected.

In other words, you draft a policy (either stand-alone, or as part of your technology or BYOD policies) prohibiting non-exempt employees from emailing off-duty.

At least one management-side lawyer, quoted in the K.C. Business Journal article, is skeptical of using these curfews as a wage-and-hour compliance tool.

“While an email curfew is a clever idea that might in certain circumstances be justified, it typically isn’t going to be much of an answer.” That’s because in most cases it’s unenforceable or could potentially anger clients who might find other companies that are willing to respond to requests 24/7.

I’m not nearly as cynical about the effectiveness of an email curfew to stave off wage-and-hour issues for off-the-clock emailing. If you tell employees not to read, send, or otherwise work on emails off work hours, and an employee disobeys, that employee is subject to being disciplined. Yes, you still have to pay him or her for the “working” time (which would be at a time-and-a-half premium if the typical work week totals 40 hours), but punishing one employee for violating an email curfew will go a long way to deterring the many from future violations.

The more difficult issue, however, is balancing the need for instant access versus the cost of paying your employees for that responsiveness. This business decision will vary from company to company (based, in part, on a company’s culture), and will dictate how you react to this compliance idea.

photo credit: Thomas Hawk via photopin cc

Tuesday, November 19, 2013

EEOC tackles national-origin discrimination


Have you seen the story about the employee at an Ephrata, Washington, Burger King, fired for posting, “Now Hiring Must Be Mexican” on the store’s marquee?


This story is particularly timely, since last week, the EEOC held a public meeting addressing issues with national-origin discrimination. 

The seven speakers highlighted various issues, including the plight of immigrants, harassment, English-only policies, and the challenges facing multi-cultural workplaces. 

America’s workforce will continue to personify our melting-pot moniker. Employers need to u detests nd and pay attention to these issues of national-origin discrimination, if for no other reason than the fact that the EEOC is watching, and litigating enforcement actions when necessary.