Product Growth & Operations

Content Distribution & Repurposing Strategy

Description

Create a content distribution and repurposing strategy. Split core content assets into multi-channel reusable formats, define channel fit, repurposing templates, cadence, and measurement to reduce marginal content cost and improve reach and conversion.

Cursor / Claude Code Instruction

There is a prompt instruction at https://www.zangwei.dev/prompts/product-growth/content-distribution-repurposing-strategy-prompt . Extract and follow the prompt to create file /docs/handbook/growth/content-distribution.md

Prompt Content

You are a senior Content Growth Lead. Design a **Content Distribution & Repurposing Strategy** that turns content from "one-off output" into "reusable assets".

## Positioning
- Goal: reuse one piece of content across channels to reduce marginal cost and increase reach/conversion
- Output must include: content types, channels, repurposing templates, and execution cadence

---

## Output structure

1) Goals & constraints
- goals (brand / acquisition / education / conversion)
- target audience and core intent
- available resources and publishing frequency

2) Content asset taxonomy
- Pillars (core content pillars)
- Derivatives (repurposed pieces)
- Conversion assets (assets designed for conversion)

3) Channel-content fit
For each channel (SEO / social / community / email / external platforms, etc.), specify:
- suitable content formats
- frequency and best timing windows
- success signals (reach / engagement / conversion)

4) Repurposing templates & workflow
- How one piece becomes: short posts / long-form / video script / FAQ / comparison page
- Standard templates and checklists
- Repurposing cadence (Day 1 / Day 7 / Day 30)

5) Measurement & iteration
- key metrics and review cadence
- what content should be updated, merged, or removed
- next-round improvements to the repurposing system

---

## Output requirements
- Avoid generic "post everywhere" advice
- Provide an executable repurposing structure and cadence
- Avoid vague terms like "optimize"
- Tie improvements to specific frictions and verifiable actions where applicable