Rewrite my feedback so they can't leave thinking it went fine
A grammatical audit for feedback about to be delivered: the readback test run twice, the tense-and-voice diagnostic, the one-ask counting rule, praise relocated below the problem — so the message that arrives is the message you meant, without cruelty doing the work of clarity.
Use when
- Use this on feedback you are about to send or say — a performance note, a review comment, a hard email to a colleague or vendor — when the stakes make you want to soften it.
- Use it when the last conversation like this one changed nothing and you filed it as delivered anyway.
The failure
The message gets softened until the person walks out comforted and uncorrected, and the conversation gets filed as delivered. Kindness stands in for clarity, the praise-to-substance ratio inverts, the one ask dissolves into three suggestions — and the correction that mattered arrives months later as a surprise with consequences, which is the cruelty the softening was trying to avoid.
The outcome
Feedback whose readback matches your intent: the recipient can state, in one sentence, what must change and by when — verified by running the readback test on the rewrite before it is sent.
The Practice — 5 rules
Run the readback test on the draft, before touching it
Read the draft as its recipient and write the one-sentence summary they would give a friend an hour later — the defensible, self-serving reading the text permits, not the intended one. Quote the spans that permit it. This readback is the reply's opening finding, stated before any edit: if the permitted reading is "it went fine, minor notes," say so in those words. The test is mechanical: the readback comes only from what the text says, never from what the writer meant.
Why Feedback fails at the reading, not the writing. The readback converts "is this too soft?" from a feeling into a checkable output — and running it before editing establishes the baseline the rewrite must beat.
Diagnose the grammar: who is the subject, and what tense is the correction in
Audit the sentences that carry the substance. Two tells, quoted where present: (1) agentless constructions and plural diffusion — "mistakes were made," "we all could have" — where the recipient never appears as the subject of a verb attached to the problem; (2) the tense asymmetry — praise in confident past indicative ("you delivered"), correction in conditional future ("it would be great if we could"). Count the asks: a message with three asks has no ask; name the one that survives. Report these as counts and quotes, not impressions.
Why Softening hides in grammar before it hides in word choice. A recipient can agree with every conditional sentence and correctly conclude nothing is required of them — the diagnostic makes that visible and countable.
Rebuild: problem first, praise after, one ask, a real stake
Rewrite so the problem leads in plain indicative with the recipient as subject, the single ask follows with its by-when, and the consequence is tied to a concrete stake — what becomes possible or impossible next — not to generic firmness. Move genuine praise below the substance and ban the bridge words (but, still, overall) that let it dilute; do not delete it, and do not inflate it. Keep every verifiable fact from the draft; where the rewrite needs a specific the draft lacks (a date, a number, an example), insert a bracketed placeholder and say the message fails without it — never invent one.
Why Order and grammar do the honest work tone was failing to do. The placeholder rule matters because one invented specific, discovered later, collapses the authority of everything around it.
Run the readback again on the rewrite — and let a clean draft pass
Run the same readback test on the rewrite and print both readbacks side by side: the summary the draft permitted, the summary the rewrite compels. If they differ in the way intended, the rewrite ships. If the original draft already compels the intended readback — the recipient is the subject, one ask with a by-when, a named stake — the verdict is SENDS AS WRITTEN, and the pass has its own deliverable: state the readback line the recipient will carry out of the room, confirm the ask and date are the ones intended, and stop. Wording you would merely phrase differently is a note, never a finding; you are not graded on finding softness.
Why The same instrument that found the fault verifies the fix — and the pass path produces the readback line, so a clean draft gets confirmation with content instead of manufactured coaching.
Close with the private-version calibration
Ask the writer to compare the rewrite against how they would describe the situation to a trusted peer in confidence. If the private version is materially harsher than the rewrite, name the paragraph carrying the gap — usually the consequence — and state the one sentence that would close it. If the private version matches, say the message is calibrated. Where the draft supports two readings of the recipient's situation (a performance problem, or an assignment problem the writer owns half of), state both and which the quoted facts support. Keep the whole reply under about 450 words plus the rewrite.
Why The private-version gap is the most reliable measure of remaining softening, and it is a test the writer can run alone on the next message — which is what turns a rewrite into a practice.
Limits — do not use this when
- Not for formal performance-management processes, terminations, or anything HR owns — this is sentence craft, not employment procedure, and using it to build a paper trail misuses it.
- Not for feedback you have not yet decided is true. The method sharpens delivery; it cannot supply conviction, and sharpened doubt reads as cruelty.
- This method works on how sentences land, never on employment decisions. It is not HR guidance, not documentation for termination, and not a substitute for the processes those require.
- Every diagnostic quotes the draft: no softness claim without the span that shows it, and no motive claims about the writer — the method reads grammar, not character.
- The rewrite may not add facts. Missing specifics become bracketed placeholders with a warning, because feedback with an invented example is worse than feedback with a hole.
- If the underlying judgment is undecided — the writer does not yet know what they want changed — the honest output says so and stops; sharpening an undecided message manufactures conviction.
Verify — evidence that it helped
- The reply opens with the draft's permitted readback, quoted to its spans — before any edit.
- The grammar diagnostics are counts and quotes: subject-of-verb, tense asymmetry, number of asks.
- The rewrite leads with the problem in plain indicative, carries exactly one ask with a by-when, and ties the consequence to a named stake.
- Both readbacks appear side by side, and the rewrite's compelled reading matches the stated intent.
- A draft that already lands got SENDS AS WRITTEN plus its readback line — no manufactured softness findings.
- Any specific the draft lacked appears as a bracketed placeholder, never an invented fact.
Resources
Listed by the author. Ctrl AI does not fetch, preview, summarize or attest them.