As the team gets larger AND/OR the product attains its necessary features, "technical debt" becomes more of a problem. I would love to address it at every stage

As the team gets larger AND/OR the product attains its necessary features, "technical debt" becomes more of a problem. I would love to address it at every stage of a product, but it is simply not possible, many times during early development our team is just figuring things out, seeing what works and what doesn't. If we were to analyze future development for each iteration during this stage, it would be a nightmare. I like to trust in my team that they have a good understanding of best practice and choosing between tough work and future work. When the product "feels" at a good stage, say a few bug fixes after release, we spend much more time refactoring.