Example 1 — Productivity Newsletter on Substack Variables filled in the prompt: [NEWSLETTER NICHE AND AUDIENCE]: "The Slow Edge" — productivity and deep work newsletter for knowledge workers aged 28-42 who feel overwhelmed by busyness and want to work less but achieve more — Substack [TOPIC]: Why working fewer hours often produces better output than working more [PERSONAL STORY]: I once worked 70-hour weeks for a month to hit a deadline — the work I produced in week 4 was worse than anything I'd done in week 1 working normal hours [RESOURCE]: Cal Newport's book "Deep Work" — specifically the concept of attention residue [CTA]: Reply to this email with the one task you've been avoiding that would make the biggest difference this week Generated output: ▸ TONE: Peer — the writer is on the same exhaustion journey as the reader, not above it. ▸ SUBJECT LINES: A) "The productivity lie that's keeping you busy but not effective" — Score: 8/10 B) "How to get more done by working 2 fewer hours a day" — Score: 7/10 C) "I worked 70-hour weeks for a month. Here's what broke." — Score: 9/10 ★ RECOMMENDED: C — Personal confession with a specific number creates immediate credibility and curiosity; the word "broke" creates an open loop the reader needs to close. ▸ PREVIEW TEXT: The output in week 4 was the worst work I'd done all year. ▸ NEWSLETTER BODY: It was 11pm on a Wednesday and I was rewriting a paragraph I had already rewritten four times. Not because it was bad. Because I couldn't tell anymore whether it was bad or not. My brain had been running at full capacity for 27 days straight and it had quietly stopped working — I just hadn't noticed yet. That month, I logged over 70 hours a week. I felt productive. I felt busy. I felt like I was doing everything right. The work disagreed. When I looked back at everything I'd produced that month, the pattern was brutal: the best work came in weeks one and two. By week three, I was maintaining. By week four, I was actively making things worse — overcomplicating, second-guessing, undoing good decisions I'd made when I was rested. Here's what nobody tells you about output: more hours don't compound. They decay. The research on this is unambiguous. Cognitive performance doesn't hold steady across long working hours — it degrades. And not gradually. It falls off a cliff around the 50-hour mark, and after 55 hours, the additional work produced is so poor in quality that it would have been better not to do it at all. But here's the part that hit me hardest: it's not just about fatigue. Cal Newport calls it attention residue — every task you switch to carries a mental tax from the last thing you were doing. The more tasks you pile into a day, the more residue accumulates. By hour ten, you're not working at full capacity on anything. You're working at 40% on everything, and you can't feel the difference anymore. The fix isn't glamorous. It's a hard stop time. It's fewer tasks on the list, not more. It's protecting one two-hour block per day where nothing interrupts — no messages, no meetings, no "quick questions." Not because it's pleasant, but because that block produces more real output than the other six hours combined. This week, I want to ask you something I wish someone had asked me that Wednesday at 11pm. What is the one task — the one you keep moving to tomorrow — that would actually move your work forward if you did it first, protected, with no interruptions? Hit reply and tell me. I read every one. ▸ P.S. LINE: The most productive people I know don't have better systems — they have better boundaries about when the day ends.