Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 14, Issue 30;   July 23, 2014: Unnecessary Boring Work: Part I

Unnecessary Boring Work: Part I

by

Work can be boring. Some of us must endure the occasional boring task, but for many, everything about work is boring. It doesn't have to be this way.
Industrial robots assembling automobiles

KUKA industrial robots assembling automobiles. Industrial robots have taken over much of the boring and dangerous work in factories. They have done so, in part, because the human labor they replaced was visible in the manufacturers' accounting systems, which made the decision to automate much easier. Desk work is different. Automating desk work also results in savings, but because the automation doesn't replace everything the human does, the accounting system is unable to easily display the savings. Photo (cc) Mixabest, courtesy Wikimedia.

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 organizations
mailboxes. 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 in this series  Go to top Top  Next issue: Unnecessary Boring Work: Part II  Next Issue

52 Tips for Leaders of Project-Oriented OrganizationsAre 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

Would you like to see your comments posted here? rbrenEhynLEphDEzqhNDhner@ChacagZjKdmKoQwdpZjOoCanyon.comSend me your comments by email, or by Web form.

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.

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:

A time ManagerRecovering Time: Part II
Where do the days go? How can it be that we spend eight, ten, or twelve hours at work each day and get so little done? To find more time, focus on strategy.
The Town of Wescott, Wisconsin is recognized as Tree City 2005Workplace Myths: Motivating People
Up and down the org chart, you can find bits of business wisdom about motivating people. We generally believe these theories without question. How many of them are true? How many are myths? What are some of these myths and why do they persist?
The rabbit that went down the rabbit-holeOur Last Meeting Together
You can find lots of tips for making meetings more effective — many at my own Web site. Most are directed toward the chair, or the facilitator if you have one. Here are some suggestions for everybody.
Heiltskuk Icefield, British ColumbiaFinding the Third Way
When a team is divided, and agreement seems out of reach, attempts to resolve the conflict usually focus on the differences between the contrasting positions. Focusing instead on their similarities can be a productive technique for reaching agreement.
An A-10 Thunderbolt II over Afghanistan in 2011Down in the Weeds: Part I
When someone says, "I think we're down in the weeds," a common meaning is that we're focusing on inappropriate — and possibly irrelevant — details. How does this happen and what can we do about it?

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

Forthcoming issues of Point Lookout

A Great Grey OwlComing June 29: How to Waste Time in Virtual Meetings
Nearly everyone hates meetings, and virtual meetings are at the top of most people's lists. Here's a catalog of some of the worst practices. Available here and by RSS on June 29.
An actual bandwagon in a circus paradeAnd on July 6: Cognitive Biases and Influence: Part I
The techniques of influence include inadvertent — and not-so-inadvertent — uses of cognitive biases. They are one way we lead each other to accept or decide things that rationality cannot support. Available here and by RSS on July 6.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrengGiRHGWqbbnCSHZrner@ChacbMzoYJJHXygXifhzoCanyon.com or (617) 491-6289, or toll-free in the continental US at (866) 378-5470.

Get the ebook!

Past issues of Point Lookout are available in six ebooks:

Reprinting this article

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 words in your inbox in one hour. License any article from this Web site. More info

Public seminars

The Race to the South Pole: The Power of Agile Development
On 14The Race to the Pole: An Application of Agile Development December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough. Lessons abound. Among the more important lessons are those that demonstrate the power of the agile approach to project management and product development. Read more about this program. Here's an upcoming date for this program:

Managing in Fluid Environments
Most Managing in Fluid Environmentspeople now work in environments that can best be characterized as fluid, because they're subject to continual change. We never know whats coming next. In such environments, managing — teams, projects, groups, departments, or the enterprise — often entails moving from surprise to surprise while somehow staying almost on track. It's a nerve-wracking existence. This program provides numerous tools that help managers who work in fluid environments. Read more about this program. Here's an upcoming date for this program:

Sudoku Solutions, INK: A Simulation of a Project-Oriented Organization
In thCross-Functional Teams: How Organizations Actually Workis workshop, we simulate a company that solves Sudoku puzzles for its customers. Each puzzle is a project, solved by a project team led by a project manager. Team members hail from different parts of the organization, such as QA or the Department of Threes. Puzzles have different values, and the company must strive to meet revenue goals. The metaphor is uncanny. Lessons abound. Read more about this program. Here are some upcoming dates for this program:

Changing How We Change: The Essence of Agility
MasteChanging How We Change: The Essence of Agilityry of the ability to adapt to unpredictable and changing circumstances is one way of understanding the success of Agile methodologies for product development. Applying the principles of Change Mastery, we can provide the analogous benefits in a larger arena. By exploring strategies and tactics for enhancing both the resilience and adaptability of projects and portfolios, we show why agile methodologies are so powerful, and how to extend them beyond product development to efforts of all kinds. Read more about this program. Here's an upcoming date for this program:

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Twitter, or share a tweet Follow me at Google+ or share a post Subscribe to RSS feeds Subscribe to RSS feeds
Please donate!The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
How to Spot a Troubled Project Before the Trouble StartsLearn how to spot troubled projects before they get out of control.
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.