Differences

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

--- content-generation:blog-posts [2025/09/17 18:45] – fabricio
+++ content-generation:blog-posts [2025/09/18 11:54] (current) – fabricio
@@ Line 1: / Line 1: @@
-I obtained the following response from a different AI. I need you to refine the response.
+====== Blog Post Planning Template for Consumer EEG Sleep Technology ======
-The original query was:
-```
+This template provides a structured framework for planning blog content.
-m planning to start a blog for our company website.
-We develop EEG devices, and are planing to get into the consumer market.
+===== 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. |
-The goal of this blog is:
+===== Part 2: Content Structure Guidelines =====
-- visibility
+==== 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
-- providing authenticity (we exist, you can see what we do)
+==== 2.2 Standard Post Architecture ====
-- showcasing our devices
+<code>
+. Headline (8-12 words)
+   └─ Clear value proposition aligned with core message
-- highlighting limitation of alternative sleep tracking devices (e.g. a watch), and thus the need for our device
+. 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
-When creating a new blog article, it must have the following topics worked out:
+. Body Sections (3-5 sections)
+   ├─ H2: Main concept headers
+   ├─ H3: Supporting points
+   ├─ Short paragraphs (2-3 sentences max)
+   └─ Visual breaks: bullets, images, charts
-- Target Group (e.g. consumers / kickstarter campaign, pharma, researchers)
+. Conclusion & CTA (75-100 words)
+   ├─ Reinforce core message
+   └─ Single, clear call-to-action
-- Core Message
+. Q&A (Mandatory; 3–6 concise Qs)
+   ├─ Address common reader questions raised by the post
+   └─ Keep answers practical and plain-language
+</code>
-- Intended Action of the reader (e.g. participate in our kickstarter, acknowledge us as proficient in our field, request early access, ...)
+==== 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 |
-Notably, we dont aim to "simply educate", as this would have no direct action, and
+==== 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?
-we expect people to rather use wikipedia etc for such broad information.
+Keep answers short (1–3 sentences), concrete, and aligned with the selected Product Status & Narrative Mode.
+===== Part 3: Editorial Standards & Style Guide =====
-I require a careful elaboration of the general structure we should consider for blog entries.
+==== 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
-That is:
+==== 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]."
-- length
+**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."
-- style we should watch out for (e.g. proper gendering, tone of voice, ...)
+==== 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
-- [fill in other things important for corporate blogs aimed at consumers/researchers/investors]
+==== 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)
-Based on existing best practices for such enterprise blogs (i.e. highest impact w.r.t. gaining customers), develop a range of questions and a structure that should be clear before writing out the actual content.
+==== 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)
-Basically, help me develop a structured approach for planning blog post, and highlight things that are easily missed by amateur bloggers.
+===== 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 =====
-```====== Structured Blog Post Planning Template for Consumer-Focused EEG Sleep Technology Startup ======
+==== 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
-//This template provides a formal, repeatable framework for planning and producing blog content aligned with strategic business objectives. It is designed for early-stage startups in the consumer health technology space — specifically EEG-based sleep monitoring — where clarity, credibility, and conversion are paramount.//
+==== 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
-===== PART 1: PRE-WRITING STRATEGIC BLUEPRINT =====
-Each blog post must be grounded in strategy and grounded in available assets. Complete this section in full prior to drafting. If any field cannot be meaningfully populated — especially under “Asset Requirements” — pause and gather resources first.
+----
-^ Element               ^ Guiding Questions & Requirements                                                                 ^ Example Entry                              ^
+**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.
-| **Target Group**      | Define the precise audience segment (e.g., Kickstarter backers, biohackers, parents of adolescents with irregular sleep, early adopters of health tech). What specific need, frustration, or goal does this post address for them? | “Consumers aged 28–45 using wearables for sleep tracking but dissatisfied with inconsistent or superficial insights.” |
-| **Core Message**      | Articulate in one sentence the primary assertion or insight the reader must retain. This is the central thesis of the post. | “While wrist-based devices estimate sleep through movement and heart rate, only EEG technology captures the brain activity necessary to accurately identify sleep stages and underlying causes of poor rest.” |
-| **Intended Action**   | Specify the single desired reader behavior post-engagement (e.g., join waitlist, pre-order, request demo, share on social media, subscribe to updates). Avoid multiple CTAs. | “Request early access to our beta program for priority onboarding and exclusive pricing.” |
-| **Working Title(s)**  | Propose 3–5 headline options. Titles must be benefit-oriented, accurate, and aligned with Core Message. Avoid sensationalism. | “Why Your Smartwatch Can’t Explain Your Sleep — And What Can” |
-| **Competitive Positioning** | How will the post contextualize alternative solutions (e.g., Oura, Apple Watch, Fitbit)? Frame comparisons constructively: acknowledge utility while clarifying limitations. Never disparage. Use “different tools for different purposes” framing. | “Wrist-worn trackers offer valuable insights into daily activity and resting heart rate. For clinical-grade sleep staging and brain-based analysis, EEG remains the gold standard — and now, accessible at home.” |
-| **Asset Requirements** | //NEW: What specific measurements, images, datasets, or visualizations are required to credibly support this post?// List exact needs — e.g., “plot comparing EEG vs. PPG sleep staging from our pilot dataset,” “photo of prototype v3 on real user,” “annotated spectrogram of NREM vs REM.” If unavailable, note: “TO BE GENERATED.” | “1. Side-by-side hypnogram: Our EEG prototype (raw data from Subject #7) vs. Apple Watch estimate. 2. Close-up photo: prototype headband on volunteer (in low-light bedroom setting). 3. Annotated graph: Delta vs. Theta power during deep sleep transition.” |
-===== PART 2: STRUCTURAL ANATOMY OF THE BLOG POST =====
-Adherence to this structure ensures logical flow, readability, and alignment with conversion goals.
-==== 1. Headline ====
-→ Must clearly reflect the Core Message.
-→ Should pass the “value test”: reader immediately understands what they will gain.
-→ Avoid clickbait; maintain credibility appropriate to health technology.
-→ Example: “The Limitations of Movement-Based Sleep Tracking — And Why EEG Changes Everything”
-==== 2. Introduction (≤ 75 words) ====
-→ Open with a relatable observation, data point, or question.
-→ Confirm relevance to the Target Group.
-→ State the article’s purpose and value proposition succinctly.
-→ Example: “If you rely on your wearable to understand your sleep but still wake up fatigued, the issue may not be your habits — it’s your hardware. Movement and heart rate alone cannot reveal what your brain is doing at night. This post explains why — and what to do about it.”
-==== 3. Body ====
-→ Organize content under descriptive H2 and H3 subheadings.
-→ Paragraphs: 1–3 sentences maximum. Prioritize scannability.
-→ Use bullet points for comparisons, benefits, or key takeaways. Bold critical terms or conclusions.
-→ Integrate visuals at strategic intervals to reinforce claims or simplify complexity.
-→ Example H2: “The Science of Sleep Staging: Why Brainwaves Matter More Than Movement”
-→ Example H3: “How Consumer Wearables Estimate Sleep — And Where They Fall Short”
-==== 4. Conclusion and Call-to-Action ====
-→ Summarize the Core Message in one to two sentences.
-→ Transition smoothly to a single, unambiguous Call-to-Action.
-→ Provide clear instruction and minimal friction (e.g., prominent button, short form).
-→ Example: “Accurate sleep insight begins with brain data — not guesswork. Join our early access list to be among the first to experience clinically validated sleep staging at home. → [Button: Request Early Access]”
-===== PART 3: TONE, LANGUAGE, AND STYLE GUIDELINES =====
-Maintain consistent, professional tone suitable for a science-driven consumer health brand.
-==== Tone of Voice ====
-  * **Authoritative yet approachable.** Convey expertise without condescension.
-  * **Empathetic and respectful.** Acknowledge reader challenges without dramatization.
-  * **Calmly confident.** Avoid hyperbolic claims (“revolutionary,” “miracle”). Let data and logic persuade.
-  * **Humanized professionalism.** Use “we” and “our” to reflect team presence, but avoid slang or forced casualness.
-==== Language Standards ====
-  * **Person-first language.** Never use terms like “insomniacs,” “sufferers,” or “patients” unless clinically appropriate and explicitly quoted. Prefer: “individuals managing sleep difficulties,” “users seeking deeper sleep insights.”
-  * **Inclusive gendering.** Default to “they/them” or plural constructions (“users,” “readers”). Avoid “he/she.”
-  * **Technical terms.** Define on first use in plain language. Example: “EEG (electroencephalography — the measurement of electrical activity in the brain).”
-  * **Competitor references.** Always respectful. Position alternatives as useful within their scope, not deficient.
-    → Inappropriate: “Smartwatches provide inaccurate sleep data.”
-    → Appropriate: “Smartwatches are effective tools for monitoring daily activity and heart rate variability. For granular analysis of sleep architecture, EEG-based systems offer a fundamentally different — and more precise — dataset.”
-==== Content Principles ====
-  * **No general education.** Do not replicate publicly available information (e.g., Wikipedia summaries of sleep cycles). Content must serve the Core Message or drive the Intended Action.
-  * **Feature → Benefit translation.** Never list specifications without explaining user value.
-    → Weak: “Our device uses six dry-contact electrodes.”
-    → Strong: “Six dry-contact electrodes comfortably conform to your forehead, capturing high-fidelity brainwave data without gels or setup — delivering lab-grade sleep staging in your own bed.”
-  * **Visuals as functional assets.** Every image, chart, or graphic must clarify, compare, or build trust. Authenticity (real product, real team) > polish.
-  * **Mobile-optimized formatting.** Assume >60% of readers are on mobile. Short paragraphs. Clear hierarchy. Tap-friendly CTAs.
-===== PART 4: ASSET DEVELOPMENT & EXECUTION CHECKLIST =====
-//NEW SECTION — Critical for early-stage teams working with prototypes and scientific data.//
-Before publishing, verify that all required assets from Part 1 have been produced or sourced. This is not optional — credibility in consumer health depends on demonstrable evidence.
-  * ✅ **Data & Plots**
-    - Confirm dataset source (e.g., “Subject #12, Night 3, 2024-06-10”)
-    - Ensure plots are labeled clearly (axes, units, conditions)
-    - Annotate key insights directly on visuals (e.g., “REM onset detected at 03:14 via theta burst”)
-    - Include brief methodological note if needed: “Data collected using prototype v2.3 with 4-channel dry EEG, sampled at 250Hz.”
-  * ✅ **Photography & Visuals**
-    - Use real prototypes — not renders or mockups.
-    - Show device in context (e.g., on pillow, worn during sleep, with real user — with consent).
-    - Include scale reference if helpful (e.g., device next to common object).
-    - Ensure lighting and composition convey comfort, simplicity, and trust.
-  * ✅ **Permissions & Ethics**
-    - All human-subject data/images require documented consent.
-    - Anonymize data if not from team members (remove timestamps, IDs, etc.).
-    - If using third-party data or code, cite source and verify licensing.
-  * ✅ **Reproducibility Note (Optional but Recommended)**
-    - For technical audiences: “Raw data and plotting scripts available on request for research collaborators.”
-    - Shows scientific integrity without over-educating consumers.
-===== PART 5: COMMON PITFALLS TO AVOID =====
-  * ❌ Drafting content without completing Part 1 — especially “Asset Requirements.”
-  * ❌ Publishing without verifying asset availability or quality.
-  * ❌ Using placeholder visuals or “we’ll add this later.”
-  * ❌ Including multiple Calls-to-Action. One goal per post.
-  * ❌ Long, unbroken text blocks. Online readers scan — design for it.
-  * ❌ Generic or stock photography. Authentic visuals build credibility.
-  * ❌ Over-explaining basic concepts. Assume baseline knowledge; focus on differentiation.
-  * ❌ Ignoring accessibility. All images require descriptive alt text. Headings must be semantic.
-  * ❌ Publishing without mobile preview. Test layout on small screens.
-===== IMPLEMENTATION INSTRUCTIONS =====
-→ Duplicate this template for each planned blog post within your DokuWiki environment.
-→ Mandate completion of Part 1 — including **Asset Requirements** — prior to content drafting.
-→ Use Part 2 as the structural outline during writing.
-→ Apply Part 3 as an editorial checklist during revision.
-→ Execute Part 4 rigorously before publishing — no exceptions.
-→ Consult Part 5 prior to final approval.
-//This is not a content repository. It is a conversion-oriented planning instrument grounded in real prototypes and data. Every published post must advance visibility, authenticity, product showcase, or competitive differentiation — as defined in your original objectives.//
-```
-I want you to refine this response, to provide me a properly usable template in DOKUWIKI MARKDOWN STYLE. Make it generally enough for sleep EEG devices (e.g. a smart alarm, measuring sleep stages, ..). Do not be too specific, but be aware we are within a consumer health sector, and obvious competitors are either other sleep bands or sensor devices like oura, apple watch, etc.
-We are a small startup first starting with the blog. This serves to introduce us, our topic, our expertice, and our product.  I don't care about "big company" things like "updates" about fundings etc. This is not a news site, this is a blog with actual content.
-What I really liked about the initial proposal:
-- example for comparing with a competitor. That is good and should be reintroduced (ie not putting it down, but stating it has a different purpose).
-- good guidelines for proper language in context, specifically for people suffering from diseases. I.e. not saying "insomniacs" etc.. also gendering etc.
-As an additional note, our mission is NOT to educate people, thats what wikipedia etc is for. Our blogs need a specific purpose, as stated in my original question.
-Stay formal in tone, this is for an internal wiki guide.