The AI Reckoning / Chapter 14

Rewrite or Modernize Decision Tree

Choose a change strategy after understanding the system and its dependencies.

Download printable PDFOne page · Updated October 20, 2026

Work through these options

Retire: no required user, integration, record-retention obligation, or business process still depends on it. Plan data disposition and a safe shutdown.
Wrap: the core behavior remains useful, but integration is the obstacle. Add an interface with access controls, validation, monitoring, and ownership.
Refactor: the desired changes are bounded and the team understands the behavior. Change small pieces behind characterization tests.
Replace gradually: route one workflow at a time to a new implementation. Plan data synchronization, reconciliation, rollback, and the eventual shutdown.
Rewrite: assess this when required behavior cannot be achieved through bounded changes, or the platform cannot be operated acceptably. Record alternatives, migration costs, business rules, and transition risks.

Map dependencies with users and operators. Capture important current behavior in tests, including exceptions.
Use sanitized test data. Check outputs against business requirements; preserving an existing bug is not the goal.
Choose an accountable owner, a reversible first step, success measures, and stop conditions. No option is automatically safe.

Chosen approach and evidence: …. Next reversible step and owner: ….

Use the printable worksheet to keep your notes and evidence with your team.