Well said. Nobody is willing to take risks and change things up when things are going well.
I've found myself warning the people I work with that we need to do things to stabilize the core of our software and infrastructure.
When things are going well it's hard to get buy-in and the time to do any necessary, and sometimes radical changes.
And you probably may say at this point: "well if things are going well why would you do anything radical?" but I generally mean well as in not falling apart, but not ideal, as in every week we keep seeing the same issues reported in our day-to-day. Cause eventually, it only takes something else to go wrong to expose major issues and vulnerabilities with the operation.
Nevertheless, when shit goes sideways, as it usually tends to happen especially when you don't slow down and maintain enough, people then just want you to fix the problem, and do whatever it takes, including those aforementioned risky things you were proposing to avoid the shitty times to begin with.