You all know that I love telecommuting, although it works better in some instances than in others.
Before any employer starts a telecommuting program, it should ask itself three questions:
1) Does the job lend itself to a telecommuting arrangement? (You can't very well assemble Cadillac Escalades from your home office, now can you?)
2) Is the employee's home worksite conducive to work? Does the employee have proper equipment, or does she have a Commodore 64 with dial-up modem, and a rotary phone? (If the latter, are you willing to provide her with a decent set-up as part of the deal?) Is the home environment free of distractions?
Register here for our webinar, "Labor Board Takes Aim at 'Joint' Employers," which will be from 1 to 2:30 p.m. Eastern Thursday, August 21. If the National Labor Relations Board redefines the test for determining joint employer status, it will affect employers in virtually every industry and segment of the economy. Presenters will be Dan Barker, Tim Davis, Dan Murphy, and Kim Seten. Don't miss it!
and the big one, which is really the one I want to talk about today . . .
3) Is this particular employee fit to telecommute? Can she work independently? Is the quality of his work satisfactory? Is she reliable and responsible? Is he motivated, even when the supervisor isn't nearby? Has she demonstrated personal integrity?
Telecommuting works with good, reliable employees, but it can be a disaster with lazy, incompetent, or dishonest ones. If the latter have not quite been fired yet (and, if not, you ought to be working on it), do NOT let them work from home.
This post was inspired by a recent Washington Post article about an internal investigation of the acclaimed "telework" program instituted by the U.S. Patent and Trademark Office. In 2012, four whistleblowers reported that patent examiners (the people who recommend whether your invention ought to have legal protection or not) were goofing off and totally getting away with it. The USPTO conducted an investigation* and found that many examiners were committing time fraud (i.e., not working when they claimed to be working and were getting paid to work), "end-loading" (more commonly known as procrastination), and "mortgaging" their work (when they had a deadline, they'd submit incomplete or shoddy work which allowed them to meet their quota, and then finish it up - if ever - after the deadline).
*According to the Post article, the initial USPTO report linked above was later "sanitized" before being submitted to the Inspector General of the U.S. Department of Commerce. (You may need a paid subscription to be able to access the full article.)
This, in an agency that has a backlog of 600,000 patent applications and a five-year estimated waiting period.
And patent examiners are not minimum-wage workers, either. They have scientific or engineering backgrounds, and average $79,000 a year. At the top of the pay scale, they may make as much as $148,000.
The moral of the story: Don't let your marginal employees telecommute. But how can you make sure that even the average and above-average telecommuters are really working when they say they are? Here are some things to watch out for, and some suggested solutions.
Time Fraud. When you call or send your employee an email, how long does it normally take for the employee to respond? Of course, the employee may not be able to respond promptly every time, but he ought to be able to be reasonably prompt and have a good explanation for any delays. Is the employee willing to share her cell phone and home phone numbers with you? If the employee has to leave in the middle of the work day, does he notify you in advance, with an estimated time of return? If she's interrupted during the business day, do you know that she usually makes up the lost time later in the evening, or on the weekend?
In the USPTO case, some patent examiners would reportedly disappear for hours and would not take calls or respond to emails. They also apparently either did not have cell phones, or did not provide the numbers to their supervisors. Granted, the nature of their work required them to study technical material without interruption. But they should have been accessible to their supervisors as appropriate under the circumstances.
It might also be a good idea to require the examiners to enter time each day with detailed descriptions of what they did. (It's harder to cheat when you have to affirmatively lie to do it.)
I'm proud to be a member of Constangy's new e-Law Practice Group, led by Nancy Leonard and Susan Bassford Wilson, which will help employers navigate the complex landscape of the digital workplace by combining legal acumen and technical expertise. The group will cut across traditional legal practice areas and provide help with issues like social media policies, electronic discovery and document preservation, online hiring processes, and much more - including dealing with teleslackers (tehe). You can follow us on Twitter at @eLawConstangy, and join our discussion group on LinkedIn.
"End-loading"/procrastination. This is waiting until the last possible minute to get your work done before the deadline, and then dumping it all on your boss at once. "End-loading" allows the teleslacker to take the entire production period off except for the very end.
In the case of the USPTO, the patent examiners had quarterly production quotas. Their supervisors said that some examiners completed reviews at rates of 500 percent or even 1,000 percent in the last two weeks of the quarter (which shows that they were capable of getting the work done when they had to). They turned in such a heavy volume of work so close to deadlines that the supervisors could not meaningfully review it, and as a result the Thomas Edisons, Bill Gateses, and Bette Nesmith Grahams of the world were not getting the consideration their work deserved.
I am an authority on the subject of procrastination, being (ahem!) "deadline-driven" myself. Here's what you do to deal with people like me: Require smaller chunks of the work to be turned in on a weekly basis, or even a daily basis. Make the deadlines a little artificially tight, although still realistic. Accept excuses only in the most dire circumstances. Don't praise employees who meet the deadlines - that just makes them think that being late is "less than ideal but still ok" instead of "completely unacceptable." Penalize the ones who miss the deadlines. No mercy! (Well, hardly any mercy.) Quickly enough, you will stop getting 12 weeks' worth of work in two weeks.
"Mortgaging" work. This is beating the deadline by turning in sloppy work, and then fixing it later (after the work has already been counted toward meeting the quota). Easy solution: Incomplete or sloppy work will not be counted in the employee's quota and, unless there is a really good excuse, will also result in progressive discipline. The shorter deadlines discussed above ought to help with "mortgaging," too.
Those were the good solutions to teleslacking. Here are "solutions" suggested by some of the USPTO management that I think will NOT work:
Requiring employees to be signed into the VPN during work hours. First, this will not guarantee that they are working. Employees can surf the internet and goof off even when they're in the VPN. Second, VPN connections can be unreliable. Sometimes it's easier to get the work done on the "outside" and then email it back in when it's done. Your focus should be on whether the work is timely and of sufficient quality, not whether it's done inside or outside a VPN.
Requiring employees to be in their offices or at their home work stations during work hours. This is no guarantee against slacking (you can goof off in an office, and you sure as heck can goof off at home), and it unfairly penalizes employees who are doing their jobs.
Monitoring everybody. Too "Big Brother," as some of the honchos at the USPTO correctly noted. On the other hand, these same people didn't want to single anyone out, which I think is a mistake. To be fair and avoid discrimination, make sure you use objective and consistent criteria for determining who is an "alleged slacker" deserving of closer monitoring. It's fine to make distinctions among employees based on their accessibility, quality of work, and compliance with deadlines.
Did you notice how the good solutions do not require any special technology or systems upgrades? All they require is low-tech attentive management and a firm-but-fair hand. (Hmm . . . is that good, or bad?)
Some other Constangy publications from the past week that may interest you
Please, make it stop! Be sure to read Cara Crotty's latest on the proposed rule from the Office of Federal Contract Compliance Programs relating to the new "Equal Pay Report" requirement for federal contractors. What doesn't kill you will make you stronger.
- Partner
Robin has more than 30 years' experience counseling employers and representing them before government agencies and in employment litigation involving Title VII and the Age Discrimination in Employment Act, the Americans with ...
Robin Shea has 30 years' experience in employment litigation, including Title VII and the Age Discrimination in Employment Act, the Americans with Disabilities Act (including the Amendments Act).
Continue Reading
Subscribe
Contributors
- William A. "Zan" Blue, Jr.
- Obasi Bryant
- Kenneth P. Carlson, Jr.
- James M. Coleman
- Cara Yates Crotty
- Lara C. de Leon
- Christopher R. Deubert
- Joyce M. Dos Santos
- Colin Finnegan
- Steven B. Katz
- Ellen C. Kearns
- F. Damon Kitchen
- David C. Kurtz
- Angelique Groza Lyons
- John E. MacDonald
- Kelly McGrath
- Alyssa K. Peters
- Sarah M. Phaff
- David P. Phippen
- William K. Principe
- Sabrina M. Punia-Ly
- Angela L. Rapko
- Rachael Rustmann
- Paul Ryan
- Piyumi M. Samaratunga
- Robin E. Shea
- Kristine Marie Sims
- David L. Smith
- Jill S. Stricklin
- Jack R. Wallace
Archives
- November 2024
- October 2024
- September 2024
- August 2024
- July 2024
- June 2024
- May 2024
- April 2024
- March 2024
- February 2024
- January 2024
- December 2023
- November 2023
- October 2023
- September 2023
- August 2023
- July 2023
- June 2023
- May 2023
- April 2023
- March 2023
- February 2023
- January 2023
- December 2022
- November 2022
- October 2022
- September 2022
- August 2022
- July 2022
- June 2022
- May 2022
- April 2022
- March 2022
- February 2022
- January 2022
- December 2021
- November 2021
- October 2021
- September 2021
- August 2021
- July 2021
- June 2021
- May 2021
- April 2021
- March 2021
- February 2021
- January 2021
- December 2020
- November 2020
- October 2020
- September 2020
- August 2020
- July 2020
- June 2020
- May 2020
- April 2020
- March 2020
- February 2020
- January 2020
- December 2019
- November 2019
- October 2019
- September 2019
- August 2019
- July 2019
- June 2019
- May 2019
- April 2019
- March 2019
- February 2019
- January 2019
- December 2018
- November 2018
- October 2018
- September 2018
- August 2018
- July 2018
- June 2018
- May 2018
- April 2018
- March 2018
- February 2018
- January 2018
- December 2017
- November 2017
- October 2017
- September 2017
- August 2017
- July 2017
- June 2017
- May 2017
- April 2017
- March 2017
- February 2017
- January 2017
- December 2016
- November 2016
- October 2016
- September 2016
- August 2016
- July 2016
- June 2016
- May 2016
- April 2016
- March 2016
- February 2016
- January 2016
- December 2015
- November 2015
- October 2015
- September 2015
- August 2015
- July 2015
- June 2015
- May 2015
- April 2015
- March 2015
- February 2015
- January 2015
- December 2014
- November 2014
- October 2014
- September 2014
- August 2014
- July 2014
- June 2014
- May 2014
- April 2014
- March 2014
- February 2014
- January 2014
- December 2013
- November 2013
- October 2013
- September 2013
- August 2013
- July 2013
- June 2013
- May 2013
- April 2013
- March 2013
- February 2013
- January 2013
- December 2012
- November 2012
- October 2012
- September 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- October 2010