Always negotiate your deadlines! (How to gain trust and prevent working overtime)

The post says that when a feature must ship in a fixed timeframe and the team cannot add capacity, the practical move is to negotiate scope. It presents this as a better response than quietly overworking or insisting the plan is doomed.

Reading notes

#

• The author describes a feature with a PRD ready and a three-week release deadline, while the work they had identified would require four people.
• The manager asked for the feature to be implemented by one person, with only limited senior engineer support because of other responsibilities.
• The post contrasts three reactions: trying to do as much as possible alone and missing the deadline, saying the project is impossible, or negotiating.
• It argues that business deals are rarely closed on the first offer, so there is room to work toward a solution both sides accept.
• The value of an engineer is presented as extending beyond code, including interaction with management and product.
• The post names the project management triangle as scope, deadline, and cost.
• Scope is described as the PM’s territory, deadline as something set by leadership or communicated by the SDM, and cost as the number of engineers assigned, also under SDM responsibility.
• In the example, the deadline was fixed by leadership and the cost could not change because the team had other priorities, so the scope was negotiated.