How do you measure content maturity?

Why measure through people rather than artefacts?

Because capability lives in how people work, not in the artefacts they could show you. A style guide can exist and be ignored; a workflow can be documented and routinely bypassed; a strategy deck can be beautiful and dead. Artefacts prove that something was made once – only people can tell you what actually happens.

Consider what the five areas of content maturity contain: whether leadership genuinely backs content, whether audience needs survive contact with internal politics, whether maintenance happens when nobody's watching, whether collaboration works or merely occurs. None of this is visible to a crawler, and most of it is invisible even to a document review. An automated audit can assess your content – that's exactly what a content health check does, and the output view matters. But the capability behind the output is social, procedural and cultural, and the only instrument that reaches it is a well-structured question put to the people inside it.

The practical consequence: measuring maturity is less like instrumenting a system and more like taking a clinical history – from several patients who all live in the same body.

Isn't self-assessment just subjective?

The score alone would be. That's why the score is the smallest part of the method: every rating comes with an explanation, every conclusion is triangulated across multiple respondents, and the findings are grounded in what people actually wrote rather than how they felt on a scale. Structure is what turns opinion into evidence.

Four mechanisms do the work:

• The explanation outranks the number. For each aspect, respondents score the organisation from 1 (immature) to 5 (mature) – and then answer "why did you choose this score?" The number anchors; the reasoning is the data. A 3 justified by "we have guidelines but nobody uses them" tells you more than the 3 does.
• Multiple respondents triangulate. One person's view is an opinion; the same observation arriving independently from five departments is a finding. Capability looks different from the comms desk, the leadership team and the front line – the method wants all of those vantage points on record.
• Disagreement is measured, not averaged away. Where colleagues converge, you have confidence; where they diverge, you have a discovery – usually that one team has solved something locally, or that leadership believes a thing the people downstream know isn't true. The assessment reports agreement explicitly rather than burying it in a mean.
• Prompts calibrate the scale. Each aspect comes with context and "things to consider" – concrete questions about what mature practice looks like – so respondents score against a shared reference rather than a private hunch.

One quirk worth knowing: self-assessment skews harsh as often as generous, because the people closest to the work see every gap. That's fine. The percentages matter for their shape and their movement over time, not as a grade – and the explanations keep everyone honest in both directions.

What does the assessment actually ask?

For each of the 29 aspects in the framework, respondents get a short description of what the aspect covers, prompts on what to consider, a five-point scale from immature to mature, and one open question: why did you choose this score? Simple to answer, structured enough to aggregate.

The framework behind the questions is where the rigour sits: five areas (strategy, culture, operations, substance, infrastructure), 29 aspects within them, and 90 indicators describing what mature practice concretely looks like – evergreen content systematically maintained, governance documented and machine-readable, user research feeding decisions. Respondents don't need to know any of that taxonomy; they answer plain questions about how things really work. The structure does its job afterwards, in the analysis.

How are the answers turned into results?

Scores aggregate into percentages – overall, per area, per aspect – while our AI-powered engine analyses the explanations, synthesising findings at every level and grounding each one in direct quotes. The result is a picture with three layers: numbers for shape, analysis for meaning, quotes for proof.

The traceability is the point. Every synthesised finding – "planning is inconsistent across teams", "maintenance is unowned" – sits alongside the anonymised words of the colleagues who said so, which means nothing in the report has to be taken on trust: you can follow any conclusion back to its evidence. (It's also what makes the results so useful for making the case for investment – the findings arrive in the organisation's own voice, not the assessor's.)

Agreement gets the same treatment: results show not just what respondents think but how strongly they concur, across aspects and between respondents – so you can tell a settled finding from a live argument at a glance.

Who should take part?

A genuine cross-section: the content and comms specialists, the leaders who set priorities and budgets, and the people across the organisation who make content without "content" in their job titles. Maturity is organisational – a specialists-only assessment measures one room and misses the gaps between rooms, which is where capability actually fails.

Include the sceptics deliberately. Their answers are data like everyone's, their blind spots show up in the divergence, and their participation means the findings arrive pre-endorsed – it's hard to dismiss a report your own answers are in. Numbers matter less than spread: a handful of well-chosen respondents from genuinely different vantage points beats a large sample from one department.

Frequently asked questions

How is this different from a consultant doing interviews?

It's the same instinct, systematised. A good consultant also asks people and synthesises – but one interpreter, a limited interview round and an unstructured synthesis make the result expensive, slow and hard to repeat. A structured assessment captures more voices, analyses them consistently, keeps the quotes, and can be re-run to measure change.

Can AI really analyse qualitative answers reliably?

For this job, yes – synthesis across many free-text answers is precisely what it's good at, and the method keeps it accountable: every finding is grounded in direct quotes, so you can check any conclusion against what respondents actually wrote. Our AI-powered engine organises the evidence; it doesn't get to assert anything the evidence doesn't show.

Should respondents' answers be anonymous?

Candour matters more than attribution, so lean towards confidence: people describing broken workflows or absent leadership support need to know honesty is safe. Quotes in results work fine unattributed – it's the pattern across respondents that carries the finding, not who said which sentence.

What if respondents disagree wildly?

Then you've learned something important. Wide divergence (the tool shows you this too) usually means experience genuinely differs – one team has working processes others lack, or leadership's view of capability doesn't survive contact with the people downstream of it. Treat the disagreement as a finding to investigate, not noise to average out.

Can you benchmark against other organisations?

Comparison over time and across areas is the primary lens – your own trend is the benchmark that drives action. Cross-organisation benchmarking is on our roadmap, and percentages will make it natural when it arrives; but "better than last year, in the areas we invested in" is already the comparison that matters.

---

See the method in action: Content Maturity puts the questions to your organisation and turns the answers into evidence – percentages, findings and your colleagues' own words. Explore the framework behind it.