What this can look like in practice
A single symptom rarely tells the whole story. These are some of the signs worth checking before deciding what needs to change.
- A small number of pages cause most of the problems
- The site works but messaging and calls to action are weak
- Technical problems repeatedly return after patches
- The content model cannot support current services or markets
- The team cannot safely maintain or measure the site
What to check next
Start with the parts that can be verified. This helps avoid expensive changes based on assumptions.
- List the failures before listing desired design features
- Estimate whether each failure is local or structural
- Protect URLs and content that already perform useful work
- Compare repair cost with the operational cost of retaining the constraint
- Choose the smallest intervention that resolves the real problem
Decision point
The practical takeaway
The correct scope can be a targeted repair, partial redevelopment or full rebuild. Diagnosis should decide.