When to fix content, when to fix IA, and when to fix team rhythm

“Performance is bad” is a single sentence that hides a lot.

Most issues fall into one of three buckets:

• Content: what you're saying and how well it answers real questions.
• Information architecture: how pages connect and how people move.
• Team rhythm: how decisions get made, and how work gets shipped.

If you treat all three as “content problems,” you'll keep pulling the wrong lever.

You probably have a content problem if:

• Pages are clearly off-intent — they don't answer what the query or user actually implies.
• The right topics aren't covered at all, or only in shallow, generic ways.
• When you read the page, you genuinely wouldn't trust it enough to act on it.

Here, rewriting, expanding, or creating new content is the right move — once structure and ownership are clear.

You probably have an IA problem if:

• People land on sensible pages but have nowhere obvious to go next.
• High-intent pages exist, but they're buried or hard to reach.
• Important hubs are fragmented across multiple URLs with no clear hierarchy.

In this case, rewriting copy won't do much. You need to fix how the estate is organised, named, and connected.

You probably have a rhythm problem if:

• Work happens in frantic bursts around campaigns or reporting deadlines.
• There's no predictable cadence for audits, updates, or experimentation.
• Decisions depend heavily on individuals, not on clear standards.

Here, any content or IA work will degrade over time unless you change how the team operates.

A simple order of operations:

1. 01Get a clear view of the estate (diagnostics).
2. 02Fix obvious IA blockers that stop people reaching the right places.
3. 03Upgrade the content that sits at key junctions — the places where intent and money meet.
4. 04Put a basic rhythm in place so you revisit and evolve, instead of doing this once and forgetting.

You don't need a perfect system. You need a system that's good enough to make future changes easier, not harder.