I own a T-shirt that reads, “The misuse of the word 'literally' makes me figuratively insane." While I understand that words evolve, I am convinced that some words should keep their distinct meanings. Today, it's about 'Target' and 'Deadline'—two words that should not be used interchangeably.

Once the project requirements are clear, estimating the timeline gives you a target date. Initially, confidence in hitting that target might be low due to possible changes or unexpected hiccups. As work progresses, confidence grows, leading to a firm commitment.

When sharing target dates, always clearly state your confidence level. For instance, "Our target is October 31, but we have low confidence until we complete the initial tasks." Targets can also be broader, like Q2 2025 or year-end. Informing stakeholders helps manage expectations if they understand that the dates are estimates and not firm commitments.

A deadline is the date by which a project must be completed, often due to external factors like regulations or important events. I recall a project where the chairman needed to announce a new service at a major event, setting an unmissable deadline.

Missing a target isn't great; missing a deadline is a disaster. Project managers must clearly communicate whether they're discussing targets or deadlines.

Every ongoing or planned project should have a target date, but not all have deadlines. If your target date is close to or beyond the deadline, you have a problem. Targets can slip due to requirement changes, team availability, or estimation errors (read more about this in David's article: "3 Causes of Software Project Delays").

To address this, you can: 1. Delegate some features to another team. 2. Identify features to deliver post-launch.

These strategies can create a buffer between your target date and deadline, improving your chances of success.

In my earlier example, the target was too close to the deadline. The business model allowed us to launch without invoicing immediately and complete that process a month later. This workaround met the deadline.

Sometimes targets turn into deadlines out of necessity. This should be a deliberate choice, communicated to all stakeholders.

For instance, if other teams need to plan around project completion, such as internal training or marketing campaigns, the project manager should avoid this unless highly confident in the target date. If confidence is low, consider deploying the project in an off-state, ready to switch on when needed.

It is crucial for project managers and owners to clearly communicate whether they are discussing a target date or a deadline. Clear communication ensures everyone is on the same page and projects stay on track.

When communicating target dates, remember to include the level of confidence in that date. Communicate when events occur that may change the target date or alter the level of confidence in that date.