Every Change Needs an Undo

When we started editing a client's website content through its content management system, we discovered it kept no history. A saved change simply replaced what was there. There was no version to go back to, and no record of who had changed what.

That is common, and it makes every edit riskier than it needs to be. A mistyped headline, an overwritten paragraph, a wrong image, all of them permanent unless someone happens to remember the previous version.

Snapshot before every write

Until proper history was in place, we adopted a simple rule: before changing anything, save a copy of exactly what is there. Every edit was preceded by a snapshot and followed by a line in a change log noting what changed and where the copy lives. Reverting anything became a single step, not an act of reconstruction.

We also took a full restore point of the entire site's content, so there is one known-good state to return to whatever happens next.

Then build history into the system

Snapshots are a workaround. The lasting fix is a system that records history itself. The site now keeps a log of every save, who made it and what each field changed from and to. Version history turns 'we changed something and broke it' from an afternoon of detective work into a click.

Reversibility makes teams faster

It sounds like caution, but the effect is the opposite. When every change is easy to undo, people make changes with confidence instead of hesitation. Approvals move faster because the cost of being wrong is small. The teams that move quickest are rarely the ones taking the biggest risks. They are the ones who made risk cheap.