• New requirements are often solved via custom code even though configuration would suffice
• Without shared standards, inconsistencies arise – and technical debt builds up again
• Decisions on customisations are not consistently assessed (risk, upgrade relevance, operational consequences)
• Training on configuration options
• Risk assessment for customisations & governance processes
• Creation of individual configuration guidelines
• Compact „Decision Guide“ for customisations (when to configure, when to extend, when to avoid) as a shared reference
• Role and process setup for sustainable platform governance (e.g. review, approvals, documentation standard)
