An email that made the required action clear

Most people preparing for a difficult conversation spend their energy on the conversation itself. Less attention usually goes to the earlier email that might make the conversation unnecessary, not because wording can guarantee that outcome, but because a clear message gives the other party something specific to act on.

The situation was straightforward in its facts and more complicated in its implications. A decision had been made by an institution. The outcome was unfavourable. The initial position appeared fixed, and there was a policy that supported it.

There was also an inconsistency: the rule had been applied differently in previous periods, and the person on the receiving end had reasonable grounds to expect a different result. The stakes were genuine rather than abstract, and the anxiety that came with them was real.

The instinct to over-explain

The first draft reconstructed the timeline in detail, documenting every inconsistency before making a single request, an attempt to make the position hard to dismiss by building a case around it before any objection had been raised.

A message that arrives pre-defended can read as though the sender already expects resistance. It was rewritten around a narrower question: what does the reader need in order to act?

Three decisions in the redraft

• , The inconsistency was stated once, plainly, without being built into an argument.
• , The outstanding permissions question was resolved in the email itself, so no further clarification was required before action could be taken.
• , The requested outcomes were listed specifically, with a clear next step rather than an open-ended request.

The matter was resolved without the follow-up conversation that had been anticipated. That is worth recording as a single case, not as proof that this structure produces this result in general. Other factors, timing, the specific policy, the person reading it, were also part of what happened.