Push back and delay can both describe a date moving later, but they carry different assumptions about intent. Delay may be unplanned or caused by external factors. Push back usually implies an intentional scheduling decision someone made.
The test: intentional choice, or something that happened?
The question is whether the date was intentionally moved, or whether something caused a delay. Getting this wrong misattributes responsibility for the schedule change, which matters for accountability in a post-mortem or stakeholder update.
"A vendor outage makes the launch slip by two weeks, with nobody intentionally moving the date: 'The vendor outage delayed the launch by two weeks' is correct."
Nobody chose this. Something outside the team's control caused the slip, and "delay" reports that accurately.
"'The team pushed the launch back by two weeks' wrongly implies the team chose to move it."
Using "pushed back" here assigns a decision to the team that it never actually made -- it makes an outage look like a choice.
If the team had instead decided to add two more weeks of testing on purpose, "the team pushed the launch back by two weeks" would become the accurate wording -- the same words, correct only when the team actually made the call.
The common mistake: misattributing agency
The mistake is misattributing agency -- saying a team "pushed" something back when an external cause actually delayed it misattributes responsibility for the schedule change. In a post-mortem, this distinction is not cosmetic: it decides whether the team's decision-making gets scrutinized or whether the review turns to the vendor relationship instead.
Want to learn "Push Back" in depth?
Lyra Practice teaches advanced non-native professionals the nuance of high-value expressions like this one, then has you practice using them in realistic work scenarios.
Start learning for free →A quick test before choosing the word: did a person or team make a deliberate call to move the date? If yes, "pushed back" is accurate. If the date moved because of something that happened to the team, "delayed" is the honest word.
Agency changes what a reader does next
The reason this distinction earns its own accountability discussion is that a reader acts differently depending on which word they see. "Delayed" prompts a reader to ask what went wrong externally -- a vendor, a dependency, an unexpected event -- and to look for ways to prevent that specific cause next time. "Pushed back" prompts a reader to ask why the team decided the extra time was worth it, and to evaluate that decision on its merits.
Mixing the two up doesn't just misdescribe the past -- it can misdirect the fix. A launch that was genuinely delayed by a vendor outage doesn't need the team's decision-making reviewed; it needs the vendor relationship reviewed. Calling it "pushed back" by the team sends the post-mortem down the wrong path entirely, looking for a decision that was never actually made.
There's a middle case worth naming too: sometimes an external event forces a team to make a deliberate choice about how to respond, and both words apply to different parts of the same story. "The vendor outage delayed the initial rollout, and the team then pushed the full launch back by an additional week to rebuild confidence in the data" separates the involuntary cause from the voluntary decision that followed it -- which is usually the most accurate way to tell that kind of story.
Practice scenarios
Practice using push back in situations like:
- writing a post-mortem that correctly attributes a schedule slip to an external cause
- reporting an intentional decision to add more time, distinct from an unplanned delay
- catching wording that accidentally assigns blame to a team for something outside its control
Useful practice phrases:
- "[External cause] delayed [the launch] by..."
- "[The team] pushed [the launch] back by... to..."
- "That wasn't a delay -- the team deliberately pushed it back to..."