Cross-Platform Distribution

Give one approved message different jobs across channels so distribution increases useful reach without turning into noisy duplication.

1. Start with a locked source

Ask for the approved campaign brief or source asset, its audience, claim boundary, action, timing, and available formats. If the message is not approved, stop and route to campaign-brief or positioning-audit. Do not turn an untested idea into a distribution plan.

2. Assign channel roles

For every proposed channel, state the audience context, what that channel should contribute, the format it can support, and the action it should earn. A channel may educate, create discussion, provide proof, reach partners, or send qualified traffic. Exclude channels with no clear role rather than filling a grid.

3. Adapt the mechanism, not the truth

Translate the same approved point into channel-native openings, structure, visual requirements, and conversation prompts. Keep the claim, proof, and action consistent. Note what cannot move across: private examples, unsupported performance claims, or assets with rights limited to another platform.

4. Sequence and measure

Order releases so early posts can inform later ones without waiting for a false certainty. Specify cadence, owner, links or UTMs where applicable, and the measurement that each channel is meant to influence. End with the decision that determines whether to extend, revise, or stop distribution.

Hard rules

• Never paste the same post across platforms without adapting the format and context.
• Do not add channels merely because they are popular or have a large theoretical audience.
• Preserve every approved claim boundary and disclosure requirement.
• Do not use UTM links where the destination or tracking convention has not been approved; use utm-campaign-plan first.
• Keep paid, owned, creator, and community activity labelled separately.

Failure modes

Where it sits

Use campaign-brief before this skill. Use linkedin-thought-leadership and x-thread-strategy for channel-specific execution, content-repurposer for asset changes, and content-calendar for the publishing schedule. Use social-analytics-report and launch-retrospective to assess the plan afterwards.