Design the content cascade map
Decides which derivative formats each flagship asset spawns, the sequencing and timing across channels, and the rules for what gets repurposed versus written channel-native.
In / outFlagship content inventory + active channel list → content cascade map (formats, sequence, timing rules)
You might say…
“I write one big piece and then wonder how to make it reach people on every channel — I want a system, not a case-by-case decision each time.”
What it does
Decides which derivative formats are spawned from which flagship assets, the sequencing and timing of derivative releases across channels, and the rules for what gets repurposed versus written channel-native. Used when designing the system by which one piece of work multiplies across formats and channels.
Trigger: Use when designing the repurposing system for a body of work, before you're in production on individual pieces.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation