How We Waste Time: II

One reason why we waste as much time as we do is that some time wasting masquerades as real work, or, at least, as prudent risk management. We continue now with our catalog of techniques for wasting time, focusing on these more subtle techniques. See "How We Waste Time: I," Point Lookout for October 5, 2016 for some more blatant examples.

Write-only metrics data

Much of the world is in the midst of a decades-old metrics fad. We gather data, but even when we analyze it, we don't always act on it. When we do act, the value generated can be far less than the cost of data acquisition and analysis. To address this, gather and analyze data about the costs and benefits of gathering and analyzing data. Prepare to be shocked. One shock: why, when we measure the costs and benefits of so many processes, do we so rarely measure the costs and benefits of measuring costs and benefits?

Distrusting experts

Some teams lack expertise, but are nevertheless engaged in difficult work. To manage the risk of error, we review their results in detail. But some teams actually know what they're doing. Their work might also benefit from review, but must we review that work as closely as we review the work of the less-than-expert teams? Can we not reduce review costs without increasing risk?

Training at the wrong time

Sometimes we waste training. For example, learning a technique that we plan to use in the distant future can be futile if that future never arrives. Learning to use software or hardware too soon can also be wasteful if we need the knowledge only after the next release or model becomes available, when that knowledge has been invalidated by the new release.

Pointless debate

Some of us Some of us tend to engage in debates
that seem crucial to the debaters,
but which bystanders easily
recognize as pointlesstend to engage in debates that seem crucial to the debaters, but which bystanders easily recognize as pointless. Often, the debate isn't really about what it appears to be about. Rather, it can be little more than a disguised dominance struggle. Supervisors must recognize these debates for the performance issues that they are, and intervene appropriately.

Technical debt interest payments

Technical debt is the accumulated set of technical artifacts — hardware and software — that ought to be retired, replaced, rewritten, or re-implemented. As long as these artifacts remain in place, they accumulate "interest charges" by adding to the effort required to operate the enterprise or to maintain or enhance its assets. Technical debt remains in place, in part, because most organizations are unaware of its scale. These organizations lack any means of accounting for either technical debt or the interest paid on it. Technical solutions to this problem are available, but in my view, the problem is fundamentally political [Brenner 2016].

Every organization has its own specific sources of wasted time. What can you find in your organizaton? First 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!

Footnotes

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:

Games for Meetings: IV

We spend a lot of time and emotional energy in meetings, much of it engaged in any of dozens of ritualized games. Here's Part IV of a little catalog of some of our favorites, and what we could do about them.

Assumptions and the Johari Window: I

The roots of both creative and destructive conflict can often be traced to differing assumptions of the parties to the conflict. Working out these differences is a lot easier when we know what everyone's assumptions are.

What Makes a Good Question?

In group discussion or group problem solving, many of us focus on being the first one to provide the answer. The right answer can be good; but often, the right question can be better.

Wacky Words of Wisdom: IV

Words of wisdom are pithy sayings that can be valuable so often that we believe them absolutely. Although these sayings are often valuable, they aren't universally valid. Here's Part IV of a growing collection.

How to Get Out of Firefighting Mode: II

We know we're in firefighting mode when a new urgent problem disrupts our work on another urgent problem, and the new problem makes it impossible to use the solution we thought we had for some third problem we were also working on. Here's Part II of a set of suggestions for getting out of firefighting mode.

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

Forthcoming issues of Point Lookout

Coming December 19: Embarrassment, Shame, and Guilt at Work: Creation

Three feelings are often confused with each other: embarrassment, shame, and guilt. To understand how to cope with these feelings, begin by understanding what different kinds of situations we use when we create these feelings. Available here and by RSS on December 19.

And on December 26: Embarrassment, Shame, and Guilt at Work: Coping

Coping effectively with feelings of embarrassment, shame, or guilt is the path to recovering a sense of balance that's the foundation of clear thinking. And thinking clearly at work is important if you want to avoid feeling embarrassment, shame, or guilt. Available here and by RSS on December 26.

Coaching services

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

Public seminars

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 6:00 PM June 29 (Eastern Time), Monthly Webinar, Technobility Webinar Series. You can earn 1.0 Category 'A' PDU by viewing this program. View this program now.