5 exercises — calibrating directive strength with mitigation structures for code review and design feedback, from soft nits to blocking issues.
Key patterns:
could you / would you — polite request, standard for peer review
it might be worth / have you considered — strongly hedged suggestion
needs to be fixed — firm but professional, for blocking issues
match mitigation strength to actual priority — over-hedging urgent issues is a real failure mode
0 / 5 completed
1 / 5
A code review comment gives feedback on a colleague's pull request. Which version is a correctly mitigated (softened) directive, appropriate for peer feedback rather than a command?
"Could you...?" mitigates the directive by framing it as a polite request rather than a command, which is the conventional register for peer code review feedback. "Must" (option B) is a strong obligation modal, appropriate for hard requirements or policy, but overly forceful for a stylistic suggestion between peers. The bare imperative (option A) and imperative with "now" (option D) both read as commands, which can seem abrupt or hierarchical in a collaborative review context.
2 / 5
Which sentence uses a hedged suggestion structure ("might want to", "it may be worth") to mitigate a directive in a design review comment?
"It might be worth + gerund" is a strongly mitigated suggestion structure that frames the recommendation as optional and worth considering, rather than mandatory — useful when raising a lower-priority concern. "Need to" (option B) and "is required" (option D) both signal firm obligation, appropriate for blocking issues but too strong for a soft suggestion. The bare imperative (option A) is direct and unhedged.
3 / 5
A senior engineer wants to raise a concern about an architecture choice without being overly directive, since the decision has already been made. Which sentence best achieves this?
"Have you considered...?" is a strongly mitigated way to introduce an alternative, inviting reflection rather than issuing a correction — appropriate when a decision is already made and the goal is to open discussion, not override it. Option A is a blunt, face-threatening directive. Option C is a bare command. Option D uses a past modal of criticism ("should have"), which implies the earlier choice was a mistake and can come across as blaming rather than constructive.
4 / 5
Which sentence uses a mitigated directive with a downtoning adverb, appropriate for a low-priority nit in a code review?
Option C stacks a downtoning adverb ("perhaps") with a hedged verb (consider) and an explicit acknowledgment that the point is minor, clearly signaling low priority and optionality — appropriate for a nit-level comment. Options A, B, and D all present the change as required or non-negotiable, which would overstate the importance of what the reviewer frames as a minor stylistic point.
5 / 5
Which sentence correctly balances directness and politeness for a genuinely blocking issue that must be fixed before merge, avoiding excessive hedging that could obscure urgency?
Option B correctly matches directive strength to stakes: it uses a firm but professional obligation phrase ("needs to be fixed") and explains the concrete consequence, which is appropriate for a blocking issue. Option A over-hedges with stacked softeners ("maybe... possibly... perhaps"), which obscures the urgency of a merge-blocking bug. Option C is too blunt and provides no justification. Option D's hedging ("might be nice", "eventually", "sometime") dangerously understates a bug that will crash in production — mismatched mitigation can be as much a communication failure as excessive force.