Skip to content

2. Change Management

Change management is the discipline of making changes to a working system carefully, instead of just diving in — because "it worked before I touched it" is a far worse place to be than "I planned for this to go wrong."

The standard shape of a managed change

  1. Document the plan — what's changing, and why.
  2. Assess the risk and get the right approval — even if that's just confirming with yourself that it's reversible.
  3. Back up / snapshot first — so there's a way back if it goes wrong.
  4. Make the change.
  5. Test it.
  6. Have a rollback plan, and use it if the test fails.
  7. Document what actually happened.

This course's wiki, as a live example

Every single time this course's own wiki has been updated, that exact sequence happened: a CT 251 snapshot taken first (step 3), the new content built and checked (step 5, the mkdocs build --strict step), deployed, verified live, and logged. Nothing in this module is theoretical — it's been the actual process for every single lesson you've read in this entire A+ course.

Try it

Pick any module you've worked through in this course and name what step 3 (the backup/snapshot) actually was for that specific change.

Tip

The test-before-you're-done step matters as much as the backup — a backup only helps if you actually notice something went wrong, and checking is what makes you notice.

Play it

Open the Operational Procedures Lab and use the Change mgmt tab.

Next: Safety Procedures →