Remote Work Productivity

How Task Overlap Wastes Productivity, and How One Simple List Can Stop It

“Everyone does a little bit of everything here.” It’s a common saying in startups, and some small businesses. Harmless, right?

No. If you have remote workers, you need to stamp that practice out.

It will hurt your company’s productivity and cost you valuable time. I’ll elucidate how in this post.

Productivity Drain Warning: Task Overlap

Let’s illustrate an example here. We have a business where everyone works remotely. One worker, Bob, can do a certain task. I’ll use “populating SEO metadata on webpages” in this case.

SEO population is not Bob’s primary job. But he can do it. Now, another worker, Sarah, does SEO population as part of her regular weekly tasks.

However, not everyone in the company knows this.

Jeff, Sarah’s manager, does know about Sarah’s SEO population duty. Bob does not. Bob’s manager Anna doesn’t either.

Problem: Anna receives a task request for SEO population. Her mind, of course, goes to Bob. She asks Bob to do it.

Because Bob doesn’t know Sarah can populate SEO (and regularly does), he goes ahead & does it. It takes him 15 minutes because he’s not accustomed to doing it regularly. Two days later, Sarah does her regular SEO population for all clients. It only takes her 5 minutes per task. Along the way, she sees that one population was already done. Curious, she takes 3 minutes and finds out Bob did it.

Bob has wasted his effort and 15 minutes of time. Sarah has wasted 3. This is what I mean by Task Overlap.

Frustrated Remote Worker

I wasted HOW long doing that??

Be Specific on Who Does What, to Avoid Task Overlap

If people do many things/skills, and are not expressly aware of everyone else’s duties, then they can overlap with others. Causing wasted productivity each time. Only a little time, as we saw above. But that can add up fast.

Imagine if you could get 1 extra hour of productivity, per person, per month. That’s a big chunk of useful time.

Regular thorough communication can help avoid Task Overlap to a large degree. But it’s not as effective as specifying everyone’s duties.

How to ID Remote Workers’ Specialties

Here’s a way to solve the Task Overlap issue. You only need a little time, documentation, and a shared workspace (e.g. a wiki, Asana, etc.).

  1. Survey every remote worker. Ask them to list their specialties and their regular duties.
  2. Document all of these in 1 big list. Separate by type and person. I’ve worked up an example in the below image:

    Remote Work Duties & Specialties List

    Duties and Specialties for Bob & Sarah. At-a-glance Task Overlap prevention.

  3. Publish the list somewhere ALL workers, remote or otherwise, have access to.
  4. Require all workers to view & bookmark the list.
    • Everyone can refer to this whenever they receive a new task.
  5. Update the list quarterly. You can just re-run the previous process to check in with everyone.
  6. When you do update the list, send an email reminder around so everyone knows to check it again.

Let’s go back to our earlier example. Anna receives a request for SEO metadata population. She checks the list. Sees that Bob has SEO population listed as a Specialty…but Sarah has SEO Population under Duties.

Anna forwards the request to Jeff, who adds it to Sarah’s regular weekly task list. Time? Maybe 3 minutes. Productive time wasted? Zero.

Clarity on Who Does What Saves Time AND Productivity

Don’t get me wrong…it’s good to have multi-skilled people on your team! Especially in a remote work environment. That way another person can step in to help if someone’s out sick, or on vacation.

You just don’t want to mis-target their efforts, over and over.

In a Remote Work environment, people sometimes feel they’re the “only one who can do this.” One simple list can explain otherwise, AND let them focus on what they do best.

Does your company document people’s duties/specialties?

IBM and Remote Work

IBM has decided to cancel its remote worker policy.
Extraordinarily bad idea. I’ll illustrate why.

IBM, remote-work pioneer, is calling thousands of employees back to the office – Quartz.com

IBM’s Current State: Unwell

Let’s frame the entire discussion right now. IBM as a company is not doing well. They’ve had 20 straight quarters of revenue decline, right up to Q1 2017 (which ended right as they made this announcement).

IBM stock tumbles as year-over-year revenue declines for 20th consecutive quarter – CNBC

Now, I like the Watson project. I almost can’t overstate its value to medical professionals and research teams. But even with Watson and cloud sales improving, IBM can’t pull themselves out of a LONG slump.

I find this very telling, in regards to their remote work termination.

The Reasons Given: Lofty and Shaky

Sources cited in the Quartz article talk about innovation and productivity gains. About IBM needing to be faster, more ‘agile.’

ibm photo

Used to use one of these…ahh, days gone by.
Photo by byzantiumbooks

“What IBM should value most, says John Sullivan, a professor of management at San Francisco State University who specializes in HR strategy, are better ideas. ‘It turns out the value of innovation is so strong that it trumps any productivity gain,’ he says, pointing to companies like Apple and Facebook that make around $2 million per employee (IBM makes about $200,000 for each employee). ‘[Remote work] was a great strategy for the 90s and the 80s, but not for 2015.’ He thinks that working together in person is one key to innovation.”

