I would guess that, like technical debt, churn is something you can have both too much and too little of. Stagnation also has a cost. When I work with teams tha

I would guess that, like technical debt, churn is something you can have both too much and too little of. Stagnation also has a cost. When I work with teams that have had the same members for a long time, it seems that they've always lost their edge. They get attached to their existing code, and resistant to making changes that might require major alterations to it. To the point of pushing back hard against new business goals. I think that from the business folks' perspective, you might say they're no longer playing to win, they're just playing to not lose. Which, in many portions of the tech space, is a recipe for inexorable decline.