Irrational Deadlines

The term deadline dates to the 1840s, according to the Google Books Ngram Viewer. A hundred years later, two new phrases appear: hard deadline and soft deadline. They refer to deadlines that are, respectively, inflexible and flexible, a curious distinction, considering that the original connotation of deadline was inflexibility.

In project management, the need to distinguish deadlines by their flexibility arises, in part, from the hope that we can schedule projects as precisely as, say, showings in movie theaters. Scheduling projects is tricky at best, because uncertainties inherent in the work always intrude. We're almost always late, and at times really, really late. Sometimes, we don't finish at all.

Even when late, we maintain our schedule illusions. We actually have a word for adjusting schedules — slip — that makes re-scheduling seem like a minor, unavoidable mishap. And every time we slip, deadline loses more of its connotation of inflexibility. By now, its connotation of inflexibility is so eroded that we need a way to restore it. The phrase hard deadline meets that need. And if we have hard deadlines, we must have soft deadlines. It's only fair.

What we really need are rational deadlines.

Rational deadlines are set according to the estimated duration of the work — no other factors enter. When we set deadlines to meet other needs, we risk departing from reality. Here are some of the needs that lead to setting irrational deadlines.

Managing the budget

Some managers use deadlines as budget control tools. They believe that tight deadlines limit spending by simply terminating budget authority. But when the deadline nears and the work is incomplete, we extend both schedule and budget, sometimes repeatedly. Oh well.

Motivating people

When leadership skills and compensation-based incentives don't motivate people to work soul-killing hours, some managers hope that tight deadlines can help close the gap. Burnout is a common result.

Compensating for late starts

Decision makers sometimes make decisions with considerably less urgency than they impose on project teams, hoping that tight deadlines for project execution can compensate for lengthy pre-execution decision cycles. To some extent, they do compensate, but the price is lower quality and higher turnover.

Keeping secret schedule reserves

Some believe Rational deadlines are set
according to the estimated
duration of the work —
no other factors enterthat because projects are always late, telling teams the actual need-by dates is foolish. Instead, they tell teams some earlier date, to impose enough pressure to get the job done on time. Unfortunately this practice deepens the distrust between managers and the managed.

Compensating for revenue shortfalls

When in financial distress, some organizations seek revenue from new offerings. The pressure to produce these products and services can be intense, often appearing as irrational deadlines. But financial salvation remains elusive, if the root causes of the financial distress include anything other than gaps in the company's product lineup.

Setting objectives that address real organizational needs is sensible. Setting irrational deadlines for projects isn't sensible — it merely intensifies those real organizational needs. Setting irrational deadlines is management malpractice.  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 Project Management:

Films Not About Project Teams: II

Here's Part II of a list of films and videos about project teams that weren't necessarily meant to be about project teams. Most are available to borrow from the public library, and all are great fun.

Nine Project Management Fallacies: IV

Some of what we "know" about managing projects just isn't so. Understanding these last three of the nine fallacies of project management helps reduce risk and enhances your ability to complete projects successfully.

On the Risk of Undetected Issues: I

In complex projects, things might have gone wrong long before we notice them. Noticing them as early as possible — and addressing them — is almost always advantageous. How can we reduce the incidence of undetected issues?

Unresponsive Suppliers: II

When a project depends on external suppliers for some tasks and materials, supplier performance can affect our ability to meet deadlines. How can communication help us get what we need from unresponsive suppliers?

Premortems

Premortems are simulated retrospective examinations of future events, conducted as if those future events had already occurred. By combining the benefits of psychological safety with a shift in temporal perspective, they offer advantages for planners.

See also Project Management and Project Management 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