Expose Tech Debt and UX Debt in DevOps stage and group dashboards
We have been getting repeat user feedback via various channels such as SUS and PNPS surveys that UX and tech debt related areas of our product, such as site performance, need improvement.
We currently have labels in use for feature maintenance
(technical debt) and UX debt
. We should surface these metrics for issues and MRs, and begin tracking in group dashboards to help determine if the level of work being done in these areas by teams vs the health of their product in these areas is well-balanced toward making progress.
Surfacing these metrics is the first step to being able to better understand and prioritize UX and tech debt work as needed across teams, with the right balance against new feature development.
Reference links:
https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#technical-and-ux-debt https://about.gitlab.com/handbook/engineering/management/throughput/#implementation