A lot of interesting opinions here - I thought this the no hard set “Engineering Time” was interesting, especially given some of the challenges around quantifying some of this work and the impact.<p>"Too often, tech leaders wield the “tech debt” card to justify unstructured engineering time. While the intention is noble, the execution is usually flawed. Most of the things we treat as “tech debt” aren’t.<p>Instead, whatever you have on your backlog should be treated like any other task: Make it visible, quantify its impact, and collaborate with Product to weigh its ROI against new features. When tech debt is treated as part of the roadmap, it forces discipline and ensures alignment on what truly matters."