How content systems design works

Know what your content can actually support.

The Content Capability Assessment turns the real state of your content into an Enterprise Content Capability Profile – a decision baseline showing where transformation investment will succeed, and where it will stall.

The method

Start with the decision baseline.

The method produces the Profile first: a clear read on what can move now, what needs content-system work first, and where the next investment is carrying risk.

01

Assessment

Content Capability Assessment™

One integrated assessment – run through the Content Infrastructure Diagnostic™ (CID™) – that reads the real state of your content and turns it into a decision-ready picture, built in three moves.

Domain capability assessment Score each domain's content capability across Substance, Structure, and Governance criteria.
Content ecosystem mapping Cross-domain scores combined into a weighted ecosystem – a clear picture of the whole organisation's content capability.
Systems capability mapping The ecosystem read translated into which initiatives are ready to run now, and which are constrained until the content system is fixed.
Produces your Enterprise Content Capability Profile
02

Design

Content System Blueprint

A channel-agnostic system built once and used wherever the organisation needs reliable content.

Substance Narrative Terminology Guidance Claims Documentation
Structure Models Templates Taxonomy Metadata IA
Governance Ownership Review Standards Workflows Agentic context
03

Execution

Channels and platforms

The designed system is installed in the channels and platforms where the work actually happens.

Websites Product UI Knowledge bases Support centres AI environments

Outcome: one coherent content system – consistent, reusable, maintainable, migration-ready, and interoperable across channels.

Phase 1 · Content Capability Assessment™

Assess every domain, map the ecosystem, read what you can build on.

The Content Capability Assessment is run through the Content Infrastructure Diagnostic™ (CID™) – the engine that scores and maps content capability against three criteria layers, Substance, Structure, and Governance. It runs end to end across three stages that converge into a single deliverable.

The Content Infrastructure Stack · Assessment criteria

Every domain is read through the same three-layer stack and its twelve criteria – each scored out of 10 against a strict, repeatable rubric.

Substance

Content quality
  • Purpose
  • Accuracy
  • Clarity
  • Consistency

Structure

Semantic architecture
  • Taxonomy
  • Metadata completeness
  • Information architecture
  • Page templates & content models

Governance

Operations & system controls
  • Roles & responsibilities
  • Lifecycle workflows
  • Standards, policies & enablement
  • Tool & system governance

Stage 1 · Domain capability assessment

Each content domain is scored criterion by criterion. The UX content system, for example, shows whether product-app experiences are clear, consistent, and structured enough to support interface quality, design-system reuse, and in-product AI guidance.

UX

SUBSTANCE STRUCTURE GOVERNANCE

Aggregated domain capability

6.7
Medium capability
Substance7
Purpose8
Accuracy7
Clarity7
Consistency6
Structure5
Taxonomy5
Metadata completeness4
Information architecture6
Page templates & content models5
Governance8
Roles & responsibilities8
Lifecycle workflows8
Standards, policies & enablement9
Tool & system governance7

Illustrative. One of four domains; each is assessed the same way against all twelve criteria.

Stage 2 · Content ecosystem mapping

The four domain diagnostics are combined and weighted into one ecosystem view – the four domains standing in as proxies for organisational knowledge: Brand as identity, Marketing as commercial understanding, UX as execution knowledge, Knowledge as operational knowledge.

Brand

Substance: 8 | Structure: 4 | Governance: 3

Marketing

Substance: 6 | Structure: 7 | Governance: 5

UX

Substance: 7 | Structure: 5 | Governance: 8

Knowledge

Substance: 4 | Structure: 3 | Governance: 2

Aggregated content capability

5.2
Constrained
Substance 6.3
Structure 4.8
Governance 4.5

Aggregated profile represents an illustrative diagnostic. Real client values are generated from a live CID™ diagnostic.

Stage 3 · Systems capability mapping

Each domain's aggregated health is translated into the channel-bound capabilities it actually feeds – what is ready to run now, and what is constrained until the content system is fixed.

Brand

5.0
Medium capability
Corporate narrative & brand contentMedium
Brand voice & terminology governanceMedium
AI brand-voice agentLow

Marketing

6.0
Medium capability
Website proposition & conversionHigh
Campaign & lifecycle messagingMedium
AI marketing production & orchestrationMedium

UX

6.7
Medium capability
Product interface copy systemHigh
Design-system content integrationMedium
In-product AI guidance & copilotsLow

Knowledge

3.0
Low capability
Customer knowledge base & self-serviceLow
Technical & product documentationMedium
Customer support answer assistantLow

Cross-domain capabilities · determined by the whole ecosystem

Website transformation All four domains converge on one platform. High capability
Conversational knowledge retrieval External: customer support answer assistants. Internal: staff knowledge retrieval assistants. Both answer from governed content. Low capability
Agentic workflow automation External: support escalation and answer maintenance. Internal: content production, QA, and publishing workflows. Low capability

Capability shows what the organisation can reliably execute today based on current content infrastructure – explicitly not a maturity grade. Illustrative example.

The deliverable

Your tailored Enterprise Content Capability Profile.

The three stages produce one artefact: an evidence-rich, qualified picture of content health across every domain and channel – the baseline your next transformation investment can depend on and be prioritised against. Not a standard content audit report; a practical resource for planning digital platform investments.

Enterprise Content Capability Profile Sample organisation Illustrative dashboard view

Domain-level capability assessment

Brand

Substance: 8 | Structure: 4 | Governance: 3

Marketing

Substance: 6 | Structure: 7 | Governance: 5

UX

