I've quit before because of this very reason. You're allowed to disagree with me obviously, but I don't want to work with you if you honestly believe this is a good policy.
I've quit before because of this very reason. You're allowed to disagree with me obviously, but I don't want to work with you if you honestly believe this is a good policy.
In my experience, engineer B usually gets to take charge of the project, and inevitably takes 3-4 years before the project ends, having failed to deliver anything that works.
Bonus points if the project is then declared a success by the pointy haired boss that bet on engineer B.
If you hand out ownership/status/power/money based on unsubstantiated project estimates, I’m not sure you can ever expect very good or happy results.
It’d be much better if all of the characters in that example sat down and decided what the most realistic best case with a solid plan looks like, and took responsibility for communicating it together, and you find a different way to decide who gets to own it.
It is essential to create teams that are aware of and talk about the most optimistic timelines, but where everyone knows the people on the front lines doing the work are in control and set the pace.
This is very achievable if the starting point is empowering people, removing roadblocks, and increasing the team’s capabilities and leverage, rather than trying to impose timelines.