Architecture isn’t just about building new systems; it’s also about living with what came before. Legacy code poses tough questions: Should we refactor it? Replace it? Or simply respect it and build around it? This talk offers a framework for making those decisions with confidence. We’ll explore risk assessment, technical debt prioritization, and the role of business value in shaping technical strategy. Attendees will leave with practical decision-making models for when-and how-to act on legacy code, and how to balance architecture ideals with business realities.