Content Frameworks
This reference captures practical frameworks for generating and shaping web writing.
Framework 1: Three Content Buckets
Pick a subject, then frame it for three audience depths:
- General audience
- Niche audience
- Industry audience
Rule: Pre-define Audience Depth Before Drafting
Description: Decide which bucket you are writing for before choosing examples and terminology. Negative example: Writing a post that switches between beginner and expert assumptions every paragraph. Positive example: One post written for niche readers with niche vocabulary and explicit prerequisites.
Rule: Reuse One Topic Across Buckets
Description: Turn one core idea into multiple versions by changing audience depth, not by changing your entire topic. Negative example: Abandoning a useful topic because one version underperformed. Positive example: Rewriting a general piece into a niche version with stricter constraints and context.
Framework 2: Endless Idea Generator
For each topic:
- Choose one 4A angle:
- Actionable (how)
- Aspirational (yes, you can)
- Anthropological (here is why)
- Analytical (here are the numbers)
- Choose a proven container:
- Tips, mistakes, lessons, reasons, trends, examples, how-to, habits
- Add credibility context:
- first-hand experience, curated sources, or measurable evidence
Rule: Lock Angle Before Container
Description: Pick the 4A lens first so the piece has a clear intent. Negative example: Mixing analytical claims with motivational framing and no shared logic. Positive example: Analytical lens paired with a trends container and data-led evidence.
Rule: Keep Promise and Evidence Type Aligned
Description: Match your claim style to your proof style. Negative example: Strong numeric promise with only anecdotal support. Positive example: Numeric promise with trend data and clear caveats.
Framework 3: Curiosity Gap
Strong headlines and lead-ins answer three questions:
- What is this about?
- Who is this for?
- Why should this reader continue?
Then they withhold only the middle detail, not the core promise.
Rule: Clear Before Clever
Description: Prioritize immediate comprehension over stylistic novelty. Negative example: Vague poetic headline that hides topic and audience. Positive example: Specific headline naming audience, topic, and promised outcome.
Rule: Curiosity Without Betrayal
Description: Do not treat the headline as a separate artifact from the body. Negative example: High-drama hook followed by generic, recycled advice. Positive example: Hook promise repeated and fulfilled in the opening section.
Framework 4: POP Writing
Strong internet writing often combines three dimensions:
- Personal: lived detail and honest perspective
- Observational: insight, pattern recognition, and interpretation
- Playful: memorable phrasing, light wit, and linguistic energy
Rule: Balance POP Dimensions by Context
Description: Tune personal, observational, and playful intensity to audience and purpose. Negative example: Corporate explainer overloaded with jokes and no substance. Positive example: Technical post with clear analysis, one personal detail, and light phrasing for memorability.
Rule: Personal Detail Must Serve Reader Insight
Description: Personal stories should clarify a lesson, not become self-focused digression. Negative example: Extended autobiographical section with no practical connection. Positive example: Brief personal example tied directly to a reader-relevant takeaway.
Rule: Keep Playfulness as a Condiment
Description: Use creative phrasing to improve recall, not to replace clarity. Negative example: Clever wordplay that obscures the actual point. Positive example: One memorable phrase that sharpens, rather than hides, the argument.
Framework 5: Key Idea Compression
Before drafting, compress the piece into one smallest viable idea that every section supports.
Rule: Define One Core Idea Per Draft
Description: Name the single idea that the piece will prove or teach. Negative example: One article trying to explain an entire worldview. Positive example: One focused claim that all examples, sections, and transitions reinforce.
Rule: Use a Working Coined Phrase
Description: Give the core idea a short, memorable label during drafting. Negative example: Repeating a long abstract concept with inconsistent wording. Positive example: One concise phrase reused across title, subheads, and conclusion.
Rule: Cut Sections That Do Not Orbit the Core
Description: Remove tangential material even if it is interesting on its own. Negative example: Keeping unrelated backstory because it is well written. Positive example: Trimming side paths to preserve a tighter, more coherent argument.
Framework 6: Signal Mining Matrix
Build ideas by combining three signal sources:
- Audience language: pain points, failed attempts, and desired outcomes.
- Competitor patterns: formats, hook styles, and proof types that repeatedly perform.
- Trend context: breaking news or rising themes with clear audience relevance.
Rule: Capture Failed-Strategy Language Verbatim
Description: Save the exact words people use to describe what they tried and why it failed. Negative example: Logging only broad topics like "lead generation" with no context. Positive example: Capturing specifics like "webinars brought signups but no qualified follow-up calls," then building copy around that failure pattern.
Rule: Mine Components, Not Copies
Description: Study high-performing posts for reusable mechanics instead of replicating their exact topic. Negative example: Rewriting a competitor's post with minor wording changes. Positive example: Reusing the same structural pattern (hook type + proof style + CTA form) with original evidence and angle.
Rule: Convert Trend Inputs Into a Distinct Angle
Description: For trend-based posts, choose one angle before drafting: prediction, contrarian interpretation, or actionable takeaway. Negative example: Reposting trend headlines without an original stance. Positive example: Using a breaking update as context, then sharing one specific "what to do now" recommendation.
Rule: Repeat Winning Formats With One Controlled Variable
Description: Keep a stable structure so the core idea remains clear and easy to follow. Negative example: Changing structure repeatedly inside one piece and confusing the reader. Positive example: One consistent structure where topic, proof, and CTA align around a single message.
Framework 7: Mini-Payoff Chain
For longer posts and threads, create momentum through repeated value beats:
- Open a question or tension.
- Resolve it with a concrete mini payoff.
- Immediately set up the next question.
Rule: Resolve One Loop Before Opening the Next
Description: Give a clear answer before introducing new tension. Negative example: Stacking three unresolved questions before any concrete payoff appears. Positive example: Answering one key question in two lines, then bridging to the next with a clean transition.
Rule: Make Every Mini Payoff Actionable
Description: Each resolved loop should deliver a usable insight, not only narrative progression. Negative example: A dramatic reveal that adds excitement but no practical takeaway. Positive example: Each resolved beat includes one specific lesson, example, or decision rule.
Framework 8: Conversion Clarity Sequence
For conversion-oriented writing (sales pages, launch emails, offer sections), sequence ideas in this order:
- Clear value proposition (what, for whom, and outcome).
- Pain and stakes (what fails without change).
- Solution mechanism (how this works).
- Benefit translation (feature -> practical result).
- Proof and objection handling.
- One explicit next step.
Rule: State Who It Is For and Not For
Description: Qualification language increases trust and reduces low-fit action. Negative example: "This is for everyone who wants success." Positive example: "Best for first-time creators shipping weekly; not ideal for teams needing enterprise governance workflows."
Rule: Translate Features Into Job-to-Be-Done Benefits
Description: Name how each feature solves a concrete reader problem. Negative example: "Includes weekly coaching calls." Positive example: "Weekly coaching calls help you debug one stuck draft before publication."
Rule: Resolve Objections Before the CTA
Description: Handle major concerns before asking for commitment. Negative example: Asking for sign-up before addressing credibility, risk, or fit concerns. Positive example: Social proof, FAQ, and guarantee appear before the final action prompt.
Rule: Let Length Follow Line Utility
Description: Do not optimize for short or long by default; keep lines that advance decision quality. Negative example: Cutting critical proof to keep the page "short." Positive example: Keeping copy as long as needed to clarify value, fit, proof, and risk.
Framework 9: Persuasion Spine Selector
Choose one structure before drafting persuasive or conversion-oriented copy:
- AIDA: Attention -> Interest -> Desire -> Action
- PAS: Problem -> Agitation -> Solution
- BAB: Before -> After -> Bridge
- 4Ps: Problem -> Promise -> Proof -> Proposal
- QUEST: Qualify -> Understand -> Educate -> Stimulate -> Transition
- FAB: Feature -> Advantage -> Benefit
Rule: Match Formula to Reader Awareness
Description: Use structure based on how aware the reader already is of the problem and solution. Negative example: Leading with feature lists for readers who do not yet feel the problem. Positive example: Using PAS for cold readers, then FAB when readers are comparing solution details.
Rule: Select Spine by Search Intent and Job-to-Be-Done
Description: Choose the persuasion sequence that best matches what the reader is trying to solve right now. Negative example: Applying the same persuasion formula to every piece regardless of audience need. Positive example: Using PAS for pain-first diagnostic queries, AIDA for awareness-to-action explainers, and BAB for transformation narratives where readers need a clear before/after contrast.
Rule: Treat Spine as Planning Logic, Not Surface Template
Description: Keep one internal persuasion sequence while adapting the visible structure to channel conventions. Negative example: Forcing a rigid AIDA label stack into channels where that packaging feels unnatural. Positive example: Maintaining one persuasion arc while expressing it through channel-native pacing, transitions, and formatting.
Rule: Do Not Skip Desire or Proof
Description: Ensure the copy includes emotional motivation and credibility support before the CTA. Negative example: Attention headline and immediate button with no desire build or proof. Positive example: Clear desire framing plus evidence layer before asking for action.
Rule: Keep One Primary Spine Per Piece
Description: Avoid mixing multiple formula structures in one short draft. Negative example: Opening with PAS, switching to QUEST mid-body, and closing with unrelated CTA logic. Positive example: One consistent persuasion spine from opening through close.
Rule: Delay the Main CTA Until Readiness Signals Are Present
Description: Place the primary CTA after value, proof, and objection handling are clear. Negative example: Asking for commitment before clarifying fit, risk, or outcomes. Positive example: Primary CTA appears after promise, mechanism, and credibility are established.
Drafting Sequence
Use this when shaping a piece:
- Pick one topic and define its audience bucket.
- Choose one container and one clear headline promise.
- Compress to one core idea.
- Outline sections that all support that core idea.