← The Operations Station ~ dish 06 of 10 · the operations station

Standard Internal Communication

Every business has a house voice. The way the team writes emails. How meeting notes look. The format of internal docs. The station can read that voice and draft messages that sound like the team wrote them. The leverage is training. You have to show the station three real examples of how you actually write.

The job

A manager spends thirty minutes a day writing internal emails. Status updates. Handoffs. Requests. The messages are important but repetitive. Same structure. Same tone. Same format. Then the station reads a message that started in chat and drafts the formal email version. It matches the team’s voice. It’s published. The manager saves thirty minutes a day.

The dish learns the house voice from three internal emails you wrote yourself. It reads a message request (in chat, from a meeting, from a form). It drafts an internal email, memo, or handoff note that sounds like you wrote it. Not generic corporate. Not sales-y. Like the voice people already know. The message lands in Slack or email ready to review and send.

Plated well, this looks like: internal communication is consistent. New team members learn the tone from real examples, not style guides. Information flows predictably. The voice is so familiar that a drafted message reads like it came from inside, not outside.

The recipe

All seven ingredients still apply. The leverage is Training (Ingredient #1). The station needs three real internal emails you wrote. With all the quirks. The way you actually start messages. The structure you use for status updates. The closing language. This is your house standard.

Context (Ingredient #2) is the second lever. The station needs to know what counts as “internal communication.” Status updates to the team. Handoffs between departments. Requests for resources. Meeting agendas. The station learns the boundary.

Examples (Ingredient #4) are the training set. Three emails from the last two weeks. In your voice. With the real structure. Guardrails (Ingredient #3) matter here too. The station’s draft should stay within your house tone. No flowery language if you don’t use it. No corporate jargon if your team doesn’t.

How to build it

  1. Define what counts as internal communication. Status updates. Handoffs. Requests. Meeting agendas. Not every message. The messages that matter. That set the tone.

  2. Capture your house voice. Read three internal emails you wrote recently. The tone. The structure. The opening line. The closing. The way you handle tough feedback. The way you acknowledge someone’s work.

  3. Pull three examples from the last two weeks. Real emails. With names redacted if needed. The ones that represent how you actually write. Not the perfect ones. The real ones.

  4. Define the structure for each message type. Status update: what we shipped, what’s blocked, what’s next. Handoff: context, what we’re handing off, what the next person needs to know. Request: why we need this, what we need, when we need it.

  5. Show the station your examples. These are the training set. It learns the patterns. The way you open. The way you close. The details you include.

  6. Have the station draft a status update. You take a bullet-point list from a meeting. The station drafts the email version. Does it sound like you. Does the tone match. Does the structure land right.

  7. Refine the training if needed. If the draft is too formal, show the station a more casual example. If it’s missing context, show the station where you usually add context and why.

  8. Publish the standard. Now internal communication has a consistent voice. New team members read past emails and understand the standard. The Chef doesn’t have to coach tone.

What breaks it

  • Examples are from different voices. You pull one email from a pressured day (curt) and one from a good day (warm). The station doesn’t know which one is the house standard. The drafts bounce between tones.

  • The message type isn’t defined. The station knows status updates but not handoffs. When a handoff request comes in, it defaults to status-update structure. The format breaks. The tone lands wrong.

  • No guardrails on tone. The station drafts something too formal or too casual. The Chef has to rewrite it every time. The station never learns the house standard because feedback isn’t coming back.

  • Examples are edited. You pull emails you’ve already polished. The station trains on the final draft, not the actual voice. Real emails are messier. The station trained on ideals gets surprised by reality.

When it’s working

By week one, the station drafts a status update. Seventy percent of the tone is right. Thirty percent needs a voice nudge. By week two, the Chef is only editing for content (adding a detail, removing a tangent). The voice is locked. By week three, the draft goes out as-is on half the status updates. By week four, internal communication reads like the team wrote it because the team did. The station is just the typist.

The signal that the recipe is sharp: someone new joins the team, reads the internal emails the station drafted, and assumes they came from one of the tenured operators because they match the house voice that well.

Monday Move

Write three internal emails today. A status update. A handoff. A request. Don’t edit them. Show the station. Have it draft next week’s status update while you watch. Where does it match your voice. Where’s it different. That gap is what needs training.

Dish 6 of 10 on the Operations Station. Build-note leverage: Training (Ingredient #1).