Co-Writing with AI

Here's a paragraph from my blog post on why engineering retrospectives fail. It's factually correct but too passive and academic — it doesn't land with engineers.

My paragraph: "Retrospectives often fail because action items are too vague and unowned. When nobody owns an item, it tends not to get done. Teams lose faith in the process."

Rewrite this paragraph to:

• Keep my core argument exactly (vague unowned action items = nothing changes)
• Make it punchy for an engineering audience that has lived this frustration
• Active voice throughout
• Do NOT add new claims I haven't made
• Stay within 2–4 sentences — I'll keep editing after

I'm writing a technical article with working title: "Why Your PostgreSQL Queries Are Slow (And How to Fix Them)"

Target: backend developers with some query optimization experience but who haven't gone deep on execution plans. Goal: get them to read the whole thing and leave with 3 things they can do today.

Generate 6 headline variations, each using a different approach:

1. Outcome-focused (what they'll be able to do after reading)
2. Counterintuitive (something surprising about query performance)
3. Specific and numeric (includes a concrete number or percentage)
4. Pain/frustration-based (names a frustration they'll recognize)
5. Classic how-to
6. Single strong word opener

Format: numbered list, headline only, one per line. No explanations.