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.

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:

Seeing Through the Fog

When projects founder, we're often shocked — we thought everything was moving along smoothly. Sometimes, with the benefit of hindsight, we can see that we had — or could have had — enough information to determine that trouble was ahead. Somehow it was obscured by fog. How can we get better at seeing through the fog?

Nine Positive Indicators of Negative Progress

Project status reports rarely acknowledge negative progress until after it becomes undeniable. But projects do sometimes move backwards, outside of our awareness. What are the warning signs that negative progress might be underway?

TINOs: Teams in Name Only

Perhaps the most significant difference between face-to-face teams and virtual or distributed teams is their potential to develop from workgroups into true teams — an area in which virtual or distributed teams are at a decided disadvantage. Often, virtual and distributed teams are teams in name only.

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?

Risk Creep: II

When risk events occur, and they're of a kind we never considered before, it's possible that we've somehow invited those risks without realizing we have. This is one way for risk to creep into our efforts. Here's Part II of an exploration of risk creep.

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

Forthcoming issues of Point Lookout

Coming July 24: The Stupidity Attribution Error

In workplace debates, we sometimes conclude erroneously that only stupidity can explain why our debate partners fail to grasp the elegance or importance of our arguments. There are many other possibilities. Available here and by RSS on July 24.

And on July 31: More Things I've Learned Along the Way: IV

When I have an important insight, or when I'm taught a lesson, I write it down. Here's Part IV from my personal collection. Available here and by RSS on July 31.

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