Four workshops.
One clear outcome.

Email is where most professional writing happens and where most clarity problems show up first. This workshop focuses on the mechanics of an email that gets read, understood, and acted on. We look at how subject lines either earn or lose the open, how the first sentence sets or breaks reader expectation, and how to make the action you need from your reader impossible to miss.

The live editing session for this workshop tends to be the most immediately applicable. Participants usually come with something in their inbox they've been struggling to respond to or draft. We work through it together.

A proposal is an argument, and arguments have structure. This workshop examines how the sequence of information in a proposal either builds confidence in your recommendation or undermines it. We look at proposals that buried the recommendation in section four (common), proposals that front-loaded so much context the reader gave up (also common), and what the structure looks like when it works.

We spend particular time on executive summaries, which are often the only section a decision-maker reads. If your summary can't stand alone, your proposal is already in trouble.

Project updates fail in a specific way: they report activity instead of status. "The team completed X, worked on Y, and is currently doing Z" tells your stakeholders nothing about where the project actually stands. This workshop introduces a structural framework for updates that separates status from activity and makes risks and blockers visible rather than buried.

We also cover how to calibrate the level of detail to the audience. What your project team needs to know and what your executive sponsor needs to know are different documents, even if the project is the same.

Performance reviews are some of the most consequential documents professionals write, and some of the least carefully structured. Vague praise and vague criticism both fail the person receiving the review. This workshop focuses on how to write reviews that are specific enough to be useful — citing observable behavior, not personality traits, and connecting observations to impact.

We also address the challenge of writing reviews that align with ratings. If someone receives a "meets expectations" rating but the written review only mentions positives, you've created a document that contradicts itself. We show you how to make the words and the rating tell the same story.