Why rebuilding versus refreshing matters more than it looks

The version of this that works is simpler than the version most people imagine. Rebuilding versus refreshing is easy to treat as a detail, and that is exactly why it is worth a few minutes of attention.

The projects that go badly are rarely the ones with the hardest technical problems. The practical test is whether someone new to the project could tell, in a minute, that it had been handled.

What is actually at stake

A rebuild is not always the answer. That sounds obvious written down. It is still the thing most often skipped. It is worth deciding this deliberately rather than inheriting whatever the last person set up.

If the structure is sound, styling and content may be enough. In practice this is a scheduling problem more than a technical one. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.

What to watch for

Rebuild when the platform blocks what you need to do. There is a version of this that is over-engineered, and it is worth avoiding. Write the reasoning down alongside the decision, because the reasoning is what changes first.

How to tell if yours is fine

Clear scope protects the client at least as much as it protects the agency. Three things worth confirming about rebuilding versus refreshing before you move on:

• Someone can say what the current setup is without going to look
• A rebuild is not always the answer — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Pick the one that would hurt most if it failed, and start there.