Ask a team how often they deploy and you learn almost everything about how they work. Weekly deploys mean batching. Batching means merge conflicts, long-lived branches, and releases that need a manager.
Daily deploys invert all of it. Changes get small. Reviews get fast. Rollbacks become boring instead of terrifying.
It's a tooling problem before it's a culture problem
Most teams don't batch because they love risk — they batch because their pipeline makes shipping expensive. Twenty-minute builds and manual QA gates make daily deploys irrational.
Fix the pipeline first. When a deploy takes ten seconds and a rollback takes one click, the culture follows without a single all-hands about 'velocity'.