I've noticed a related effect, where every problem discussed in a retro has a "process" solution, because the team's own processes are the only thing the team c

I've noticed a related effect, where every problem discussed in a retro has a "process" solution, because the team's own processes are the only thing the team can fully control. This can lead to both a constant churn in processes and a piling on of additional processes, which bog the team down with an explosion of on-call-like rolls that get rotated through team members.