The comparison Professor Sullivan uses is, quite frankly, laughable. IBM already has to collaborate with ‘remote’ locations–its multiple worldwide offices! The marketing department alone has 6 offices across the U.S. ‘Working together in person’ is not possible.

(It’s also notable that the quote came from 2015…IBM had to go back 2 years to find it, apparently.)

Other sources appear to rail against remote work…Yahoo’s similar cancellation, Reddit’s demand that all employees relocate to San Francisco. The fact that Yahoo and Reddit both experienced severe trouble (and Yahoo’s ultimate collapse) are not mentioned.

The QZ.com author, Ms. Kessler, tries to show a bright side to the move. (The article itself is good; I always like seeing great writing.) But an upbeat article won’t make the truth go away.

Who made this ridiculous decision?

The Decision’s Sponsor: IBM’s New CMO

Michelle Peluso is IBM’s Chief Marketing Officer. She came on board in September of 2016. From the available information, it appears she set out to destroy IBM’s remote work policy from Day 1.

“In a video message, Peluso, formerly the CEO of fashion startup Gilt, explained the ‘only one recipe I know for success.’ Its ingredients included great people, the right tools, a mission, analysis of results, and one more thing: ‘really creative and inspiring locations.'”

Wait a minute. The only recipe she knows for success…from a fashion company? IBM is about as far from fashion as you can get. It’s not reasonable to presume the tactics used in a fashion company will work in a technology giant like IBM.

Another thing to point out…she’s the IBM Chief MARKETING Officer.

That’s not an HR position…she shouldn’t have anything to do with hiring & firing. She has no technical experience either. Yet she’s the one making a company-wide decision affecting thousands of technology workers?

This makes no sense at all! What’s the real reason behind IBM’s move?

Using Remote Work as a Scapegoat for Cost-Cutting

When we think about it,it’s pretty easy to see what’s really going on here. It’s all a cost-cutting effort.

  1. Declare an end to the remote work policy.
  2. Assign remote workers to a physical office. The office could be in a totally different city from your home. For example, say you work out of a Boston suburb. Your job is now assigned to the Austin office…and you have to show up.
  3. IBM has now created a circumstance where remote workers quit, since they can’t reach the office. If you don’t want to move? You’re fired.
  4. Profit?

The thing is, they’ve already done layoffs. Thousands of them, just in the past 12 months. It didn’t help their costs. This move won’t either…and in fact may do structural damage to the company.

What Happens to IBM Next?

Maybe some of the talent lost wasn’t so good. If so, a simple layoff would suffice. But a move like this sends a powerful message…a very, very bad one. To the world at large, and to the remaining IBM employees.

The remaining talent…the skilled engineers, good programmers, and so on…now know they can get dumped too. Nobody is safe from Peluso’s “improvements.” What will the skilled workers do in response? If I were any of them, I’d run for the exit as fast as possible!

Thousands of companies will happily slurp up IBM’s talent. Not only do they gain highly-skilled workers, they cause IBM damage. In trying to bolster its own innovation, IBM has sent a shockwave through its own halls.

In terms of short-term effect, here’s what I predict. Any IBM department which must reabsorb formerly-remote workers into their on-site workflows, will slow down. Workflows must change, space must be made, relationships built or rebuilt. The day-to-day of people moving about will drag down productivity.

Of course, this causes the opposite of what Peluso claims she wants. Unless she was only after destroying the remote work policy…in which case, anything that happens afterward is not her problem.

Could IBM Reverse the Remote Work Decision?

Is such a decision reversible? Yes, and that’s the best move. Reinstitute the remote worker policy. Do it companywide, right away.

But, even if they did so tomorrow, the damage is done. It would help them in the long run. But they’ve already burned their most important bridge…the one to their talent.

Even if invited back, some of the remote workers cut by this move will not return. (Nor should they; IBM has declared they don’t trust or want you.) That means IBM has to spend more time/money training new people…wasting all the time/money they already spent on the departing workers.

IBM now has to re-home thousands of workers, paying power costs, growing the needed office space, and raising pollution in every city affected.

crowd photo

“This is my office.” “No, this is my office.” “It’s my office too!”
Photo by markhillary

The sad thing is, IBM once enjoyed incredible boosts from their remote work policy. Not just in productivity, but in ACTUAL cost savings. The article even mentions this!

“And by 2009, when remote work was still, for most, a novelty, 40% of IBM’s 386,000 global employees already worked at home (the company noted that it had reduced its office space by 78 million square feet and saved about $100 million in the US annually as a result).”

Hundreds of millions in savings. Now destroyed, rendered moot.

A Bad Move by a Troubled Company

I give credit to the Captain Capitalism blog for pointing out the Quartz article. The man is brusque, but he knows his economics. Take heed.

My final word: IBM has destroyed a remote work policy that brought them provable gains, because a fashion exec says it’ll save the entire company. The IBM decision-makers are either voluntarily ignorant, or they think they’re above the market.

20 straight quarters of declining revenue says they are wrong.

What do you think?