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.
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 welcomeWould you like to see your comments posted here? rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.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.
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.
More articles on Personal, Team, and Organizational Effectiveness:
- Virtual Communications: I
- Participating in or managing a virtual team presents special communications challenges. Here are some
guidelines for communicating with members of virtual teams.
- Indicators of Lock-In: II
- When a group of decision makers "locks in" on a choice, they can persist in that course even
when others have concluded that the choice is folly. Here's Part II of a set of indicators of lock-in.
- The Retrospective Funding Problem
- If your organization regularly conducts project retrospectives, you're among the very fortunate. Many
organizations don't. But even among those that do, retrospectives are often underfunded, conducted by
amateurs, or too short. Often, key people "couldn't make it." We can do better than this.
What's stopping us?
- How to Get Out of Firefighting Mode: I
- When new problems pop up one after the other, we describe our response as "firefighting."
We move from fire to fire, putting out flames. How can we end the madness?
- Nine Brainstorming Demotivators: II
- Brainstorming sessions produce output of notoriously variable quality, but understanding what compromises
quality can help elevate it. Here's Part II of a set of nine phenomena that can limit the quality of
contributions to brainstorming sessions.
Forthcoming issues of Point Lookout
- Coming September 25: Planning Disappointments
- When we plan projects, we make estimates of total costs and expected delivery dates. Often these estimates are so wrong — in the wrong direction — that we might as well be planning disappointments. Why is this? Available here and by RSS on September 25.
- And on October 2: Start Anywhere
- Group problem-solving sessions sometimes focus on where to begin, even when what we know about the problem is insufficient for making such decisions. In some cases, preliminary exploration of almost any aspect of the problem can be more helpful than debating what to explore. Available here and by RSS on October 2.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.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 words in your inbox in one hour. License any article from this Web site. More info
- The Race to the South Pole: Lessons in Leadership
On 14 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. But to organizational leaders, business analysts, project sponsors, and project managers, the story is fascinating. We'll use the history of this event to explore lessons in leadership and its application to organizational efforts. A fascinating and refreshing look at leadership from the vantage point of history. Read more about this program.
Here's a date for this program:
- Baldwin-Wallace University, 275 Eastland Road, Berea, Ohio
44017: November 7,
Kerzner Lecture Series/International Project Management Day, sponsored by Baldwin Wallace University and the Northeast Ohio Chapter of the Project Management Institute.
- Baldwin-Wallace University, 275 Eastland Road, Berea, Ohio 44017: November 7, Kerzner Lecture Series/International Project Management Day, sponsored by Baldwin Wallace University and the Northeast Ohio Chapter of the Project Management Institute. Register now.
- The Power Affect: How We Express Our Personal Power
Many people who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program.