This happens a lot in companies where the CEO drives product decisions. There&#x27;s nobody to push back on ideas, so you end up with developers implementing every half-baked idea that comes out of one person&#x27;s mouth.<p>In grownup companies, where you have a product manager and that person has a boss and that person has a boss, the product manager has to justify his decisions to people and has to get feedback, and perhaps has to convince people before he&#x2F;she&#x27;s let loose on the engineers, so you get a lot less time wastage on people&#x27;s whims.<p>In really big-boy companies, engineering and QA has a stake and can push back on harebrained ideas too! The best places have it where there&#x27;s a product manager, a project manager, an engineering lead, and a QA lead, and they all are empowered to get into a room and have to agree on whether what we&#x27;re doing provides business value, whether it&#x27;s feasible, and if can be done by the deadline.<p>Of course, in any case if you&#x27;ve got senior leadership who engage in seagull management, all bets are off.