Writing Best Practices:

🚨 CORE CORE RULES (MANDATORY):

RHYTHMIC VARIETY: Mix Short and Long Complete Sentences

The Problem: Most AI writing uses the same sentence length over and over, creating a monotonous drone.

The Solution: Vary your sentence length naturally to create rhythm, but keep every sentence grammatically complete.

Grammar Rule #1: Don’t Create Fragments

What Good Rhythm Actually Looks Like:

Example 1 (Intro snippet truncated - Project management tools): “I’ve been managing remote teams since 2017. Back then, we lived in Trello and Google Sheets, and honestly, it worked fine for small teams.

But once you hit 15+ people across different time zones, everything falls apart.

These days, everyone’s using AI-powered project tools that supposedly predict bottlenecks and automate status updates. Some of it’s genuinely useful. Most of it’s just extra noise that makes simple projects feel complicated.

As someone who’s tried 12+ tools over the past two years, I can tell you which ones actually deliver and which ones are just riding the AI hype.”

→ Personal credibility, then vs now contrast, honest take, bold statement. Natural rhythm with varied sentence lengths.

Example 2 (Product listicle snippet - SEO tools): “Semrush’s old pricing plans, Pro and Guru, now only cover the SEO Toolkit.

If you want to use it, you’ll need to upgrade to at least the Pro plan, which costs $139.95 a month. It’s pricey, but still less than what I used to pay for Ahrefs ($199/month).

One thing I like about Semrush is their quick customer support. If your card gets charged by mistake (happened to me once), they process refunds within a day. You just fill out a contact form, and they’ll email you to confirm the refund.

Before paying for any plan, I’d suggest trying the free trial first. That way, you can test it out and see if it’s worth it for you.”

→ Mix of short facts, medium observations, and longer personal anecdotes. Conversational, not corporate.

Example 3 (Tutorial section - Email marketing): “Go to Campaigns > Create Campaign and pick ‘Automated Email Sequence’ from the dropdown.

Most people choose a template here, but I’d recommend starting from scratch if you actually want control over your formatting. The templates look nice in the builder but often break on mobile.

Set your trigger event (usually ‘subscribed to list’ or ‘downloaded lead magnet’), then add your first email. Don’t overthink the subject line on your welcome email. Something simple like ‘Here’s what you downloaded’ converts better than clever wordplay.

One thing that trips people up: make sure you set the sending time to match your audience’s timezone, not yours. I learned this the hard way when my 9am emails were hitting inboxes at 3am for half my list.”

→ Clear instruction, honest opinion warning, more instruction, practical tip, personal mistake story. Helpful without being robotic.

Example 4 (Conclusion section - Customer support software): “If you’re a small team (under 10 people) and just need shared email management, start with Help Scout. It’s $20/user and you can be up and running in an afternoon.

For larger teams dealing with complex tickets across multiple channels, Zendesk is worth the headache of setup. You’ll pay more ($55/user minimum) and spend a week configuring everything, but the automation and reporting actually work.

Intercom tries to be everything at once and ends up being mediocre at support. Great for sales and onboarding, terrible if support is your main use case. Don’t let the slick demo fool you.”

→ Specific recommendation with clear criteria, honest trade-off explanation, direct warning. The short decisive statements earn their punch.

When Short Sentences Work:

• After a longer setup that creates tension
• To deliver a punch line or key insight
• To signal a transition or shift
• Sparingly, maybe 1-2 per paragraph maximum

When to Keep Sentences Together:

• Cause and effect: “X so Y” or “X because Y”
• Conditions: “If X, then Y”
• Purpose: “Action to achieve result”
• Qualifying details that complete a thought

The Test: Read it aloud. Does it sound like a human talking, or a robot hitting “enter” every 6 words?

🎯 NATURAL WRITING - Avoid Corporate/AI Voice

Core Principle: Write like you’re explaining to a friend, not presenting to a board.

The biggest tell of AI writing isn’t obvious errors - it’s subtle “cover letter energy.” Every sentence sounds professionally pleasant, like permanent LinkedIn mode.

MANDATORY RULES:

1. Use simple, conversational language - Don’t polish unnecessarily
2. Avoid marketing speak and corporate buzzwords - No “leverage”, “utilize”, “solutions”
3. Write like explaining to a friend - Not pitching to executives
4. Only use strong adjectives when genuinely warranted - Most things are just “good”, not “excellent”
5. Prefer understatement over hyperbole - Humans rarely oversell routine things
6. NEVER use em dashes (—) - They pack too many ideas into one sentence and sound unnatural

CRITICAL: Adjective Usage Patterns to Avoid

1. Subtle Corporate Enthusiasm (the “cover letter” voice):

❌ WRONG (unnecessarily polished):

• “This insightful article explores…”
• “A thoughtful approach to meal planning”
• “This comprehensive guide covers…”
• “An elegant solution for organizing files”

✅ CORRECT (conversational):

