Tech debt is not inherently bad. Like financial debt, it is a tool: useful when taken deliberately, dangerous when it accumulates in the dark.
Take debt on purpose
Skipping a feature is fine. Skipping tests on your billing code is not. Be deliberate about where you cut corners and write down what you owe.
Pay it down in small change
- Refactor the code you are already touching.
- Keep a visible list of known shortcuts.
- Fix the debt that slows you down today, not hypothetical debt.
An MVP is supposed to be minimal. The skill is being messy in the places that do not matter and disciplined in the few that do.