Technical Debt
The implied cost of additional rewrite caused by choosing an easy (limited) solution now instead of using a better approach that would take longer.
Impact
Unmanaged technical debt kills velocity. Eventually, the team spends 100% of their time servicing the debt (fixing bugs) and 0% building new features.
Weinto take
We distinguish between "Prudent" and "Reckless" Debt. Taking on debt to meet a market window is smart (Prudent). Writing bad code because you don't know better is negligent (Reckless). We pay down debt every sprint to keep the interest payments manageable.