temperinglisted

# Tempering Convert a message the sender cannot send into one they can, without discarding the request it carries. ## Why the obvious rewrite fails Built-in polish features fail the same way every time: they remove the emotion and the substance together. "Is anyone actually going to decide this or not?" becomes "Would you be able to share the final decision or an estimated timeline?" — grammatically professional, and now containing no deadline, no consequence, and no reason for the recipient to prioritise a reply. The urgency was carried entirely by the tone, and the rewrite deleted it. The operating principle: **remove the attack on the person, preserve the pressure on the problem.** ## Method Every effective rewrite combines the five transforms below. Nothing further is required; additions beyond these are usually padding. | # | Transform | Before | After | |---|---|---|---| | 1 | Person to artefact — assess the work, not the judgement behind it | You're being an idiot | There are a few things in this approach I can't follow | | 2 | Emotion to impact — replace the sender's state with the cost to the business | This is infuriating | If this stays blocked, Friday's release slips | | 3 | Accusation to dated request — an accusation looks backwards, a request looks forwards | Are you going to do this or not | Can we lock this down by Wednesday | | 4 | Open complaint to closed question — a complaint can be ignored, a direct question cannot | Still no straight answer | Is i