Unnecessary Boring Work: I

If you know anyone younger than 20 years old, you know first-hand how engrossing digital devices are. And if you work at a desk, among others who work at desks, you probably know how bored some of them are. They work at computers (when they aren't in meetings), doing whatever, and they're bored. The under-20s are so involved in the virtual world that they lose track of time; the desk workers are so bored that they watch that digital clock in the corner of the screen, just waiting for the thrill that comes when one of the clock's digits changes.

How can this be? The under-20s are doing something that's fun. The desk workers aren't. But why is what we do at work boring? Here are some reasons why there's so much boring work.

Insufficient automation

Although much of the boring work can be automated, deciding to invest in automation is very difficult for most organizations.

Someone would have to write, test, document, and maintain the tools that carry out the automation. And (probably) the users would have to be trained. The company would have to invest first, before it could reap rewards later in the form of higher productivity. Although the investment would be visible in the chart of accounts, the return on investment is enhanced productivity, which doesn't appear in the chart of accounts in any clearly recognizable form. But worse, the return on investment would not necessarily appear in the accounts controlled by the part of the organization that would be making the investment. This makes the politics of internal investment even more problematic.

The result is that what computers could easily do automatically must instead by done by people.

Unnecessary tasks

Eliminating unnecessary tasks is difficult because the mechanisms that create them can be complex. For example, consider policies that limit the total volume of a user's Although much of the boring work
can be automated, deciding to
invest in automation is very
difficult for most organizationsmailboxes. These policies are usually intended to save money on storage equipment. Users who approach these limits must trim the volume of their stored mail. That's work, much of it boring, necessary only because of the mailbox size policy.

Limiting mailbox size seems cheap (or even free) because the cost of compliance isn't accounted for directly. But when viewed from a more global perspective, acquiring the equipment necessary to store more mail, while sponsoring the training necessary to show employees how to reduce the bulk of their mail, is actually cheaper. Both of these tactics appear to be more expensive than mailbox size limits, because we don't account for the cost of complying with policies governing mailbox size limits.

Imposing a ceiling on stored mail volume eliminates the need to buy more storage equipment, but it does so by creating mounds of boring work, which is not accounted for. Most organizations have many tasks like this. They seem to be sensible, but they aren't.

We'll continue next time with more sources of boring work.   Next issue in this series   Top    Next Issue

Are your projects always (or almost always) late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips and techniques for organizational leaders. Order Now!

Your comments are welcome

About Point Lookout

Thank you for reading this article. I hope you enjoyed it and found it useful, and that you'll consider recommending it to a friend.

This article in its entirety was written by a human being. No machine intelligence was involved in any way.

Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.

Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.

Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.

Related articles

More articles on Personal, Team, and Organizational Effectiveness:

Should I Keep Bailing or Start Plugging the Leaks?

When we're flooded with problems, and the rowboat is taking on water, we tend to bail with buckets, rather than take time out to plug the leaks. Here are some tips for dealing with floods of problems.

Shooting Ourselves in the Feet

When you give a demo to a small audience, there's a danger of overwhelming them in a behavior I call "swarming." Here are some tips for terrific demos to small audiences.

We Are All People

When a team works to solve a problem, it is the people of that team who do the work. Remembering that we're all people — and all different people — is an important key to success.

Remote Facilitation in Synchronous Contexts: III

Facilitators of synchronous distributed meetings (meetings that occur in real time, via telephone or video) can make life much easier for everyone by taking steps before the meeting starts. Here's Part III of a little catalog of suggestions for remote facilitators.

Meeting Troubles: Culture

Sometimes meetings are less effective than they might be because of cultural factors that are outside our awareness. Here are some examples.

See also Personal, Team, and Organizational Effectiveness and Personal, Team, and Organizational Effectiveness for more related articles.

Forthcoming issues of Point Lookout

Coming May 21: Mismanaging Project Managers: Mechanics

Most organizations hold project managers accountable for project performance. But they don?t grant those project managers control of needed resources. Nor do they hold Project Sponsors or other Senior Managers accountable for the consequences of their actions when they interfere with project work. Here?s a catalog of behaviors worth looking at. Available here and by RSS on May 21.

And on May 28: Mismanaging Project Managers: Leadership

Most organizations hold project managers accountable for project performance. But they don't hold Project Sponsors or other Senior Managers accountable for the consequences of their actions when they interfere with the project manager's ability to lead the project team. Available here and by RSS on May 28.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenubcqSvusyBsQaEDwner@ChacfhuriyFKgDguTpuYoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.

Get the ebook!

Past issues of Point Lookout are available in six ebooks:

• Get 2001-2 in Geese Don't Land on Twigs (PDF, )
• Get 2003-4 in Why Dogs Wag (PDF, )
• Get 2005-6 in Loopy Things We Do (PDF, )
• Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
• Get 2009-10 in The Questions Not Asked (PDF, )
• Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )

Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500-1000 words in your inbox in one hour. License any article from this Web site. More info