I experienced a layoff as a result of this once - essentially the product development cycle at this company did not properly account for implemenation, much les

I experienced a layoff as a result of this once - essentially the product development cycle at this company did not properly account for implemenation, much less scaling for clients' use cases. QA was flawed as a result, and products shipped buggy. Deploys were based on releasing new features or for bug fixes for bugs that important people within clients noticed. The process ended up with me accidentally releasing a broken Android apk to production, and I ended up falling on the sword with no one else taking responsibility for the resulting quality. Needless to say, that company bled a lot of high quality developers as a result, somehow turning a likely success to likely failure. Startups should beware of such behavior - it is a great way to cause the company to self-destruct when you are not giving all stakeholders adequate say on deliverables.