• “This article talks about…” or just “This article covers…”
• “A good way to meal plan” or “A simple approach to meal planning”
• “This guide covers…”
• “A simple way to organize files”

The test: If you wouldn’t say it to a friend over coffee, don’t write it.

2. Intensity Mismatches (LinkedIn energy for mundane tasks):

❌ WRONG (mismatch between adjective and subject):

• “It’s crucial to save your document regularly” (it’s just basic advice)
• “This powerful technique for folding laundry” (it’s folding laundry)
• “A compelling reason to check your tire pressure” (it’s maintenance)
• “An exceptional method for boiling water” (it’s… boiling water)

✅ CORRECT (proportional intensity):

• “It’s important to save regularly” or just “Save your document regularly”
• “A good way to fold laundry” or “This technique for folding laundry”
• “A good reason to check your tire pressure”
• “The best way to boil water” or just “How to boil water”

The test: Does the adjective match the actual importance? Tire pressure is “important”, not “compelling.”

3. The “Valuable/Effective/Helpful” Overuse:

AI defaults to these mild corporate adjectives for EVERYTHING:

❌ WRONG (corporate autopilot):

• “This offers valuable insights” (→ just say what the insights are)
• “An effective method for…” (→ “works well” or “a good way”)
• “A helpful resource for…” (→ “a useful tool” or just describe what it does)
• “This provides valuable information” (→ “This covers…” or “You’ll learn…”)

✅ CORRECT (direct and natural):

• “This shows you how…” or “You’ll learn…”
• “This works well” or “A simple method for…”
• “This tool helps you…” (describe what it actually does)
• “This covers…” or “Here’s what you need to know…”

The test: Nothing is ever just “useful” in AI writing - it’s always “valuable” or “effective.” If you find yourself reaching for these words, describe the actual benefit instead.

4. Em Dash Usage - STRICTLY FORBIDDEN

Em dashes (—) are UNNATURAL in web content. They almost always violate the “fewer ideas per sentence” rule. Even if examples or style guides use them, DO NOT COPY THIS PATTERN.

Common em dash patterns and how to fix them:

❌ WRONG (dramatic outcome): “Most CRMs just store contact info and log calls. The best ones automate lead scoring, predict customer churn, and trigger personalized outreach—turning your sales data into actual pipeline growth.”

✅ CORRECT: “Most CRMs just store contact info and log calls. The best ones automate lead scoring, predict customer churn, and trigger personalized outreach to turn your sales data into actual pipeline growth.”

❌ WRONG (qualifying detail): “Most beginners can learn Python basics in 3-6 months—with consistent daily practice—though mastering advanced concepts like algorithms and data structures takes 1-2 years.”

✅ CORRECT: “Most beginners can learn Python basics in 3-6 months with consistent daily practice. Mastering advanced concepts like algorithms and data structures typically takes 1-2 years.”

❌ WRONG (list elaboration): “There are three main types—public, private, and hybrid—each with different security and cost tradeoffs.”

✅ CORRECT: “There are three main types: public, private, and hybrid. Each has different security and cost tradeoffs.”

Natural alternatives to em dashes:

• Periods (break into separate sentences)
• Commas (for non-essential details)
• Colons (for lists or elaborations)
• Natural conjunctions: “to”, “by”, “with”, “if”

Why this matters: Em dashes pack multiple ideas into one sentence, creating unnatural complexity. Breaking them apart produces clearer, more conversational writing.

Summary: Humans don’t talk like they’re permanently writing professional emails. Remove the subtle polish. Say “good” when you mean good, not “thoughtful” or “insightful.” Write plainly unless the situation genuinely warrants emphasis. And NEVER use em dashes.

Sentence Structure & Clarity

• Vary sentence structures: Mix short and long sentences to create rhythm
• Active voice: Use active voice for clarity and directness
• Address the reader: Use “you” to make content engaging
• Paragraph splitting: Break paragraphs every 1-2 sentences for readability (use double newlines)
• Casual transitions: It’s fine to start sentences/paragraphs with “But…” or “So…” for natural flow
• Typography for emphasis: Use bold, italics, strikethrough, or CAPS within sentences to add personality and highlight key points

Using Uncertain Phrases (“might”, “could be”, “probably”)

✅ WHEN TO USE uncertain phrases:

1. Addressing reader thoughts: “You might be wondering…” or “This could be confusing…”
   • Fine to assume/anticipate what reader is thinking
2. Inherently uncertain topics:
   • SEO results: “This change will likely improve rankings” (SEO is probabilistic)
   • Human behavior: “Users might prefer this approach” (behavior varies)
   • Competitor analysis: “They could be struggling with…” (incomplete information)

❌ AVOID uncertain phrases for:

• Deterministic facts: Don’t say “X might be the standard” when X IS the standard
• Technical definitions: “SOC 2 could be a compliance framework” → “SOC 2 is a compliance framework”
• Established processes: “This probably works by…” → “This works by…”

Rule of thumb: If it’s a fact you can verify, state it definitively. Only hedge when uncertainty is inherent to the topic.