1) Build a basic governance framework for reviewing design debt and moving fixes into future sprints.
This governance framework does not need to be complex. In fact, it is preferable that it is not.
Often referred to as the"cost of delay," this means calculating the cost of postponing fixes. The cost can include projected loss in sales and likely customer churn.The log may contain elements such as description of defect, frequency, impact, priority, source, and experience level or conditions necessary for fixing.Realistically assess what can be done holistically to address items in upcoming sprints and which items can be saved for future sprints.
In summary, design debt has the power over time to significantly degrade your user experience. The goal is to face design debt realistically, while still maintaining high productivity of code deployment. Design debt is best framed as an opportunity, a chance to save effort and time and increase customer engagement. As with any new process, revisit the process and make continuous improvements, validating your time and effort in a cohesive product and engaged customers.