Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 16, Issue 40;   October 5, 2016: How We Waste Time: I

How We Waste Time: I

by

Time is the one workplace resource that's evenly distributed. Everyone gets exactly the same share, but some use it more wisely than others. Here's Part I of a little catalog of ways we waste time.
Astronauts Musgrave and Hoffman install corrective optics during the Hubble Telescope's Service Mission 1

Among the most famous examples of "spills" as defined here, or rework as commonly defined, is the first servicing mission to the Hubble Space Telescope, STS-61, in which astronauts installed a set of specialized lenses to correct the flawed main mirror in the telescope. The cost of the telescope itself was 2.5 Billion USD 1990. Estimates of the cost of Service Mission 1, which installed the COSTAR mirror correction system, do vary, but a reasonable range is about 30% of the telescope cost.

Photo courtesy U.S. National Aeronautics and Space Administration.

We all waste time, but some people and organizations waste time habitually, on their own, while others are forced to waste time because of someone else's mistakes. We tend to notice only the mandatory time wasting that results from the actions of others, but it's useful to catalog all causes of wasted time. That information can be a guide for investigating just how much of what we do could be avoided if we took appropriate measures.

In that spirit, here's Part I of a catalog of ways we waste time.

Make-work
The textbook definition of make-work is any activity that serves no purpose other than to keep someone busy. Supervisors do sometimes assign make-work, but I believe that most make-work is self-assigned. That is, we take on tasks that give us a sense of actually doing something, even though the output produced is of no value. For example, we sometimes devote effort to improving something that's already way past good enough. Or we produce something that might be needed later, when a little time spent in reflection could have revealed the remoteness of the chance of its ever being useful.
Rework
Rework is work that was perfectly successful the first time, but which must be done again because the result of our first effort got trashed, lost, or damaged in some way. Maybe the dog ate it. Or we accidentally deleted it. Or we delivered it to the people we were supposed to deliver it to, but they trashed it or lost it or something. Carelessness can be a cause, but often the tools we use are so finicky and badly designed that damaging mistakes happen too often.
Cleaning up and treatment after spills
A "spill" is any This catalog of ways we waste time
can be a guide for investigating
just how much of what we do
could be avoided if we took
appropriate measures
incident that creates a need to clean up or repair equipment, facilities, code, or any other factor of production. Spills can also create a need to treat personnel for injuries received. All consequences of spills count as effort. Some of it is very expensive, and little or none of it produces customer value. After-incident reviews are essential to reducing the incidence of spills.
Leaping before looking
Rushing into something injudiciously can create spills or a need for rework if the rushing led to incorrect modification of — or damage to — deliverable items that subsequently need to be restored. But a more wasteful consequence of rushing is the need to back out work that shouldn't have been done at all. In that case, the waste consists of (a) doing the wrong work; (b) doing the work required to undo the wrong work; and (c) the meetings and debates that were necessary to convince people that the work shouldn't have been done and now needs to be undone.

We'll continue next time exploring some subtler and more-often-overlooked ways we waste time.  Next in this series Go to top Top  Next issue: How We Waste Time: 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? rbrenNfkwzeDhEzXYHtJRner@ChacePNVpMEPwbTFAhOpoCanyon.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:

The Leonard P. Zakim Bunker Hill BridgeTen Reasons Why You Don't Always Get What You Measure: III
The phrase "You get what you measure," has acquired the status of "truism." Yet many measurement-based initiatives have produced disappointing results. Here's Part III of an examination of the idea — a look at management's role in these surprises.
Roger Boisjoly of Morton Thiokol, who tried to halt the launch of Challenger in 1986Towards More Gracious Disagreement
We spend a sizable chunk of time correcting each other. Some believe that we win points by being right, or lose points by being wrong, but nobody seems to know who keeps the official score. Here are some thoughts to help you kick the habit.
A Roman coin from the reign of Marcus Cocceius NervaThe Ups and Downs of American Handshakes: 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.
A centrifugal governorSixteen Overload Haiku
Most of us have some experience of being overloaded and overworked. Many of us have forgotten what it is not to be overloaded. Here's a contemplation of the state of overload.
Two barnacles affixed to the shell of a green musselSome Hidden Costs of Business Fads
Adopting business fads is an expensive organizational pattern, with costs that extend beyond what can be measured by the chart of accounts most organizations use. Here are some examples of the hidden costs of business fads.

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

Forthcoming issues of Point Lookout

The end of the line for a railroad trackComing May 30: Chronic Peer Interrupters: I
When making contributions to meeting discussions, we're sometimes interrupted. Often, the interruption is beneficial and saves time. But some people constantly interrupt their peers or near peers, disrespectfully, in a pattern that compromises meeting outcomes. How can we deal with chronic peer interrupters? Available here and by RSS on May 30.
Mohandas K. Ghandi, in the 1930sAnd on June 6: Chronic Peer Interrupters: II
People use a variety of tactics when they're interrupted while making contributions in meetings. Some tactics work well, while others carry risks of their own. Here's Part II of a little survey of those tactics. Available here and by RSS on June 6.

Coaching services

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

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 Power Affect: How We Express Our Personal Power
Many The Power Affect: How We Express Personal Powerpeople 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. Here's a date for this program:

Technical Debt Management: Making the Business Case
This Technical Debt Management: Making the Business Caseprogram outlines the steps necessary for deploying a program for rational management of technical debt. For many organizations, adopting a program for rationally managing technical debt entails organizational change. And unlike some organizational changes, this one touches almost everyone in the organization, because technical debt isn't merely a technical problem. Technical debt manifests itself in technological assets, to be sure, but its causes are rarely isolated to the behavior and decisions of engineers. We can't resolve the problem of chronically excessive levels of technical debt by changing the behavior of engineers alone. Technical debt is the symptom, not the problem. In this program we outline the essential elements of an effective business case for adopting a rational technical debt management program. But this business case, unlike many business cases, cannot be captured in a document. We must make the case not only at the leadership level of the organization, but also at the level of the individual contributor. Everyone must understand. Everyone must contribute. We explore five issues that make technical debt so difficult to manage, and develop five guidelines for designing technical debt management strategies for the modern enterprise. Read more about this program. Here's a date for this program:

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 a date for this program:

The Power Affect: How We Express Our Personal Power
Many The Power Affect: How We Express Personal Powerpeople 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. Here's a 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
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy 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!
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.