Configuration, not code
A change to how a system behaves shouldn't need a developer, a release and a weekend.
The problem
On our sports club platform, commission rates, payment limits and which features each club uses all change often, and often urgently. If any of them needs a release, the platform owner becomes a bottleneck.
What we did
All of these are settings, held in one place and checked when they're used. Commission falls back from the club's rate to its plan's rate to a default. Every feature can be switched off for one club, and payments have an emergency off switch. Clubs choose their own features on a settings screen, and nothing is deleted when they switch one off.
In an enterprise
We use the same idea in data platforms: pipelines driven by configuration, so a new feed is a few lines of settings rather than new code. Reference data that business teams own goes one step further. They change it through a reviewed change, deployed with the code, so it never drifts between environments.
What we'd do differently
Decide early which settings need an audit trail, and record who changed what from the first day.