> I've personally witnessed a case where a team member went out of his way to propose a rewrite of an important feature and reached out to a couple of senior me

> I've personally witnessed a case where a team member went out of his way to propose a rewrite of an important feature and reached out to a couple of senior members to do a system design review and provide feedback. They initially told him the design was good as is and required no feedback and change, but once the project was about to be deployed they suddenly became very opinionated and critical of each and every tiny detail, including on the need to rewrite the component. I think I've probably been on both sides of this coin. It takes some experience to recognize, and I don't think it's entirely on the individuals. I think it comes about when the people being asked "if it's fine" probably have a completely separate set of day to day concerns than the people doing the asking. They probably have not enough context on why, or the impacts. And they probably don't have the time or support to ask for more time to give a real answer. It's on management for not asking for more analysis or aligning needs or overextending the staff. The term 'ownership' has also done a disservice. 'Stewardship' would be better.