It&#x27;s not a decision which should be made at the level of executives though.<p>Presumably developers are the one&#x27;s estimating how long things take. (If they&#x27;re not, you have even bigger problems and I&#x27;m sorry.) The time to make it safe should automatically be included in those estimates.<p>Moreover, making it safe shouldn&#x27;t be a separate part of the process. It should just be part of how you write software. It&#x27;s either safe or it doesn&#x27;t exist at all. (Compare this to how organizations like Google deal with concurrency: it&#x27;s built in from the start.)<p>A reputable engineer wouldn&#x27;t design and build a bridge which might collapse. A developer shouldn&#x27;t build software which puts lives at risk, regardless of management pressure.<p>If they refuse to relent, there are plenty of jobs where safety isn&#x27;t critical.