A good code review to change software systems

  1. Acknowledge however long a process has worked for and how much business value it has gained.
  2. Present the changes and growth occurring, and the challenges that are becoming apparent or the needs that are blocked.
  3. Outline what needs to change to support this growth or needs.

Burning down the past in a structured attack is a path of last resort if indeed of any resort.

A good code review, a business process review, and any proposed changes should be viewed from the perspective of making the company better.