Substance: 7 | Structure: 5 | Governance: 8

Knowledge

Substance: 4 | Structure: 3 | Governance: 2

Overall Content Capability Score

Constrained
5.2

Breakdown by diagnostic layer

Substance 6.3
Structure 4.8
Governance 4.5

Systems capability map

Website transformation High capability
Campaign & lifecycle messaging Medium capability
Technical & product documentation Medium capability
Customer support answer assistant Low capability
Agentic workflow automation Low capability

Illustrative example. Real client values are generated from a live CID™ diagnostic.

Why this matters

The Profile turns the diagnostic into an investment baseline. It shows which initiatives can move now, which need content-system work first, and where sequencing risk is being hidden by optimistic programme language – the evidence beneath transformation, budget, hiring, governance, and AI-sequencing decisions.

Phase 2

Content systems: design, development, and production.

The Profile's capability map weights and sequences what gets built first. Every content system is then built and handed over as a structured, channel-agnostic folder of mostly-Markdown files, version-controlled like a codebase. Substance/ holds the canonical meaning; Structure/ makes it reusable; Governance/ keeps it reliable for people and machines, with agentic context added inside Governance where AI is in scope.

Universal elements of a designed content system.

The same basic handover shape sits underneath each domain-specific system.

example-org – content system template
$ define system -> operate across channels
Substance/ The meaning and reusable content assets the system draws from. Structure/ The models, templates, taxonomy, and metadata that make it usable. Governance/ The ownership, workflows, standards, and agentic context that keep it reliable.

Illustrative domain-specific content systems.

Click each example to get a feel for what the system would typically contain once the universal template is adapted to a specific content domain. In practice, these are usually scoped to a real channel, product, workflow, or platform – a product's UI strings, a help centre, a technical documentation set, an internal staff knowledge base – rather than a generic domain in the abstract.

Brand content systemVoice, terminology, claims, proof. Click to expand 
brand-content-system/
  Substance/
    corporate-narrative.md
    voice-and-tone.md
    approved-terminology.md
    claims-and-proof/
    examples-and-anti-examples.md
  Structure/
    messaging-architecture.md
    terminology-model.md
    reusable-narrative-components/
  Governance/
    ownership.md
    review-and-approval-workflow.md
    terminology-change-control.md
    qa-and-drift-checks.md
    agentic-context.md where AI is in scope
    retrieval-and-validation-rules.md

Operational channels: website, campaigns, sales and partner materials, executive comms, AI-supported content workflows.

Marketing content systemPositioning, propositions, offers, proof. Click to expand 
marketing-content-system/
  Substance/
    audiences-and-segments.md
    offers-and-propositions.md
    objections.md
    proof-points/
    cta-language.md
    messaging-hierarchy.md
  Structure/
    offer-models.md
    landing-page-templates/
    campaign-taxonomy.md
  Governance/
    claim-governance.md
    adaptation-and-reuse-rules.md
    experimentation-and-variant-testing.md
    performance-review.md
    agentic-context.md where AI is in scope
    briefing-and-retrieval-rules.md

Operational channels: website, landing pages, campaigns, email, sales enablement, partner channels, AI-assisted marketing.

UX content systemInterface language, guidance, product terms. Click to expand 
ux-content-system/
  Substance/
    app-name/
      screen-strings/
      flow-copy/
      labels-and-navigation.md
      forms-and-validation.md
      errors-and-empty-states.md
      notifications.md
      onboarding.md
    product-terminology.md
    interaction-principles.md
  Structure/
    screen-inventory.md
    ui-string-schema.md
    localisation-keys.md
    component-content-models.md
    journey-content-map.md
  Governance/
    release-triggers-and-change-control.md
    ui-copy-qa.md
    accessibility-review.md
    design-system-content-ownership.md
    agentic-context.md where AI is in scope
    prompt-and-context-rules.md

Operational channels: product UI, onboarding, design systems, in-app guidance, support prompts, in-product AI copilots.

Knowledge content systemDocumentation, support, procedures, answers. Click to expand 
knowledge-content-system/
  Substance/
    help-centre/
      support-articles/
      troubleshooting-guides/
      answer-patterns.md
    technical-documentation/
      reference/
      procedures/
      release-notes/
    staff-knowledge/
      policies-and-procedures.md
      internal-guidance/
      canonical-product-truths.md
  Structure/
    article-types.md
    metadata-schema.md
    decision-trees/
    audience-and-permission-model.md
    version-relationships.md
  Governance/
    maintenance-and-escalation-triggers.md
    answer-review-workflow.md
    documentation-ownership.md
    staff-knowledge-review.md
    failure-review.md
    versioning-and-deprecation.md
    quality-review.md
    retrieval-rules.md
    agentic-context.md where AI is in scope
    source-priority-rules.md
    retrieval-boundaries.md
    confidence-thresholds.md
    handoff-rules.md

Operational channels: help centres, documentation platforms, in-product help, support assistants, internal knowledge bases, AI-assisted resolution.

Phase 3

Operationalisation installs the system where the work happens.

The designed system feeds every channel and platform – the same governed source content, drawn on wherever the organisation needs reliable content.

Content as infrastructure: brand, marketing, UX, and knowledge content systems feeding website, mobile app, help centre, and AI tools.

Where AI is in scope, operationalisation deepens into machine-operable context: retrieval logic, source-priority rules, evaluation criteria, context wrappers, and operating boundaries.

Start with the content system, not the next tool.

A free 30-minute conversation about what your current content can support, what it cannot, and where the next investment is carrying risk. No pitch.

Book a diagnostic conversation