Long-Form Storytelling Framework Post

Write a long-form framework post with the following: Framework concept: {&{FRAMEWORK_CONCEPT}} Framework name (or ask AI to generate): {&{FRAMEWORK_NAME}} Illustrative story/case study: {&{ILLUSTRATIVE_STORY}} Evidence base: {&{EVIDENCE}} (data, case studies, research) Target audience: {&{TARGET_AUDIENCE}} Application context: {&{APPLICATION_CONTEXT}} (when/how should readers use this framework?) Author's authority basis: {&{AUTHOR_AUTHORITY}} Tone: {&{TONE}} Word count: {&{WORD_COUNT}} (default: 2,200) **Build the post in this structure:** 1. **Title Options (3 variants)**: Each must include the framework name and promise a specific outcome. 2. **Opening Story** (200–250 words): Tell the story that illustrates the framework in action — before naming or explaining the framework. The reader should feel the problem and the solution before they understand its structure. 3. **The Framework Introduction** (150–180 words): Name the framework. Explain what it is in one crisp paragraph. Use the story from Step 2 as the first proof of concept. 4. **Framework Component Deep-Dives** (200–250 words per component): For each component of the framework: - Name and one-sentence definition - Why this component is essential - How it works in practice with a concrete example - The most common mistake people make with this component 5. **Validation Section** (200–250 words): Present 2–3 pieces of evidence that support the framework's effectiveness. Data, case studies, or logical proof. 6. **Step-by-Step Application Guide**: A numbered, action-oriented guide for applying the framework in the specific context. Specific enough to use without the author present. 7. **Framework Visualization Description**: Describe exactly how the framework should be visualized (diagram, matrix, flowchart) for a designer to execute. 8. **Author Positioning Statement** (80–100 words): Establish the author as the reference point for this framework. Where can readers go deeper? 9. **SEO Metadata**: Title tag, meta description, 5 keywords. **Anti-patterns:** - Do NOT name the framework something generic (the 'Success Framework', the 'Growth Model') - Do NOT explain the framework abstractly before showing it in action - Do NOT make the application guide too high-level to be actionable