Methods
How the work gets done
Frameworks explain how to think about Editorial Intelligence.
Methods make the work repeatable.
They turn broad capabilities such as synthesis, narrative and activation into practical sequences a team can use on real research, customer evidence and editorial projects.
Frameworks
Models for understanding the problem.
Methods
Repeatable ways of doing the work.
Applications
The OS applied to a specific context.
Flagship method
Editorial Product Workflow
A repeatable eight-stage process for turning distributed evidence into a coherent editorial experience that a web team can build, publish and learn from.
Explore the workflow →Method library
Connected practices across the OS
These practices are being documented from live work. Some sit directly inside the Editorial Product Workflow; others support the wider OS. For now, they are defined together because their value comes from how they connect, not from treating each one as a standalone template.
Evidence mapping
Locate the research, customer insight, expertise and market signals already available — then expose the gaps, contradictions and unused connections.
Editorial synthesis
Move beyond summarising sources to identify patterns, tensions, useful distinctions and the argument the evidence can support.
Narrative design
Turn the strongest insight into a clear position, supporting themes and a narrative structure that can hold future evidence.
Experience design
Design how an audience moves through the knowledge before deciding what the page, hub, tool or journey should contain.
Asset mapping
Give every article, video, data point, case study and call to action a defined role within the wider editorial experience.
Customer signal analysis
Structure recurring customer language, pressures and outcomes so individual conversations strengthen a reusable evidence base.
Working principle
Document the method when a repeatable pattern appears
The aim is not to turn every useful idea into another framework. A working method belongs here when recurring steps become clear, make judgement easier to transfer and produce recognisable outputs another person could use. It should remain open to revision until further projects test it.
Start with a live problem