The release-cadence check at the end is useful. It makes the choice about how the team ships, rather than which branching diagram looks most organized.
Exactly! The release cadence should drive the branching strategy, not the visual appeal of the workflow. GitFlow adds useful structure when releases need stabilization and coordination, but it becomes unnecessary overhead for teams that can safely deploy small changes continuously. Thanks for highlighting that point.
In your experience, what is usually the clearest signal that a team has outgrown GitFlow?