Project Manager’s Dilemma: Soft Deadlines v Hard Deadlines?

deadlines

In the fairy tale, The Boy who cried Wolf, the villagers stopped believing the child.

There was no wolf, they thought which was true until one day…

The same thing occurs when you – or someone above you – creates an artificial deadline.

I’m looking at a report that says we have a hard deadline on May 31st.

Why hard? Why not just deadline?

I suspect it to do with our fondness for military terminology.

  • Deadlines
  • Targets
  • Conquer

We’re fond of military (and sports) terminology in business. Maybe it sounds macho.

Project Plan Template

Gantt Chart in the Project Plan template pack

Soft Deadlines v Hard Deadlines

Ordinary tasks (another military term?) feel more important. But sometimes a deadline is simply a deadline.

Why dress it up?

It can work but it has drawbacks too. For example, it:

  • Creates a false sense of urgency. This has a negative cascade effect on the team. Suddenly everyone stops what they’re doing to meet this new artificial deadline.
  • Distracts us from our current work, which was almost finished. It’ll lose momentum and we’ll have to kick start it again.
  • Postpones more pressing issues to a later date, which we will also have to start again, losing more time.
  • Relegates important tasks to the back burner.

‘What happens if we miss this deadline?’ is a valid question.

‘Do we ignore the previous hard deadline?’

Clichéd writing and clichéd thinking are everywhere.

Fake hard deadlines are a common example of this.

See it for what it is.

Sometimes it’s ok to miss a deadline. Trust me, the world keeps spinning.

Thousands of templates to jump start your project

Acceptance Test Plan

Contingency Plan

Software Development Templates

Acquisition Plan

Conversion Plan

Software Requirements Specification

Action Plan

Cost Benefit Analysis

Software Testing

API Documentation

Database Design

Standard Operating Procedures (SOP)

Audience Analysis

Datasheet

Statement of Work

Availability Plan

Deployment Plan

System Administration Guide

Bill of Materials

Design Document

System Boundary

Business Case

Disaster Recovery Plan

System Design Document

Business Continuity

Disposition Plan

System Specifications

Business Plan

Documentation Plan

Technical Writing Templates

Business Process

Employee Handbook

Test Plan

Business Requirements

Error Message Guide

Training Plan

Business Rules

Expression of Interest

Transition Plan

Capacity Plan

Fact Sheet

Troubleshooting Guide

Case Study

Feasibility Study

Use Case

Change Management Plan

Functional Requirements

User Guide

Communication Plan

Grant Proposal

Verification and Validation Plan

Concept of Operations

Implementation Plan

White Papers

Concept Proposal

Installation Plan

Work Instructions

Configuration Management Plan

Interface Control Document

Software Development Templates

Acceptance Test Plan

Maintenance Plan

Software Requirements Specification

Acquisition Plan

Market Research

Software Testing

Action Plan

Marketing Plan

Standard Operating Procedures (SOP)

API Documentation

Needs Statement

Statement of Work

Audience Analysis

Operations Guide

System Administration Guide

Availability Plan

Policy Manual

System Boundary

Bill of Materials

Project Plan

System Design Document

Business Case

Proposal Manager Templates

System Specifications

Business Continuity

Proposal Template

Technical Writing Templates

Business Plan

Quality Assurance Plan

Test Plan

Business Process

Release Notes

Training Plan

Business Requirements

Request for Proposal

Transition Plan

Business Rules

Risk Management Plan

Troubleshooting Guide

Capacity Plan

Scope of Work

Use Case

Case Study

Security Plan

User Guide

Change Management Plan

Service Level Agreement (SLA)

Verification and Validation Plan

Communication Plan

Setup Guide

White Papers

Concept of Operations

Social Media Policy

Work Instructions

Concept Proposal

Contingency Plan

 

Configuration Management Plan

Conversion Plan