Content ideas are useful when they connect a real audience situation to credible evidence and a channel-native action. A long list of hooks without context may create drafts, but it does not create a defensible editorial system.
Download the 100-idea library
The library contains 100 rows across ten families: audience questions, practical education, evidence and research, product understanding, customer proof, people and process, community participation, timely interpretation, objection handling, and experiments.
Every row includes an audience job, prompt, evidence requirement, suggested formats, channel role, call to action, risk check, and repurposing path. Filter the sheet instead of copying every prompt into the calendar.
Turn an idea into a usable brief
Choose the audience and situation first. Replace generic placeholders with the exact problem, constraint, misconception, desired progress, and level of prior knowledge. State why the brand has the right to address it.
Add proof before writing the hook. Evidence may come from product data, a customer interview, an accountable expert, original research, primary documentation, an observed workflow, or a transparent experiment. If the idea is opinion, label it as opinion and explain the experience behind it.
Define the stable core and the channel adaptation. The stable core includes the audience problem, claim, evidence, and boundaries. The opening, length, visual structure, interaction, and call to action should fit the destination.
Use prompt families intentionally
Education prompts explain a method, decision, mistake, tradeoff, or checklist. Proof prompts show evidence, process, before-and-after conditions, limitations, and what changed. Product prompts connect a user job to a real workflow rather than listing features.
Community prompts invite useful participation: examples, questions, experience, critique, local context, or shared problem solving. They should not manufacture engagement through empty requests.
People and process prompts can show operators, creators, support teams, design choices, failures, and corrections without exposing private staff or confidential work. Timely interpretation prompts add accountable context to news rather than repeating it.
Experiment prompts define a question and comparison before publishing. The result becomes another asset only after the method and uncertainty are preserved.
Review quality, rights, and repetition
Before scheduling, check source freshness, claims, customer consent, employee privacy, music and visual rights, disclosures, accessibility, product availability, links, and the exact approved version. AI-assisted drafts need the same evidence and review as human drafts.
Track which audience jobs, pillars, formats, and prompts have recently shipped. Rotate the underlying question, evidence, example, and interaction—not only the wording. A library should reduce blank-page time without making the account sound mechanically repetitive.
Idea selection checklist
- Audience, situation, problem, and desired progress are specific
- Brand relevance and evidence are credible
- Fact, opinion, hypothesis, and promotion are clearly separated
- Format and channel role fit the destination
- Rights, privacy, disclosure, accessibility, and claim risks reviewed
- Call to action matches the audience's current readiness
- Source idea and future variants remain linked
- Result and next learning will be recorded after publishing
Move selected ideas into the campaign brief, content calendar, and repurposing map.
