Unnecessary Boring Work: Part II
by Rick Brenner
Workplace boredom can result from poor choices by the person who's bored. More often boredom comes from the design of the job itself. Here's Part II of our little catalog of causes of workplace boredom.
A stretch of the Amazon rain forest showing storm damage. In a study of the forest conducted by NASA and Tulane University, it was found that violent storms from January 16 to 18, 2005, killed approximately half a billion trees. The study is significant not only for its findings, but also because it was the first instance in which researchers calculated how many trees a single thunderstorm can kill, according to Jeffrey Chambers, who is a forest ecologist at Tulane and one of the authors of the paper. In the photo, you can see trunks of trees made visible by the loss of their neighbors. Prior to the study, it was believed that the losses were due to drought. But by combining ground observations, modeling, and LandSat imagery, the researchers were able to calculate tree losses.
An accurate assessment of what happened in the Amazon in 2005 was possible only by combining information about the forest obtained at different scales — both ground and satellite observations were required. In organizational process design, too often we use data from only one scale — either local or global. The result is a process architecture that makes sense at one scale — that at which it was designed — but not at the other scale. Sensible process design requires careful analysis at both local and global scales.
Photo by Jeffrey Chambers, courtesy NASA.
Workplace boredom is to some extent the responsibility of the bored, who sometimes make choices that lead to boredom. For example, by exploiting capabilities already provided in the software we use most, we can eliminate much of the boring work we do. To do so, we must learn to make better use of the tools we have. Some of us are averse to learning, and many feel too pressed for time to learn.
Most employers can help more than they do. The net cost of training is zero or negative for many employers, because productivity increases offset the costs. But employers who use contractors, or who accept high turnover rates resulting from abominable working conditions, get little benefit from training, and therefore find the investment unjustifiable. It's a vicious cycle.
But the most fertile source of workplace boredom is the design of the work itself. Here are three examples.
- Wasteful workflows
- I've actually encountered cases in which people print documents "for the record," file one copy, and attach another to a package to be passed to the next stage of processing in another department, where it's scanned "for the record." We like to believe that such cases are rare, but they do exist. Even when all stages are electronic, the steps might not make sense from a whole-organization perspective. When organizational processes have wasteful steps, the real problem isn't the process or the boring work it creates. Rather, it's a failure of organizational leaders to see the organization as a whole.
- Cost management
- In some organizations, people of proven capability are paid very well on an annual basis. But on an hourly basis, not so much. Often they work 60- or 70-hour weeks. Possibly this happens because cost management measures make hiring enough knowledgeable people difficult. The result is that people who do have knowledge don't have time to transfer what they know to the less knowledgeable. And the less knowledgeable don't have time to learn, because they're loaded down with the more routine, boring work, which might be automated if time permitted. Thus, cost management prevents the knowledge transfer needed to reduce the amount of boring work and increase productivity.
- The illusion of cost control
- Cost control The most fertile source of
workplace boredom is the
design of the work itselfmeasures, such as layers of approvals and positional expenditure limits, are often too stringent. Whether they're actually effective is an open question, for two reasons. First, they create (boring) and costly work both for the people who must seek approvals and for the people whose approvals they seek. Second, they reduce the velocity of work, because the approvers are often busy people who cannot respond to requests in a timely fashion. Reduced velocity leads to delays, which become lost sales, delayed revenue, increased customer frustration, and reduced market share.
Well, enough of this. I don't want to bore anybody. First 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
Would you like to see your comments posted here? rbrenvVgLQmizhNeWBhOxner@ChacsXSfteVrJXlrAiJDoCanyon.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.
More articles on Personal, Team, and Organizational Effectiveness:
- Status-Report as a Second Language
- Sometimes, the clichés the losing team's players feed to sports reporters can have hidden meaning. So it is with Project Status Reports, especially for projects in trouble.
- When the job market eases for job seekers, we often see increases in job shifting, as people who've been biding their time make the jump. Typically, they're the people we most want to keep. How can we reduce this source of turnover?
- The Questions Not Asked
- Often, the path to forward progress is open and waiting, but we don't recognize it, or we convince ourselves it isn't there. Learning to see what we believe isn't there is difficult. Here are some reasons why.
- The Ups and Downs of American Handshakes: Part I
- In much of the world, the handshake is a customary business greeting. It seems so simple, but its nuances can send signals we don't intend. Here are some of the details of handshakes in the USA.
- The Reification Error and Performance Management
- Just as real concrete objects have attributes, so do abstract concepts, or constructs. But attempting to measure the attributes of constructs as if they were the attributes of real objects is an example of the reification error. In performance management, committing this error leads to unexpected and unwanted results.
See also Personal, Team, and Organizational Effectiveness and Project Management for more related articles.
Forthcoming Issues of Point Lookout
- Coming September 2: That Was a Yes-or-No Question: Part II
- When, in the presence of others, someone asks you "a simple yes or no" question, beware. Chances are that you're confronting a trap. Here's Part II of a set of suggestions for dealing with the yes-or-no trap. Available here and by RSS on September 2.
- And on September 9: Holding Back: Part I
- When members of teams or groups hold back their efforts toward achieving group goals, schedule and budget problems can arise, along with frustration and destructive intra-group conflict. What causes this behavior? Available here and by RSS on September 9.
I offer email and telephone coaching at both corporate and individual rates.
Contact Rick for details at rbrenaYsiMgjPPubPGlGsner@ChacQzlZJQNgwGlwSeRxoCanyon.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
- Ten Project Management Fallacies: The Power of Avoiding Hazards
- Most of what we know about managing projects is useful and effective, but some of what we know "just ain't so." Identifying the fallacies of project management reduces risk and enhances your ability to complete projects successfully. Even more important, avoiding these traps can demonstrate the value and power of the project management profession in general, and your personal capabilities in particular. In this program we describe ten of these beliefs. There are almost certainly many more, but these ten are a good start. We'll explore the situations where these fallacies are most likely to expose projects to risk, and suggest techniques for avoiding them. Read more about this program. Here's an upcoming date for this program:
- Managing in Fluid Environments
- Most people 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 are some upcoming dates for this program:
- Download to
your calendarCharleston, South Carolina: October 15, Monthly Meeting, Charleston Chapter of the Project Management Institute. Register now.
- Download to
your calendarMITRE, in Bedford, MA: November 17, Monthly Meeting, Boston SPIN. Register now.
- Wherever you are: it's a webinar: May 4, 2016, Webinar, IT Metrics and Productivity Institute. Register now.
- The Race to the South Pole: The Organizational Politics of Risk Management
- 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 risk management, its application to organizational efforts, and how workplace politics enters the mix. A fascinating and refreshing look at risk management from the vantage point of history and workplace politics. Read more about this program. Here's an upcoming date for this program:
- Team Development for Leaders
- Teams at work are often teams in name only — they're actually just groups. True teams are able to achieve much higher levels of performance than groups can. In this program, Rick Brenner shows team leads and team sponsors the techniques they need to form their groups into teams, and once they are teams, how to keep them there. Read more about this program. Here's an upcoming date for this program: