Many failures occur shortly after something in the environment changes. That change may involve new equipment, firmware, network configuration, construction, electrical work, a vendor update, or a modification to operating procedures.

Maintaining change records gives troubleshooting teams a timeline they can compare with the first appearance of a problem.

Asking "What changed?" is often one of the most useful early questions when previously stable technology suddenly begins behaving differently.