Write Once, Ship Five Times: One Voice Memo Becomes Email, Slack, Doc, Ticket, and Tomorrow’s Brief

Work less, ship more — a six-part series. 1. Sunday setup · 2. Don’t open Slack first · 3. Leave the meeting when it ends · 4. Write once, ship five times · 5. Your first overnight agent · 6. The 4-hour Friday

You already said it out loud, or you already wrote it once. Then you wrote it again as an email, again as a Slack message, again as a ticket, again as a doc. That is not communication. That is a tax. One messy source. Five outputs. Then you stop.

This is part 4. It uses the same chat and dump from the Sunday setup. It is the cousin of leaving the meeting when it ends. That post is for a room you just left. This one is for the thing in your head that has to go to four places before Friday.

The source is allowed to be ugly

A 90-second voice memo. A dump paragraph with typos. A screenshot of notes. A meeting leave-behind. That is the source. You do not outline first. Outlining is draft number two.

Paste it. Then name the five ships, even if you only need three today:

1. Email — the person who needs a decision or a record
2. Slack / Teams — the people who only need the headline
3. Doc — the version that will still make sense in a month
4. Ticket — the work object: owner, done-when, not a novel
5. Calendar or brief — the time it stole, or the decision it created for tomorrow morning

If a ship has no audience, skip it. Five is the ceiling, not a quota. The rule is you do not open a sixth tab to rewrite the same paragraph by hand.

The prompt

Here is one source. Turn it into only the ships I list. Keep the facts identical across all of them. Do not invent people, dates, or commitments. If something is missing, put a [bracket] instead of guessing.

Ships:
1) Email to [who], 6–8 sentences, my voice, short, one ask.
2) Slack to [channel or person], 3 lines max.
3) Doc section: heading + 5 bullets a stranger could follow next month.
4) Ticket: title, owner, done-when, 3 acceptance lines.
5) One line for tomorrow’s brief (a decision or a skip).

I am [name / role]. Protect my stop time. I will send these as-is after one pass.

One pass means you fix names and tone. It does not mean you start over in Google Docs. If you are rewriting from scratch, the source was too thin. Talk for another 30 seconds and paste again.

What each ship is for

Email carries the ask and the record. One ask. If you have two asks, you have two emails, or you have a meeting.

Slack is the headline plus a link or “details in the email.” It is not the email pasted into a channel. That is how you train people to ignore you.

Doc is for the next person, including you in three weeks. No “as we discussed.” No vibe. Facts and the decision.

Ticket is a done-when, not a diary. If the chat writes a paragraph of context, cut it. The context lives in the doc. The ticket points at the doc.

Brief line is how this system talks to tomorrow morning. “Send the invoice reply” or “skip, waiting on Maya.” If it does not change tomorrow, do not add a line.

A real source, so you can see the shape

You mutter into your phone after a client call: They want the proposal by Thursday. Scope is the landing page and the email sequence, not the app. I said 8 to 10k if we stay in that box. Jake will send brand files. I need to tell the team we are not starting the app work. I should block two hours Tuesday.

That becomes:

• Email to the client confirming scope, range, Thursday, and the brand-file ask
• Slack to the team: landing page + emails only, app is parked, details in the doc
• Doc: scope in / scope out, date, range, open item (brand files)
• Ticket: “Draft proposal — landing + email seq, due Thursday”
• Brief: “Protect Tuesday 2-hour proposal block; wait on Jake’s files”

Same facts. Five costumes. You send them before you reward yourself with a different tab.

What you refuse

• Do not keep a “content engine” of extra tools for this. The chat is the engine. The dump is the archive.
• Do not ask it to “make it more professional” until the facts are right. Polish last.
• Do not ship all five if two will do. The win is not volume. The win is not rewriting.
• Do not paste Slack back into the chat to “improve it” for twenty minutes. One pass.

Do it once this afternoon

Pick a thing you have already explained twice this week. Voice-memo the version in your head. Run the prompt. Send two of the ships. Put the rest in the dump if they are not due today.

The Sunday setup made the buckets. The brief protects the morning. The meeting leave-behind protects the afternoon. This one stops you from paying the rewrite tax. Next: your first overnight agent — one recurring chore only, so the teammate does not become a second job.

Work less, ship more — a six-part series. 1. Sunday setup · 2. Don’t open Slack first · 3. Leave the meeting when it ends · 4. Write once, ship five times · 5. Your first overnight agent · 6. The 4-hour Friday