How do I convince my team to fix tech debt?
You can spot the debt. The wall you hit is convincing others to fix it while everyone is pushing for the next feature. That is not a technical problem anymore. It is a persuasion problem, and it is one of the hardest because you are asking people to spend now to avoid a pain they cannot yet feel. The mistake is arguing in engineering terms. Clean code, right structure, proper design. Those words do not move the people who control the schedule, because they are not measured on them. What moves them is risk and cost in their language. This debt will slow every future feature by this much, or it will break at the worst time and cost us that. Before your next attempt, translate the debt into their stakes. Tie it to a deadline they care about, a customer risk, a cost they will feel. Pick the one piece of debt that is genuinely most dangerous and make that case, not a general plea to clean things up. You will not win them all. You win the important ones by speaking about the future in terms the decision makers already care about.