Technical debt
Technical debt is the deferred cost of design or implementation shortcuts that slow future change or raise risk.
How it works
Name the debt, the interest (slowdowns, incidents) and the paydown plan. Not all debt is bad; unpaid invisible debt is. Product engineering makes debt visible in roadmaps.
Example
A dual-write period during a datastore migration is deliberate debt with an end date - unlike an undocumented shared database.