Really good articulation of the behavioral shift. The batch size point is the one teams underestimate most. I've seen orgs try trunk-based with massive PRs that sit for days and they wonder why it doesnt work. The non-blocking review problem you highlighted is real, when reviews become non-urgent they lose their signal value entirely and just become compliance theater. What helped us was making review latency a tracked metric alongside deploy frequency, once people saw that stale reviews correlated with longer cycle times the priority shifted naturaly. The mindset change is definitly harder than the Git config.
Really good articulation of the behavioral shift. The batch size point is the one teams underestimate most. I've seen orgs try trunk-based with massive PRs that sit for days and they wonder why it doesnt work. The non-blocking review problem you highlighted is real, when reviews become non-urgent they lose their signal value entirely and just become compliance theater. What helped us was making review latency a tracked metric alongside deploy frequency, once people saw that stale reviews correlated with longer cycle times the priority shifted naturaly. The mindset change is definitly harder than the Git config.