Using fake deadlines without driving your engineers crazy

The post argues that deadlines are useful because work expands to fill the time available. In software and communication, a clear due date creates urgency, narrows scope, and helps teams make progress faster.

It also says fake deadlines work best when they are healthy and negotiated. Teams should help define achievable scope, expectations should stay clear, and missing a fake deadline can be better than pushing people into overtime or a toxic pace.

Reading notes

#

• Parkinson’s Law says work expands to fill the time available for completion.
• Without tight time constraints, projects tend to take longer and can suffer from feature creep and scope bloat.
• Challenging deadlines can improve results by forcing trade-offs among scope, resources, and time.
• A deadline can create external accountability and help people make clear decisions about what to include and what to leave out.
• When asking people to do something, it helps to lead with a recommendation of when it should be done by.
• Being explicit about deadlines while staying open to negotiation can improve communication in big organizations.
• A survey with a deadline gets a faster response rate than one that can be filled in whenever.
• Deadlines work best when they are just outside the comfort zone and the team is part of the scope discussion.
• It can be better to miss a fake deadline sometimes than to force extra hours and weekends.
• If external people want to change the deadline or add scope, clear communication helps the team understand the change.