The methodology
The Editorial Intelligence Cycle
Editorial Intelligence is not a linear content workflow. It is a continuous learning system that transforms organisational knowledge into strategic narratives and reusable editorial assets.
Not a workflow that ends with publication.
A system that learns.
Why the cycle exists
Most organisations stop at publication.
A research report is published, used briefly, then filed. A customer story is approved, distributed, then forgotten. A framework is shared once and never updated. Each piece of work is treated as complete the moment it is produced.
Editorial Intelligence does not stop at publication.
Every article, framework, diagnostic, case study or AI workflow should generate new evidence — new questions, new signals, new patterns that the original work did not anticipate. That evidence feeds back into the next cycle, making each pass stronger than the last.
The organisation that practises Editorial Intelligence does not simply produce better content. It becomes more intelligent over time.
Explore each stage
Signals
"What should we pay attention to?"
Recognise observations with strategic potential before they disappear into the noise.
Inputs
- Customer interviews
- Research findings
- Event conversations
- Sales observations
- Product feedback
- Market data
Insights
"What does it mean?"
Connect multiple signals into meaningful patterns that reveal something strategically significant.
Outputs
- Recurring themes
- Structural tensions
- Strategic opportunities
- Industry risks
- Audience truths
Narratives
"What position should we build?"
Organise insights into strategic stories an organisation can develop and strengthen over time.
Editorial Assets
"How should we express it?"
Turn narratives into reusable forms that move across teams, audiences and time.
Outputs
- Articles
- Frameworks
- Diagnostics
- Case studies
- AI workflows
- Playbooks
Evidence
"What did we learn?"
Capture what each asset reveals after use, then feed that evidence back as new signals.
Outputs
- New customer questions
- Stakeholder feedback
- Repeated patterns
- Challenged assumptions
Worked example
Hidden Hours
A research project into operational pressure on accounting professionals — and how it became a knowledge system.
Research into operational pressure on accountants — hidden work, compliance burden, workflow friction
Admin and workflow friction are structural pressures, not individual inefficiencies
The Hidden Hours narrative — the profession absorbing structural change in silence
Articles, diagnostic tool, Editorial Intelligence Framework, AI workflow
New signals from customer stories, practitioner conversations and stakeholder use
Cycle continues — each pass stronger than the last
Related knowledge objects
Narratives
Experiments
Principles
- Knowledge before content
- Narratives over campaigns
- Evidence over assertion
- Editorial judgement before AI scale