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 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
Would you like to see your comments posted here? rbrentSgXnAlNVWlhxNIJner@ChacAtZoEYrrmofzZnjPoCanyon.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.
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:
What Haven't I Told You?- When a project team hits a speed bump, it often learns that it had all the information it needed to
avoid the problem, sometimes months in advance of uncovering it. Here's a technique for discovering
this kind of knowledge more systematically.
Decisions, Decisions: II- Most of us have participated in group decision making. The process can be frustrating and painful, but
it can also be thrilling. What processes do groups use to make decisions?
The Deck Chairs of the <em>Titanic</em>: Obvious Waste- Among the most futile and irrelevant actions ever taken in crisis is rearranging the deck chairs of
the Titanic, which, of course, never actually happened. But in the workplace, we engage in
activities just as futile and irrelevant, often outside our awareness. Recognition is the first step
to prevention.
Workplace Antipatterns- We find patterns of counter-effective behavior — antipatterns — in every part of life, including
the workplace. Why? What are their features?
A Pain Scale for Meetings- Most meetings could be shorter, less frequent, and more productive than they are. Part of the problem
is that we don't realize how much we do to get in our own way. If we track the incidents of dysfunctional
activity, we can use the data to spot trends and take corrective action.
See also Personal, Team, and Organizational Effectiveness and Personal, Team, and Organizational Effectiveness for more related articles.
Forthcoming issues of Point Lookout
Coming March 19: On Lying by Omission- Of the many devious strategies of workplace politics, deception is among the most commonly used. And perhaps the most commonly used tactic of deception is lying. Since getting caught in a lie can be costly, people try to lie without lying. Available here and by RSS on March 19.
And on March 26: Seven Ways to Support Word-of-Mouth About Your Content- Whether you're making a presentation or writing an article or a book, making your material more memorable is a desirable objective. After the talk, or after the reader sets down your work, what you have to offer will be accessible only if the auditor or reader remembers something about it. Available here and by RSS on March 26.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrentSgXnAlNVWlhxNIJner@ChacAtZoEYrrmofzZnjPoCanyon.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
Follow Rick
Recommend this issue to a friend
Send an email message to a friend
rbrentSgXnAlNVWlhxNIJner@ChacAtZoEYrrmofzZnjPoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
My blog, Technical Debt for Policymakers, offers
resources, insights, and conversations of interest to policymakers who are concerned with managing
technical debt within their organizations. Get the millstone of technical debt off the neck of your
organization!
Bad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we
love the work but not the job.Learn how to make your virtual global team sing.Are you managing a change effort that faces rampant cynicism, passive non-cooperation, or
maybe even outright revolt?Learn how to make meetings more productive — and more rare.