content-generation:blog-posts [DokuWiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Blog Post Planning Template for Consumer EEG Sleep Technology ======

This template provides a structured framework for planning blog content.

===== Part 1: Strategic Planning Framework =====

Complete this section before drafting any content. Each field must align with business objectives.

^ Element ^ Requirements & Guiding Questions ^ Example ^
| **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 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 behavior you want readers to take. Avoid multiple CTAs. | Join early access waitlist for beta testing program |
| **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. |

===== Part 2: Content Structure Guidelines =====

==== 2.1 Optimal Length ====
  * **Target: 800-1,200 words** for consumer-focused content
  * **Technical deep-dives: 1,500-2,000 words** for researcher/prosumer audiences
  * Prioritize depth over length — every paragraph must serve the core message

==== 2.2 Standard Post Architecture ====

<code>
1. Headline (8-12 words)
   └─ Clear value proposition aligned with core message

2. Introduction (50-100 words)
   ├─ Hook: relatable problem or striking insight
   └─ Promise: what reader will gain

[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

3. Body Sections (3-5 sections)
   ├─ H2: Main concept headers
   ├─ H3: Supporting points
   ├─ Short paragraphs (2-3 sentences max)
   └─ Visual breaks: bullets, images, charts

4. Conclusion & CTA (75-100 words)
   ├─ Reinforce core message
   └─ Single, clear call-to-action

5. Q&A (Mandatory; 3–6 concise Qs)
   ├─ Address common reader questions raised by the post
   └─ Keep answers practical and plain-language
</code>

==== 2.3 Essential Sections by Audience Type ====

^ 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 |

==== 2.4 Q&A Section Guidance (Mandatory) ====
Include 3–6 of the most relevant questions. Suggested prompts:
  * Is this product already available or currently being built?
  * 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?

Keep answers short (1–3 sentences), concrete, and aligned with the selected Product Status & Narrative Mode.

===== Part 3: Editorial Standards & Style Guide =====

==== 3.1 Language Principles ====
  * **Person-first language mandatory**
    * ❌ "insomniacs" → ✓ "individuals experiencing insomnia"
    * ❌ "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 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]."

**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."

==== 3.3 Tone Guidelines ====
  * **Authority without arrogance**: Support claims with concrete evidence/examples, not superlatives
  * **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

==== 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).

===== Part 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

==== 4.2 Accessibility & Formatting ====
  - [ ] All images include descriptive alt text
  - [ ] Headings follow semantic hierarchy (H2 → H3)
  - [ ] Paragraphs ≤ 3 sentences for mobile readability
  - [ ] Links use descriptive text (not "click here")
  - [ ] Optional TL;DR or Key Takeaways included when skimmability is important
  - [ ] Content passes readability analysis (target: 8th-10th grade level for consumers)

==== 4.3 Asset Quality Control ====
  - [ ] Data visualizations include clear labels and units
  - [ ] 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

==== 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)

===== Part 5: Common Pitfalls & Solutions =====

^ 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 |

===== Part 6: Example Blog Topics =====

==== 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

==== 6.2 Demonstrating Product Value ====
  * Case study: How beta users discovered their optimal sleep schedule
  * 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 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.