Back to playbooks

Writing Playbook (Bridge + Receipts + One Ask)

This is a small, repeatable writing stack for “showing up” online without becoming needlessly harsh.

The goal is not winning arguments. The goal is: clear + checkable + bridge-building + one next step.

What’s inside

• Bridge Language
  Connection-first lines that keep you human, plus “bridge + boundary” exits to avoid circular comment fights.

• Post Frames (Small Set, High Reuse)
  A small set of reusable post structures (one point each).

• Channel Shapes What changes across Facebook, Substack notes, Substack posts, blogs, and notes.

• Editing Checklist (Integrity Gate)
  The pre-publish integrity gate: evidence labeling, mechanism, tone, and one action.

• Receipts Stubs (Backlog)
  A “backlog” format for facts you want to source properly before posting.

• Action Menu
  A tiny library of repeatable actions so every post can end with something concrete.

Default workflow (5 minutes)

1. Pick a frame (one point)
2. Write the post in plain language
3. Run the editing checklist
4. Add one action (from the action menu)
5. Add a boundary line if the topic is high-heat
6. If you need stats: add a receipts stub instead of guessing

Definition of Done for a post

A post is done when it has:

1. one point
2. evidence labeled
3. mechanism named
4. one ask with a decider or a time box
5. a boundary line if the topic is high-heat

Series spines

Every post should ladder into at least one of these:

• monthly squeeze
• market power and competition
• admin drag
• capacity and abundance
• guardrails and accountability
• information hygiene and shared reality
• anti-scapegoating

Success criteria

A post is “good” if:

• you’re not embarrassed reading it tomorrow
• it’s clear what’s confirmed vs unknown
• it names a mechanism (not a villain story)
• it ends with one doable next step

Back to playbooks