2211 S 39th St, St. Louis, MO

Write
less
badly.

Sample Lessons

Five rewrites, five kinds of Tuesday

These are shortened examples of what a full lesson covers. Each one shows a real workplace message rewritten, with a short explanation of what changed.

Email

The follow-up that finally gets answered

Vague check-ins get skipped. A specific ask with a deadline gets a reply.

Before

"Hi team, just wanted to check in and see if there were any updates on the thing we discussed last week regarding the budget approvals. Let me know when you get a chance, no rush at all, just following up. Thanks so much!"

After

"Hi team, following up on budget approvals from last week. I need a yes or no by Thursday to keep the vendor timeline on track. Can you confirm status today?"

What changed: the ask moved to the first line, "no rush" was removed since it wasn't true, and a concrete deadline replaced "when you get a chance."

Slack message

A message that doesn't sound like an ambush

Loose, lowercase messages read as low-stakes, until someone opens them expecting a quick question and finds three.

Before

"hey can we talk sometime today? not urgent just have a few things to go over whenever ur free"

After

"Have 15 minutes today for the Q3 roadmap? I have three questions and want your call on scope before Friday. Free at 2 or 4?"

What changed: "a few things" became a stated number and topic, and two concrete time options replaced an open-ended "whenever."

Status update

An update that reads in thirty seconds

Paragraph-style updates hide the one line a manager actually needs.

Before

"This week we made progress on the onboarding flow, met with design twice, and continued testing. There's a small issue with the API that we're looking into, but otherwise things are moving along and we should have more to share soon."

After

Done: Onboarding flow, design sign-off.
Doing: QA on the new signup screen.
Blocked: API rate limit issue, need backend input by Wednesday.

What changed: the update moved from narrative to a Done / Doing / Blocked format, so the blocker is the first thing a reader sees.

Meeting notes

Notes that don't trigger a reply-all

A transcript-style summary forces readers to hunt for decisions. A structured one doesn't.

Before

"We talked about the launch date and there were some concerns about timing, Priya mentioned the vendor contract, and Sam brought up marketing needing more lead time. We'll circle back next week."

After

Decision: Launch moves to March 14.
Owner: Priya, finalize vendor contract by March 3.
Owner: Sam, send marketing lead-time request by Friday.

What changed: discussion was separated from decisions, and every open item got a named owner and a date.

Proposal

An ask that shows up before page three

Proposals that bury the recommendation risk getting shelved instead of decided on.

Before

A four-paragraph introduction covering market context, team background, and general goals, with the actual recommendation and cost appearing halfway down page two.

After

Recommendation: Move to the annual plan with Vendor B. Cost: $18,400/year, a decrease from current spend. Decision needed by: March 20, to align with contract renewal.

What changed: the recommendation, cost, and decision deadline moved to the top, with supporting context pushed below.

Have a message you're stuck on? Ask us about it.

Contact Dojomi

We use cookies to run this site and understand how it's used. Learn more.

Cookie preferences

Strictly necessary

Required for basic site function. Cannot be disabled.

Functional

Remembers settings like form inputs and preferences.

Analytics

Helps us understand which lessons and pages are used.

Advertising

Used to measure the performance of any ads that reach this site.