"Endless refactoring and tech debt cycles are the failure mode of mature eng orgs — someone has to cut through and demand product value again"
Evidence from the Archive
Basecamp / Shape Up
Ryan Singer sees mature engineering orgs trapped in 'all refactoring all day' — a sign that product and engineering have lost the conversation about what to build
His diagnosis: refactoring becomes the default work when there's no cross-functional agreement, because engineers can unilaterally decide the system needs cleaning
Singer's pushback isn't against debt per se but against the endemic middle-age failure mode in engineering organizations that started well and got stuck. A company has been running scrum for years, revenue is coming in, but 'nothing is getting out the door.' There's an entrenched engineering team separated by a wall from an entrenched product team.
In that environment, tech debt and refactoring become the default work because they require no cross-functional agreement — engineers can unilaterally decide the system needs cleaning, and product can't credibly push back because they don't understand the code. The contrast with Basecamp's six-week cycles is the tell: there, engineering capacity was predictably blank and could be spent on whatever the team agreed was most important. Endless paydown is a disguised form of stagnation.
In Ryan's own words: "There are a lot of engineering orgs that have been standing around for a while and it's all refactoring all day and tech debt and stuff like that. And there's reasons why all those things got there, but there comes a point where we have to figure out how to cut through it and make some hard choices so that we can carve out time to build the stuff that's actually going to be needle moving again and not just sustaining us where we are to run in place." (The core critique — refactoring cycles as the failure mode of mature eng orgs.)