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

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:

There Is No Rumor Mill

Rumors about organizational intentions or expectations can depress productivity. Even when they're factually false, rumors can be so powerful that they sometimes produce the results they predict. How can we manage organizational rumors?

Recalcitrant Collaborators

Much of the work we do happens outside the context of a team. We collaborate with people in other departments, other divisions, and other companies. When these collaborators are reluctant, resistive, or recalcitrant, what can we do?

Coping and Hard Lessons

Ever have the feeling of "Uh-oh, I've made this mistake before"? Some of these oft-repeated mistakes happen not because of obstinacy, or stupidity, or foolishness, but because the learning required to avoid them is just plain difficult. Here are some examples of hard lessons.

Contextual Causes of Conflict: II

Too often we assume that the causes of destructive conflict lie in the behavior or personalities of the people directly participating in the conflict. Here's Part II of an exploration of causes that lie elsewhere.

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.

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

Forthcoming issues of Point Lookout

Coming October 23: Power Distance and Teams

One of the attributes of team cultures is something called power distance, which is a measure of the overall comfort people have with inequality in the distribution of power. Power distance can determine how well a team performs when executing high-risk projects. Available here and by RSS on October 23.

And on October 30: Power Distance and Risk

Managing or responding to project risks is much easier when team culture encourages people to report problems and question any plans they have reason to doubt. Here are five examples that show how such encouragement helps to manage risk. Available here and by RSS on October 30.

Coaching services

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

Public seminars

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

• A recording of a program presented June 29, 2017, Monthly Webinar, sponsored by Technobility Webinar Series. PMI members can earn 1.0 Category 'A' PDU by viewing this program. View this program now.