What is the best way to manage technical debt in a growing product team?

First, make technical debt visible. Keep a simple list of painful areas that slow the team down and ask developers to add items as they encounter them. Then, prioritise these items based on impact on delivery and risk, not just annoyance. Allocate a predictable slice of capacity each sprint or month to paying down high value debt, rather than relying on occasional clean up weeks. When you introduce a shortcut, capture why it was chosen and under what conditions it should be revisited. This approach keeps debt under control and avoids the all or nothing cycles of neglect and massive rewrites.