Last month I moved a football club’s WordPress site from a local development environment to a live production server. Straightforward, in theory. In practice, the media library was broken, the database was pointing at the wrong address, and the WooCommerce shop was showing placeholder images everywhere.
It was fixed in a day. But the fix took longer than it should have, because the club had no documentation of their setup, no backup strategy, and no migration checklist.
The real problem wasn’t technical
The image files were missing because nobody had established a clear process for what “moving the site” actually meant. The developer who built it knew how to move a WordPress site. But without a documented procedure, a step got skipped — the one where you actually export and transfer the uploads folder.
This is the most common systems failure I see in small businesses: the knowledge lives in someone’s head, not in a document. Everything runs fine until that person isn’t there — or until the context changes.
Three questions to ask about any critical process
If your business has a process that depends on one person’s institutional knowledge, ask yourself: Could someone else run this process from a written description? Would they know when something had gone wrong? Do you have a way to recover if it breaks?
If the answer to any of those is “no”, you have a systems gap. It might never matter. Or it might matter a lot, at the worst possible moment.
Documentation isn’t bureaucracy. It’s the difference between a one-day fix and a three-day crisis.