Engineering roadmaps usually list features and hide the work that keeps the product running. This deck makes the trade-off visible. It starts with who the engineers are and how capacity is split between features, reliability and debt, then shows the now, next and later view, the platform migration, the debt trend, a reliability scorecard and the risks.

The sample follows Dunlinn Cloud, with 42 engineers and a 60 / 20 / 20 split of 1,680 engineer-days a quarter. It shows four initiatives with a target metric each, a platform migration in four steps, debt falling from 62 to 38 items and an honest amber and red scorecard. Replace the split, initiatives, metrics and risks with your own, and defend the split with last quarter's actuals.