Blog Post Planning Template for Consumer EEG Sleep Technology

This template provides a structured framework for planning blog content.

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

• 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

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

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.

• 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

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.”

• 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

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

1. [ ] Core message appears in headline, introduction, and conclusion
2. [ ] Single, clear CTA with minimal friction
3. [ ] All claims supported by concrete examples, visuals, or citations (as appropriate)
4. [ ] Competitor mentions follow positioning framework
5. [ ] Technical terms defined on first use
6. [ ] Narrative Mode matches Product Status throughout the post

1. [ ] All images include descriptive alt text
2. [ ] Headings follow semantic hierarchy (H2 → H3)
3. [ ] Paragraphs ≤ 3 sentences for mobile readability
4. [ ] Links use descriptive text (not “click here”)
5. [ ] Optional TL;DR or Key Takeaways included when skimmability is important
6. [ ] Content passes readability analysis (target: 8th-10th grade level for consumers)

1. [ ] Data visualizations include clear labels and units
2. [ ] Product images show real prototypes (not renders)
3. [ ] Charts highlight key insights with annotations
4. [ ] Human subjects in images have provided consent
5. [ ] File sizes optimized for web performance

1. [ ] Includes 3–6 questions with concise answers
2. [ ] Explicitly addresses availability/build status
3. [ ] Explains why the experiment/approach was tried
4. [ ] Provides a clear way to engage (e.g., waitlist, survey, reply)

• 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

• 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.