3,000 m
The architecture
Shared metadata needs a shared cadence
When one Salesforce org hosts a dozen teams, independent releases stop being independent. Two teams change the same page layout, a third deploys a permission set that overwrites both, and the retro concludes that communication could be better. The underlying problem is simpler. Shared metadata needs a shared cadence, whether or not anyone likes the word train.
Keep the cadence fixed and the scope flexible: a fortnightly release window, one integration sandbox everyone merges into early, and a clear cut-off for what makes the train. Work that misses it catches the next one. Unpackaged metadata causes most collisions, so moving teams towards unlocked packages with clear ownership shrinks what the train has to carry.
300 m
The delivery team
Keep the cadence, drop the ceremony
The ceremony is what teams actually hate. Drop the two-hour release planning meeting and replace it with a merge deadline, an automated deployment to the integration sandbox and a short go or no-go check in the release channel. If the pipeline is green and the smoke tests pass, it ships. If not, the owning team fixes it or pulls it.
A train that leaves on time is a train people stop arguing about.
Hotfixes still exist, but they are rare and visible. Anything outside the window needs a named approver and a short note explaining why it could not wait for the next train. Publish the list every quarter. It turns out most things can wait a fortnight, and the few that cannot are worth a proper conversation.
