Differences

This shows you the differences between two versions of the page.

--- content-generation:blog-posts [2025/09/17 18:44] – created fabricio
+++ content-generation:blog-posts [2025/09/18 11:54] (current) – fabricio
@@ Line 1: / Line 1: @@
-====== Strategic Blog Development Framework ======
+====== Blog Post Planning Template for Consumer EEG Sleep Technology ======
-This template establishes a systematic approach for planning and executing blog content that advances business objectives. It is designed for early-stage sleep technology companies entering the consumer market, where establishing credibility and driving specific reader actions are critical.
+This template provides a structured framework for planning blog content.
-===== Section 1: Strategic Foundation =====
+===== Part 1: Strategic Planning Framework =====
-Complete this section in full before drafting any content. Each field must have a clear, actionable entry.
+Complete this section before drafting any content. Each field must align with business objectives.
-==== 1.1 Core Strategic Elements ====
 ^ Element ^ Requirements & Guiding Questions ^ Example ^
-| Target Audience | Define the specific reader segment. Consider: demographics, current solutions they use, pain points, level of technical sophistication. Be precise. | "Tech-savvy consumers aged 25-45 currently using wearables for health tracking but seeking deeper sleep insights" |
+| **Target Audience** | Define the specific segment. Consider: demographics, current solutions they use, pain points, sophistication level. | Quantified-self enthusiasts aged 25-45 who track sleep with wearables but seek deeper insights into sleep quality |
-| Core Message | One sentence capturing the essential insight or claim. This is what the reader must remember. | "While wrist-worn devices estimate sleep through indirect measures, EEG technology directly observes brain activity—the actual source of sleep stages" |
+| **Core Message** | One sentence capturing the primary insight readers must retain. This drives all content decisions. | EEG-based monitoring reveals brain activity patterns that movement-based trackers cannot detect, providing actionable insights for sleep optimization |
-| Intended Action | Single, specific action you want the reader to take. Avoid multiple CTAs. | "Join our early access program for priority product availability" |
+| **Intended Action** | Single, specific behavior you want readers to take. Avoid multiple CTAs. | Join early access waitlist for beta testing program |
-| Competitive Context | How will you position alternatives? Frame as "different tools for different needs" rather than inferior products. | "Smartwatches excel at 24/7 activity monitoring and convenience. For those seeking laboratory-grade sleep analysis at home, brain-based measurement offers fundamentally different—and more detailed—insights" |
+| **Competitive Context** | How to position alternative solutions constructively. Acknowledge their strengths while clarifying different use cases. | Wrist-worn devices excel at 24/7 activity tracking and convenience; EEG devices provide clinical-grade sleep stage analysis for those prioritizing sleep optimization |
+| **Product Status & Narrative Mode** | Select current status and how you’ll talk about it. Options: Concept, Basic Prototype, In Development, Shipping. Narrative modes: Present-state (what exists today) or Future-cast (market interest test, projecting near-term availability). Ensure consistent framing across the post and Q&A. | Status: Basic Prototype. Narrative: Future-cast — “We’re building toward a version you could use at home next year.” |
+| **Required Assets** | List specific data, images, or demonstrations needed. Mark items as "TO CREATE" if not available. | 1. Comparison chart: sleep stage accuracy (EEG vs accelerometer) 2. Product photo on nightstand 3. Sample hypnogram from our device |
+| **Distribution Plan** | Outline primary channels and messaging. How will this content reach the target audience? Tailor the hook for each platform. | * **Kickstarter Update:** **Hook:** "Deep Dive: We're sharing the science behind our smart alarm. See the EEG data that makes it possible." **Asset:** Use the sample hypnogram chart. <br> * **LinkedIn (Founder's Profile):** **Hook:** "Many sleep trackers guess your sleep stages. Here's why measuring brain activity directly is a game-changer. A look at the tech we're building." **Asset:** Use the comparison chart. <br> * **Email Newsletter:** **Hook:** "For our waitlist members: a first look at how we validate our sleep staging accuracy." **Asset:** Embed the product photo. |
-==== 1.2 Content Planning Elements ====
+===== Part 2: Content Structure Guidelines =====
-^ Element ^ Requirements ^ Checklist ^
+==== 2.1 Optimal Length ====
-| Working Title | Create 3-5 options. Must be clear, benefit-oriented, and honest. | ☐ Reflects core message \ ☐ Indicates value to reader \ ☐ Avoids clickbait |
+  * **Target: 800-1,200 words** for consumer-focused content
-| Required Assets | List specific data, images, or demonstrations needed. If unavailable, mark as "TO GENERATE" | ☐ Data visualizations identified \ ☐ Product images specified \ ☐ Comparison charts outlined |
+  * **Technical deep-dives: 1,500-2,000 words** for researcher/prosumer audiences
-| Credibility Elements | What evidence supports your claims? Studies, pilot data, technical specifications? | ☐ Sources identified \ ☐ Data permissions verified \ ☐ Technical accuracy confirmed |
+  * Prioritize depth over length — every paragraph must serve the core message
-===== Section 2: Content Structure Guidelines =====
+==== 2.2 Standard Post Architecture ====
-==== 2.1 Recommended Length and Format ====
+<code>
+. Headline (8-12 words)
+   └─ Clear value proposition aligned with core message
-    Total length: 800-1,200 words for standard posts; 1,500-2,000 for technical deep-dives
+. Introduction (50-100 words)
-    Paragraph length: Maximum 3 sentences
+   ├─ Hook: relatable problem or striking insight
-    Section length: 150-300 words per H2 section
+   └─ Promise: what reader will gain
-    Visual frequency: One supporting element every 250-350 words
-==== 2.2 Standard Post Architecture ====
+[Optional] TL;DR or Key Takeaways (use only when skimmability is critical)
+   ├─ TL;DR: 2–3 bullets summarizing the post, OR
+   └─ Key Takeaways: 3–5 bullets placed near the end before the CTA
-=== Introduction (50-100 words) ===
+. Body Sections (3-5 sections)
+   ├─ H2: Main concept headers
+   ├─ H3: Supporting points
+   ├─ Short paragraphs (2-3 sentences max)
+   └─ Visual breaks: bullets, images, charts
-    Open with relatable scenario or compelling data point
+. Conclusion & CTA (75-100 words)
-    Confirm relevance to target audience
+   ├─ Reinforce core message
-    State what the reader will gain
+   └─ Single, clear call-to-action
-    Transition to main content
-=== Body Structure ===
+. Q&A (Mandatory; 3–6 concise Qs)
+   ├─ Address common reader questions raised by the post
+   └─ Keep answers practical and plain-language
+</code>
-    Use descriptive H2 headings that allow scanning
+==== 2.3 Essential Sections by Audience Type ====
-    Break complex topics into H3 subsections
-    Employ bullet points for comparisons or key features
-    Bold critical phrases but sparingly
-    Include data/visuals at natural break points
-=== Conclusion & CTA (75-125 words) ===
+^ Audience ^ Required Sections ^ Tone Adjustments ^
+| **Consumers** | Problem validation, solution comparison, user benefits, social proof | Conversational but credible; minimize jargon |
+| **Prosumers / Biohackers** | Technical differentiators, data deep-dives, integration potential, clear product specs | Enthusiastic and data-rich; use precise terminology but explain its practical value |
+| **Researchers** | Methodology transparency, data quality metrics, validation studies, collaboration opportunities | Technical precision; include citations |
-    Restate core message concisely
+==== 2.4 Q&A Section Guidance (Mandatory) ====
-    Bridge logically to intended action
+Include 3–6 of the most relevant questions. Suggested prompts:
-    Present single, clear call-to-action
+  * Is this product already available or currently being built?
-    Make next step frictionless
+  * Why did you try this experiment or approach?
+  * How does this differ from wrist wearables or phone-based alarms?
+  * What can readers expect in the first week of use?
+  * What are the known trade-offs (e.g., comfort, setup)?
+  * How can interested readers get involved or share feedback?
-===== Section 3: Editorial Standards =====
+Keep answers short (1–3 sentences), concrete, and aligned with the selected Product Status & Narrative Mode.
-==== 3.1 Tone and Voice Guidelines ====
+===== Part 3: Editorial Standards & Style Guide =====
-^ Principle ^ Implementation ^ Example ^
+==== 3.1 Language Principles ====
-| Authoritative yet Accessible | Demonstrate expertise without jargon. Define technical terms on first use. | "EEG (electroencephalography—measurement of brain electrical activity) provides..." |
+  * **Person-first language mandatory**
-| Respectful of Competitors | Position alternatives as valuable within their scope | ✗ "Fitness trackers give inaccurate sleep data" \ ✓ "Fitness trackers effectively monitor daily activity patterns. For clinical-grade sleep architecture analysis, brain-based measurement provides a different dataset" |
+    * ❌ "insomniacs" → ✓ "individuals experiencing insomnia"
-| Evidence-Based Claims | Support assertions with data or established science | "Studies show that 30% of perceived 'light sleep' is actually wake time when measured via EEG" |
+    * ❌ "sleep disorder sufferers" → ✓ "people managing sleep conditions"
+  * **Inclusive writing**
+    * Default to "they/them" for singular examples
+    * Use "users," "individuals," or role-specific terms
+    * Avoid assumptions about family structures or lifestyles
+  * **Technical terminology**
+    * Define on first use: "REM (Rapid Eye Movement) sleep"
+    * Link to glossary for recurring terms
+    * Provide analogies for complex concepts
-==== 3.2 Language Standards ====
+==== 3.2 Competitor Positioning Framework ====
+**Template for respectful comparison:**
+> "[Competitor/category] excels at [genuine strength], making it ideal for [use case]. For users specifically seeking [our differentiator], EEG-based monitoring provides [unique value]."
-=== Inclusive Language Requirements ===
+**Example:**
+> "The Oura Ring excels at continuous health monitoring and long-term trend analysis, making it ideal for holistic wellness tracking. For users specifically seeking to understand why they wake unrested despite adequate sleep duration, EEG-based monitoring provides the brain activity data necessary to identify sleep stage disruptions."
-    Person-first terminology: Use "people experiencing insomnia" not "insomniacs"
+==== 3.3 Tone Guidelines ====
-    Gender-neutral default: Use "they/them" or plural constructions
+  * **Authority without arrogance**: Support claims with concrete evidence/examples, not superlatives
-    Accessible descriptions: Avoid ableist language; focus on function not limitation
+  * **Empathetic problem acknowledgment**: Validate reader frustrations without dramatization
+  * **Solution-focused optimism**: Present technology as tool, not miracle cure
+  * **Accessible expertise**: Explain complex concepts through relatable analogies
-=== Technical Communication Standards ===
+==== 3.4 Narrative Mode: Future-Cast (Market Interest Test) ====
+Use when exploring a device or version not yet available but planned.
+  * Be consistent: match language across headline, body, and Q&A (e.g., “we’re building toward…” “targeting next year”).
+  * Focus on experience: describe what mornings could feel like and what problems it aims to solve.
+  * Invite signal: clearly state how readers can express interest (e.g., join waitlist, short survey).
-    Define acronyms: Always expand on first use
+===== Part 4: Pre-Publication Checklist =====
-    Translate features to benefits: "Six dry electrodes" → "Six dry electrodes mean no gels or complex setup—just comfortable, accurate measurement"
-    Avoid hyperbole: No "revolutionary," "breakthrough," or "game-changing" without substantiation
-===== Section 4: Pre-Publication Checklist =====
 ==== 4.1 Content Verification ====
+  - [ ] Core message appears in headline, introduction, and conclusion
+  - [ ] Single, clear CTA with minimal friction
+  - [ ] All claims supported by concrete examples, visuals, or citations (as appropriate)
+  - [ ] Competitor mentions follow positioning framework
+  - [ ] Technical terms defined on first use
+  - [ ] Narrative Mode matches Product Status throughout the post
-    ☐ Target audience clearly defined
+==== 4.2 Accessibility & Formatting ====
-    ☐ Core message present in introduction and conclusion
+  - [ ] All images include descriptive alt text
-    ☐ Single, clear call-to-action
+  - [ ] Headings follow semantic hierarchy (H2 → H3)
-    ☐ Competitive positioning respectful and accurate
+  - [ ] Paragraphs ≤ 3 sentences for mobile readability
-    ☐ All claims supported by evidence
+  - [ ] Links use descriptive text (not "click here")
-    ☐ Technical terms defined
+  - [ ] Optional TL;DR or Key Takeaways included when skimmability is important
+  - [ ] Content passes readability analysis (target: 8th-10th grade level for consumers)
-==== 4.2 Asset Verification ====
-    ☐ All referenced data/images created or sourced
-    ☐ Visuals labeled with units, axes, and context
-    ☐ Product images show real prototypes (not renders)
-    ☐ Alt text provided for accessibility
-    ☐ Image permissions/consent documented
-==== 4.3 Quality Assurance ====
-    ☐ Mobile layout tested
-    ☐ Links functional
-    ☐ No spelling/grammar errors
-    ☐ Headings create logical hierarchy
-    ☐ Reading time under 7 minutes
-===== Section 5: Common Pitfalls to Avoid =====
-^ Pitfall ^ Why It Matters ^ Solution ^
-| Generic educational content | Readers can find this on Wikipedia; provides no business value | Focus on unique insights, comparisons, or applications specific to your technology |
-| Multiple CTAs | Confuses reader; reduces conversion | One primary action per post |
-| Attacking competitors | Damages credibility; appears defensive | Frame as "different approaches for different needs" |
-| Publishing without assets | Undermines authority; looks amateur | Complete asset requirements before writing |
-| Overly technical language | Alienates consumer audience | Write for intelligent non-specialists; define terms |
-| Stock photography | Reduces authenticity | Use real product images, team photos, or original graphics |
-===== Section 6: Topic Categories for Sleep EEG Devices =====
-Consider these proven content angles when planning posts:
-==== Technology Comparisons ====
-    EEG vs. actigraphy vs. heart rate variability
+==== 4.3 Asset Quality Control ====
-    Home sleep monitoring vs. sleep lab studies
+  - [ ] Data visualizations include clear labels and units
-    Different electrode configurations and their trade-offs
+  - [ ] Product images show real prototypes (not renders)
+  - [ ] Charts highlight key insights with annotations
+  - [ ] Human subjects in images have provided consent
+  - [ ] File sizes optimized for web performance
-==== Use Case Explorations ====
+==== 4.4 Q&A Quality (Mandatory) ====
+  - [ ] Includes 3–6 questions with concise answers
+  - [ ] Explicitly addresses availability/build status
+  - [ ] Explains why the experiment/approach was tried
+  - [ ] Provides a clear way to engage (e.g., waitlist, survey, reply)
-    Optimizing sleep for shift workers
+===== Part 5: Common Pitfalls & Solutions =====
-    Tracking sleep architecture changes during stress
-    Monitoring sleep quality improvements from interventions
-==== Scientific Foundations ====
+^ Pitfall ^ Impact ^ Solution ^
+| Multiple CTAs | Decision paralysis, reduced conversions | Choose primary action; save others for follow-up |
+| Generic stock photos | Reduced authenticity and trust | Use actual product shots or team photos |
+| Over-explaining basics | Reader abandonment | Link to external resources; focus on unique insights |
+| Jargon without context | Alienates non-technical readers | Always provide plain-language explanation |
+| Defensive competitor comparisons | Appears insecure | Emphasize different tools for different needs |
+| Inconsistent product status messaging | Confusion and distrust | Set Product Status & Narrative Mode in Part 1; ensure Q&A aligns |
+| Burying availability info | Frustration, missed intent signals | Use the mandatory Q&A to answer availability clearly |
-    How sleep stages are actually determined
+===== Part 6: Example Blog Topics =====
-    Why brain activity matters for sleep assessment
-    The limitations of movement-based tracking
-==== Product Development Insights ====
+==== 6.1 Establishing Credibility ====
+  * Behind the technology: How EEG captures what other devices miss
+  * Team spotlight: Sleep researchers explain why they joined our mission
+  * How we check ourselves: What “good” looks like for a smart alarm (in plain English)
+  * Design choices that matter: Headband comfort, electrode placement, and quick setup
-    Designing comfortable dry electrodes
+==== 6.2 Demonstrating Product Value ====
-    Balancing accuracy with usability
+  * Case study: How beta users discovered their optimal sleep schedule
-    Real-world testing and validation processes
+  * Feature deep-dive: Understanding your personal sleep architecture
+  * Real user night: A before/after wake-up experience with EEG timing
+  * Concept spotlight (future-cast): What we’re exploring next — tell us if you’d use it
-===== Implementation Protocol =====
-    Planning Phase: Complete Section 1 entirely before proceeding
+----
-    Drafting Phase: Follow Section 2 structure; apply Section 3 standards
-    Review Phase: Execute Section 4 checklist systematically
-    Approval: Verify no items from Section 5 are present
-    Publication: Schedule for optimal audience engagement times
-Remember: Every post must drive a specific business outcome—awareness, credibility, or conversion. Content without purpose is wasted effort.
+**Implementation Note:** Save a completed Part 1 (including Product Status & Narrative Mode) for each planned post in your project management system before content creation begins. This ensures strategic alignment and prevents scope creep during writing.