Written criticism is one of the situations I found most uncomfortable when I first started working with Australian colleagues. Back in Hong Kong, critical feedback — in any direction — tended to happen in conversation, not in writing. Writing things down felt permanent. It felt more aggressive than it probably needed to be. So I either softened it past the point of usefulness, or avoided it altogether.
That does not work well in Western workplaces, where written feedback is a normal and expected part of the job — code reviews, document reviews, performance cycles. The question is how to be honest and clear without coming across as cold, harsh, or personally critical.
The Structure That Works Across Cultures
Before getting into regional variation, here is a baseline structure for written critical feedback that works well in most Western professional contexts:
- Acknowledge what is working — specific, not generic.
- State the issue — specific, focused on the work or behaviour, not the person.
- Explain the impact — why it matters, what it affects.
- Suggest or invite a path forward — a concrete next step or a question.
This structure — sometimes called the situation-behaviour-impact model in management training — separates the person from the work, links the issue to a real consequence, and closes with a forward-looking action rather than a verdict.
The Specificity Rule
The most common failure in written critical feedback is vagueness. Vague feedback reads as passive-aggressive to most English readers, and feels unfair to the person receiving it who wants to improve.
Before (vague): "The report needs improvement."
After (specific): "The executive summary in section 1 states the conclusion before the supporting analysis — most readers will want the evidence first so they can evaluate the conclusion. Moving the summary to page 3 would fix this."
The specific version explains exactly what is wrong and why. It is more work to write, but it is also harder to experience as a personal attack, because it is clearly about the document.
Behaviour vs Character
Feedback that attributes a problem to the person's character or attitude is harder to act on and more likely to feel hostile than feedback that describes a specific behaviour or output.
Before: "You need to be more careful with your work."
After: "Section 3 has several figures that don't match the source data — I've annotated them. Can you verify these against the raw numbers before we circulate?"
Regional Calibration for Critical Feedback
The degree of directness in feedback varies by professional culture.
Australian: Reasonably direct. Specific criticism of work is acceptable without extensive softening, provided it is clearly focused on the work and not the person. A light opening acknowledgement of what works is considerate; multiple paragraphs of positive framing before a single line of critique is not expected.
British: More softened. British professional feedback tends to use more hedging ("it might be worth considering..."), indirect framing ("one thing I wondered about was..."), and a longer positive opening before the critique arrives. This is the convention for delivering criticism while preserving the relationship.
American: Relatively direct, but values positive framing and specific actionability. American feedback culture has been shaped by management training that emphasises the "compliment sandwich." Strike a balance between acknowledging strengths and getting to the point.
The Written vs Verbal Rule
A useful principle: save the most direct feedback for in-person or video conversations. Use written feedback for:
- Specific, detailed technical critique that benefits from being visible and referenceable.
- Positive feedback (written recognition is particularly valued).
- Situations where the recipient needs time to reflect before responding.
Avoid writing feedback that you would not say in person. If a message reads harsher in writing than you intended, it will almost certainly read harsher still to the recipient.
Common Patterns to Avoid
The invisible critique: "This is an interesting approach." Without further comment in a feedback context, this phrase reads as either non-committal or mildly dismissive. If you mean it positively, say so explicitly. If you have a concern, state it.
The excessive qualifier sequence: "This is not necessarily wrong per se, and I'm sure you had good reasons for this choice, but perhaps one might consider whether a slightly different approach could potentially have merit..." — this reads as passive-aggressive because the recipient can tell criticism is coming but has to wait through a long build-up for it. Get to the point.
The "but" pivot: Opening with genuine praise and then using "but" to introduce the criticism undermines the praise: "This is really well-written, but the core argument doesn't hold." Try "and" or a new sentence instead.
How Local Tone Handles This
When you paste feedback text into Local Tone, the analysis identifies vague characterological critique, excessive qualifier sequences, and structural problems like burying the main issue. The rewrite structures the feedback according to the region-appropriate convention you have selected, explains the changes, and preserves your specific observations. You can then decide which suggestions to accept.
For related reading, see the politeness gap in Asian English and the article on writing one-pagers that don't read as translated.