You're leading an engineering initiative where the business wants visible progress quickly, but the underlying system has enough technical debt that rushing delivery could create long-term cost and instability. You need to show near-term results without locking the team into brittle architecture, recurring rework, or a growing maintenance burden.
How do you balance short-term delivery with long-term maintainability?