No amount of velocity measurement will either. My observation has been time estimation is often precise and people confuse precision for accuracy. If dates are being missed I evaluate carefully the decisions made given the information at the time and understand that as long as decisions are being made well stuff doesn’t always move at the pace we expected or desire. I don’t need fake velocity data to argue for time, people, or prioritization with management because I can actually explain what’s going on in my organization. Btw - I’ve been in FAANG as well as other large software development orgs with 60k+ developers for my entire career. Nothing beats steady and rapid delivery, but I occasionally do have to move teams to avoid micromanaging scrum waterfall agile folks.

Martin Fowler, who I had the pleasure to know back in the XP days, says:

“Agile Development is adaptive rather than predictive is people-oriented rather than process-oriented”

Reconcile that with agile as you understand and practice it - the entire point of measuring velocity is to be predictive. How on earth is that agile? How many process and planning oriented ceremonies do you go to? Does my empathetic listening approach sound more people oriented or OP’s “I’ll fire you if you aren’t burning down points” approach?