The business executives don't want to avoid change. What they want is that the changes are deployed more successfully. What the business is really asking for, although they may not have the words for it, is a more stable software-release-management process. Change is not the enemy; unstable software releases are.
Think about your smartphone. You get updates every day there; you have become the release manager on your own device. You now update without caring, because you know the changes are small, unlikely to disrupt the functioning of your device and are, in short, safe.
Release managers need to get the business to have that same confidence in their releases. The secret to better software-release-management processes is working on smaller pieces of code.
Small changes are naturally finished more frequently, are easy for the users to absorb, have a smaller impact, require little if any training, are easier to test and generally bring less risk than larger deployments. The business gets to prioritize the changes they want and continuously adjust those priorities almost up to the point where things are put into production.