Great question! Team retrospectives are one way to identify if there is a balance or not. The team can give ideas with owners to track how they prefer to work. Another way is to keep the heavy lifting on the Scrum Master temporarily and slowly introduce the changes/processes/standards into the team like a funnel. I am curious to hear other feedback on this topic! Saving Changes...
Self-organization and team autonomy needs to be within the guardrails of organization standards and policies, though not necessarily processes as those should be "fit for purpose".
By engaging enterprise control partners early in the life of a project, the team can ensure they are aware of the rules which can be bent and which need to be adhered to.
This is one of the reasons that Disciplined Agile has Enterprise Awareness as one of its principles.