Engine iii
Content and campaigns
Creative direction, campaigns, film and editorial.
The problem it solves
Why this leaks.
Output is high, reuse is near zero, and the same brief gets re-solved every quarter. Creative quality depends on who happened to be available, and nobody can find last year’s assets or say what they achieved.
What you get
The deliverables.
Creative direction
The visual and editorial point of view, set at the level of the system rather than the individual asset.
Campaign architecture
What the campaign is arguing, to whom, in what sequence, and how each piece hands to the next.
Editorial and content systems
Formats, templates, tone and a production calendar that a team can run without re-inventing the approach.
Photo, film and production
Shoots planned to feed the system — one production yielding assets across channels and quarters.
Media planning and orchestration
Where the work runs, in what order, and how performance feeds the next brief.
How it runs
Five steps, in order.
Direct
Establish the creative and editorial point of view.
Structure
Build formats, templates and the production pipeline with explicit ownership.
Produce
Shoot, write, edit and assemble against the system.
Orchestrate
Sequence release across channels.
Recycle
Version, tag and register assets so the next campaign starts ahead.
Recognise this?
Signs you need this engine.
- You produce constantly and can never find anything.
- Every campaign starts from a blank page.
- Quality swings depending on who picked up the brief.
- A shoot produces assets for one channel and one month.
Register nodes
The nodes behind it.
Start with the pipeline.
Begin with the audit, or go straight to a System Build if the problem is already clear.
The other engines