I'm not sure how many execs would be totally chill with not being first to market if they could have been, but I have seen "Oh, that's actually okay, we been saying March knowing it'd really be September. So you have more time, but it really has to be September"
And then the exec pats themselves on the back for their smart planning, while the engineers regret all the corners that they wouldn't have cut if they'd known they had more time.
... most people aren't arbitrary, they have different experiences or perspectives which leads them to 'rational' decisions.
I'm struggling to see what's supposed to be wrong with this.
so that's the problem... what the solution is and if it has anything to do with due dates, I don't know!
But that wasn't known. They expected to need it, and when circumstances changed, they canceled the project. It seems to have been a huge project; "don't start work on the project until you need it to be finished" was never going to work.
You can't judge people by what they should have done if they'd had perfect knowledge of the future. If anyone involved had had perfect knowledge of the future, they wouldn't have been working for the company anyway.
I did, before you, when I did the same thing, but it's not like you disagreed with the premise.
Supposedly there's a thing called "first-mover advantage". Making the deadline would get them $XXX, and missing it only gets $XX but is still worth doing.
There's a way to map an additional X% chance of making the deadline to being worth some dollar amount of extra effort. Ideally done with full knowledge that it is somewhat of a gamble, and that the dev team don't need to catch any frustration if it doesn't work out.
> "Looks like we won't be using that system anymore, so we can sunset the replacement."
Makes sense to be. Replacing the system would have benefits worth an estimated $X/year, but it takes long enough that the world changed under you and it no longer matters.
A year later, a different team is tasked with replacing a legacy system with a new one. The team asks the Executive when the legacy system needs to be replaced. "Oh, well the legacy system still works, so we don't have a hard date. But it should be soon." Four years later, the team is still working on replacing the legacy system. The Executive comes to them and says, "Looks like we won't be using that system anymore, so we can sunset the replacement."