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:

Snapshots of Squirming Subjects

Today we use data as a management tool. We store, recall, and process data about our operations to help us manage resources and processes. But this kind of management data is often scattered, out of date, or just plain incorrect, and taking a snapshot doesn't work. There is a better way.

Logically Illogical

Discussions in meetings and in written media can get long and complex. When a chain of reasoning gets long enough, we sometimes make fundamental errors of logic, especially when we're under time pressure. Here are just a few.

How to Ruin Meetings

Much has been written about how to conduct meetings effectively. Here are some reliable techniques for doing something else altogether.

Creating Toxic Conflict: II

Some supervisors seem to behave as if part of their job description is creating toxic conflict among their subordinates. It isn't really, of course, but here's a collection of methods bad managers use that make trouble.

How to Get Out of Firefighting Mode: II

We know we're in firefighting mode when a new urgent problem disrupts our work on another urgent problem, and the new problem makes it impossible to use the solution we thought we had for some third problem we were also working on. Here's Part II of a set of suggestions for getting out of firefighting mode.

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

Forthcoming issues of Point Lookout

Coming January 22: Storming: Obstacle or Pathway?

The Storming stage of Tuckman's model of small group development is widely misunderstood. Fighting the storms, denying they exist, or bypassing them doesn't work. Letting them blow themselves out in a somewhat-controlled manner is the path to Norming and Performing. Available here and by RSS on January 22.

And on January 29: A Framework for Safe Storming

The Storming stage of Tuckman's development sequence for small groups is when the group explores its frustrations and degrees of disagreement about both structure and task. Only by understanding these misalignments is reaching alignment possible. Here is a framework for this exploration. Available here and by RSS on January 29.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.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