Expand one evidence-backed topic into distinct audience questions and a coherent publishing sequence
8 min setupTested with:ChatGPTReviewed: 2026-08-28
1
Add your context
Your text stays in this browser. AILesson Prompts does not send it to a model or server.
2
Your prompt
Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt
Turn the supplied topic into a useful content series without padding or unsupported claims.
Topic, boundaries, viewpoint, and invariant facts:
[topic]
Audience situations, questions, knowledge, objections, action, and goal:
[audience]
Approved sources, channels, count, formats, cadence, capacity, and prohibited claims:
[sources]
Build an audience question tree before proposing titles. Separate foundational, diagnostic, how-to, comparison, mistake, example, objection, decision, and follow-up angles only where evidence supports them. Each item must answer a different primary question and contribute a distinct step in the series. For every item give working title, audience need, promise, key points, evidence locator, format and channel, CTA, dependency, reuse opportunity, production effort, and success signal. Label source gaps and validation ideas; never invent trends, statistics, experience, quotes, or examples presented as real. Remove overlapping ideas, sequence prerequisites before advanced use, balance evergreen and timely material using only confirmed dates, and identify one anchor asset. End with coverage, repetition, evidence, and workload audits.
Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.
From input to outcome
A worked example
See how concrete context turns this recipe into a usable result
Actual input
Topic and boundaries
Reducing unclear work handoffs in small operations teams. Include role clarity, acceptance criteria, status visibility, and escalation. Exclude claims that one tool eliminates coordination. Viewpoint: improve the workflow before adding software.
Audience and purpose
Operations leads at 20-80 person companies. They notice overdue tasks but often cannot locate where a handoff broke. Goal: help them run a workflow audit and download our checklist. They know project tools but not process mapping.
Sources and production limits
Approved: internal handoff-audit checklist; anonymized interviews with 10 operations leads, 7 mentioning unclear ownership; one fictional demonstration process clearly labeled. Six LinkedIn posts and one newsletter over four weeks; one writer, one simple visual weekly. No industry prevalence claims.
Example output
Anchor asset: the newsletter “Audit a handoff from request to acceptance,” grounded in the approved checklist. It supplies the reusable framework for the posts.
Diagnostic — “Where did this handoff actually break?” Need: distinguish overdue symptom from process failure. Cover request, owner, acceptance, visibility, and escalation checkpoints. Evidence: checklist sections 1-5. Format: LinkedIn text diagram; CTA: mark one failed checkpoint; signal: saves.
Evidence angle — “Seven interviewees named unclear ownership—what that does and does not show.” Explain the 7-of-10 sample without generalizing prevalence. CTA: compare one team handoff; signal: qualified comments.
How-to — “Write acceptance criteria the receiver can test.” Use checklist method and a clearly labeled fictional example. Dependency: item 1. Carousel; one weekly visual.
Mistake — “A status field cannot repair a missing decision owner.” Contrast visibility and accountability without claiming tools are useless.
Objection — “We are too small for process mapping.” Offer a five-minute, one-handoff version from the checklist; do not present an unmeasured time saving.
Decision — “When workflow repair is enough—and when a tool may help.” Give criteria, not a product guarantee. CTA: download the audit checklist.
Week 2 newsletter expands items 1 and 3; posts sequence diagnosis, evidence, method, mistake, objection, decision across four weeks. No item claims industry prevalence or elimination of coordination. Writer load is seven units; verify capacity because only visual capacity was quantified.
Why this works
1
Question-first expansion creates meaningful depth instead of title variations.
2
Evidence and workload fields keep the series credible and producible.
Check the result
Does every item answer a distinct audience question?
Can every factual promise be traced to an approved source?
Do sequence and effort fit prerequisites and capacity?
ChatGPT