How We Waste Time: I

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 measuresincident 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 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

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:

Finding Work in Tough Times: Communications

Finding work in tough times entails presenting yourself to many people. You'll be conversing, interviewing, writing, presenting, and when you're finally successful, negotiating.

How to Foresee the Foreseeable: Focus on the Question

When group decisions go awry, we sometimes feel that the failure could have been foreseen. Often, the cause of the failure was foreseen, but because the seer was a dissenter within the group, the issue was set aside. Improving how groups deal with dissent can enhance decision quality.

Disjoint Awareness

In collaborations, awareness of how our own work might interfere with the work of others is essential. Unless our awareness of others' work — and their awareness of ours — matches reality, the collaboration's objective is at risk.

Red Flags: I

When we finally admit to ourselves that a collaborative effort is in serious trouble, we sometimes recall that we had noticed several "red flags" early enough to take action. Toxic conflict and voluntary turnover are two examples.

Red Flags: II

When we find clear evidence of serious problems in a project or other collaboration, we sometimes realize that we had overlooked several "red flags" that had foretold trouble. In this Part II of our review of red flags, we consider communication patterns that are useful indicators of future problems.

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

Forthcoming issues of Point Lookout

Coming May 14: Working with the Overconfident

A cognitive bias known as the Overconfidence Effect causes us to overestimate the reliability of our judgments. Decisions we make based on those judgments are therefore suspect. But there are steps we can take to make our confidence levels more realistic, and thus make our decisions more reliable. Available here and by RSS on May 14.

And on May 21: Mismanaging Project Managers

Most organizations hold project managers accountable for project performance. But they don't grant those project managers control of needed resources. Nor do they hold project sponsors or other senior managers accountable for the consequences of their actions when they interfere with project work. Here's a catalog of behaviors worth looking at. Available here and by RSS on May 21.

Coaching services

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