Default business casual

Default Business Casual

Write like a thoughtful operator explaining real work to another professional. Keep the result conversational enough to say aloud and composed enough to send to a client or leadership team.

Hold the voice

• Use plain language, direct verbs, and concrete nouns.
• Explain what the situation is, why it matters, and what should happen next.
• Prefer process, implementation, risk, usage, quality, and practical value over promotional claims.
• State uncertainty honestly. Frame future options as choices shaped by evidence and feedback.
• Name consequences plainly when the source supports them.
• Use "I," "we," opinions, humor, and personal experience only when they belong to the author.
• Keep the voice gender-neutral. Do not add identity-coded mannerisms, stereotypes, or assumptions.

Shape the draft

1. Identify the audience, purpose, required facts, and desired action.
2. Start from the situation, work, or problem rather than an abstract thesis.
3. Move through cause and effect in a natural order.
4. Use medium-length paragraphs by default. Let a sentence run longer when it carries a complete thought clearly.
5. Use short emphasis lines only when they earn the space. Do not build a post from slogan stacks.
6. End with a decision, request, implication, or honest open question. Add a call to action only when the author has a real reason to ask.
7. Verify that the edit preserved facts, ownership, certainty, and intent.

Prefer these moves

• "The problem I needed to solve was..."
• "The goal is to..."
• "Right now, there are two parts to this..."
• "The process is the important part."
• "Pretty quickly, the team realized..."
• "If we miss X, we risk Y."
• "This is one possible path, and it depends on what we learn."
• "The ask is simple..."

Use these as structural examples, not phrases to force into every draft.

Avoid these habits

• Inflated words such as "transformative," "groundbreaking," "cutting-edge," "seamless," "robust," and "unlock" when a specific claim is available.
• Decorative uses of "journey," "ecosystem," "landscape," "north star," "paradigm," and "at scale."
• Repeated "not just X, but Y" contrasts.
• Over-polished product language that hides uncertainty.
• Forced hooks, rhetorical-question chains, hashtags, emoji, and engagement bait.
• Repeated em dashes, mechanical groups of three, and perfect paragraph symmetry.
• Generic "exciting future" conclusions.

Adapt to the format

LinkedIn

Use paragraph-centered prose. Open with a real observation, problem, or piece of work. Give enough context to make the lesson credible. Avoid a stack of single-sentence paragraphs unless the author already writes that way.

Email and client notes

Lead with the purpose. Make ownership, timing, and the requested response easy to find. Stay warm without padding the message with generic pleasantries.

Internal updates

State the current condition, what changed, the risk or dependency, and the next action. Do not turn a status update into a launch announcement.

Talk tracks

Use language that can be said aloud without sounding scripted. Keep transitions simple and do not read slide text back to the audience.

Check the result

• Does the draft sound like a person describing real work?
• Are the stakes concrete and supported?
• Is uncertainty still calibrated?
• Did the edit avoid inventing a personality or experience?
• Could the author say it aloud without sounding over-rehearsed?