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.
- 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 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.
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 welcomeWould you like to see your comments posted here? rbrenIyYrkaKMUbUPgdIcner@ChacdBWgshNrkboUTETSoCanyon.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.
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:
- Pygmalion Side Effects: Bowling a Strike
- Elise slowly walked back to her office, beaten. Her supervisor, Alton, had just given Elise her performance
review — her third consecutive "meets expectations." No point now to her strategy of
giving 120% to turn it all around. She is living a part of the Pygmalion Effect, and she's about to
experience the Pygmalion Side Effects.
- The Good, the Bad, and the Complicated
- In fiction and movies, the world is often simple. There's a protagonist, a goal, and a series of obstacles.
The protagonists and goals are good, and the obstacles are bad. Real life is more complicated.
- Teamwork Myths: Formation
- Much of the conventional wisdom about teams is in the form of over-generalized rules of thumb, or myths.
In this first part of our survey of teamwork myths, we examine two myths about forming teams.
- Office Automation
- Desktop computers, laptop computers, and tablets have automation capabilities that can transform our
lives, but few of us use them. Why not? What can we do about that?
- 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
Forthcoming issues of Point Lookout
- Coming August 23: Look Where You Aren't Looking
- Being blindsided by an adverse event could indicate the event's sudden, unexpected development. It can also indicate a failure to anticipate what could have been reasonably anticipated. How can we improve our ability to prepare for adverse events? Available here and by RSS on August 23.
- And on August 30: They Just Don't Understand
- When we cannot resolve an issue in open debate, we sometimes try to explain the obstinacy of others. The explanations we favor can tell us more about ourselves than they do about others. Available here and by RSS on August 30.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenVVdrvOdWruhUkiXYner@ChacbWwVajsVlUJaWRUhoCanyon.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:
- Get 2001-2 in Geese Don't Land on Twigs (PDF, USD 11.95)
- Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
- Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
- Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)
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
- The Race to the South Pole: Ten Lessons for Project Managers
- 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. Lessons abound. Read
more about this program. Here are some dates for this program:
- The Westin Virginia Beach Town Center, 4535 Commerce Street,
Virginia Beach, VA 23462: September 13,
Monthly Meeting, Hampton Roads Chapter of the Project Management Institute. Register now.
- CTCPA, 716 Brook Street,
Rocky Hill, CT 06067: September 20,
Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.
- The Westin Virginia Beach Town Center, 4535 Commerce Street, Virginia Beach, VA 23462: September 13, Monthly Meeting, Hampton Roads Chapter of the Project Management Institute. Register now.
- Creating High Performance Virtual Teams
- Many people experience virtual teams as awkward, slow, and sometimes
frustrating. Even when most team members hail from the same nation or culture, and even when they all
speak the same language, geographic dispersion or the presence of employees from multiple enterprises
is often enough to exclude all possibility of high performance. The problem is that we lead, manage,
and support virtual teams in ways that are too much like the way we lead, manage, and support co-located
teams. In this program, Rick Brenner shows you how to change your approach to leading, managing, and
supporting virtual teams to achieve high performance using Simons' Four Spans model of high performance.
Read more about this program. Here's a date for this
- Baci Grill, 134 Berlin
Road, Berlin, CT 06416: September 19,
Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- Baci Grill, 134 Berlin Road, Berlin, CT 06416: September 19, Monthly Meeting, Southern New England 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.