Why your content problems are organisational, not editorial

Why do content fixes never stick?

Because a fix changes the content without changing the system that produced it. Rewrite the weak page and the conditions that made it weak – no owner, no standards, no review date, no time – are still there, already at work on the next page. That's why content improvement so often feels like bailing.

The cycle is recognisable in most organisations. Something embarrassing surfaces; there's a clean-up, perhaps a full rewrite or a new website; everything is briefly good; then decay resumes at exactly the old rate, because nothing about how content gets made, owned and maintained has changed. The website project is the big tell – organisations rebuild their sites every few years largely because rebuilding is easier than maintaining, and then carry the same operating habits into the new CMS. New ovens, same bakery.

The pattern holds for the loaf as well as the batch: a page can be written brilliantly and still fail later, because nobody owned it, nobody updated it and nobody noticed. Time defeats talent unless the system is on talent's side.

What actually produces good content?

A working system: clear direction, a culture that values the work, capable day-to-day operations, standards for the content itself and solid infrastructure underneath. Editorial skill is one ingredient in that system – essential, but not sufficient, and not usually the thing that's missing.

Run the bakery analogy across the five areas of content maturity:

• Strategy is deciding what kind of bakery you are – what you bake, for whom, and why anyone should cross the street for it. Without it, you bake whatever each loud customer demands.
• Culture is whether the whole shop believes the bread matters – or whether baking is "something the bakers handle", done after the real work.
• Operations is the daily rhythm: who bakes what and when, how recipes are followed, what happens when someone's on holiday, who checks yesterday's stock.
• Substance is the bread itself – the only part the customer ever tastes, and the part everything else exists to serve.
• Infrastructure is the premises and the kit: ovens, mixers, supply chains, the recipe book everyone can actually find.

The point of the analogy is what it does to diagnosis. When the bread is bad, nobody assumes the answer is always "hire a better baker" – they check the ovens, the flour, the rota, the recipes. Content deserves the same breadth of suspicion. Stale pages are usually a rota problem. Inconsistent tone is usually a recipe problem. Bottlenecks are usually a workflow problem. None of these is solved at the keyboard.

Isn't this just about hiring better people?

Talented people are necessary and never enough. A skilled team inside an immature organisation produces good content heroically, intermittently and at personal cost – and the quality leaves when they do. Maturity is what lets ordinary effort produce reliably good content, instead of extraordinary effort producing it occasionally.

You can usually spot heroics-as-operating-model from the language: "it only got done because she pushed it through"; "everything goes through one person, and he's stretched"; "we know what we should be doing, we just never have time." These are descriptions of missing structure, narrated as personal virtue. The organisations involved often genuinely have the right instincts and real expertise – what they lack is the system that turns instinct into routine. Heroics also hide the problem from leadership: the bread keeps appearing, so the bakery looks fine, right up until the hero burns out or leaves.

Our content seems fine – why look upstream?

Because output quality is a lagging indicator of organisational health. Content produced by heroics looks identical to content produced by a sound system – today. The difference appears over time: how fast things decay, what breaks when a key person leaves, and what happens when volume, channels or AI raise the stakes.

Fragility shows up in questions output can't answer: Who owns this page in eighteen months? What happens to quality when the team doubles its output? Could a new starter find the standards, or do they live in someone's head? If your content is good but your honest answers are "nobody", "it slips" and "someone's head", the content is fine and the capability isn't – yet only one of those is visible on the website.

AI sharpens all of this, in both directions. Immature organisations adopt AI and get faster bread from a broken bakery – more volume through the same missing standards, absent owners and unstructured systems. Mature ones – documented standards, machine-readable governance, structured content, clear workflows – can put AI to work across creation, maintenance and quality, and compound the advantage. AI multiplies whatever operating model it lands in.

Where do you start?

By measuring the system instead of the symptoms. Assess your content maturity – strategy, culture, operations, substance, infrastructure – so you can see which parts of the bakery are actually weak, in what order to fix them, and make the case to the people who control the budget.

The diagnosis usually surprises. Teams convinced they have a quality problem discover a maintenance problem; teams asking for more writers discover the real constraint is governance or tooling. The Content Maturity assessment builds the picture from your own people's testimony – scores and explanations from across the organisation, analysed and quoted back – which is also what makes the findings persuasive upstairs: it's not a consultant's opinion, it's the organisation describing itself.

And keep checking the bread while you fix the bakery – the two views need each other. Content Health Check measures the output; Content Maturity measures the system producing it. When health scores and maturity scores both rise, you know the improvement is real and will last.

Frequently asked questions

What are the most common organisational causes of content problems?

Unclear ownership, no documented standards, no maintenance cadence, under-investment, and content treated as a task that's "done" at publication. Most organisations have several at once, and they compound: ownerless content with no standards and no review date decays on schedule, whoever wrote it.

How can you tell whether a content problem is editorial or organisational?

Ask whether it recurs. A weak page is editorial; weak pages appearing faster than you fix them is organisational. One-off errors are editorial; the same inconsistencies across teams and channels are organisational. If a problem survives the people who caused it, it isn't a people problem.

Does this mean editorial skill doesn't matter?

It matters enormously – it's just not usually the binding constraint. Mature organisations are where editorial skill pays off most, because good work gets maintained, reused and built upon instead of decaying. Maturity doesn't replace talent; it stops talent being wasted.

What's the first step towards fixing organisational content problems?

Get an honest picture of where you stand. Run a content maturity assessment across a genuine cross-section of colleagues, see where the five areas are strong and weak, and pick the one or two gaps that explain most of your symptoms. Then fix those – not the pages – first.

---

Suspect your bakery, not your bakers? Content Maturity assesses how your organisation really makes content – across strategy, culture, operations, substance and infrastructure – and shows you what to fix first.