Which phrasing avoids blaming others when raising a workload concern?

Which phrasing avoids blaming others when raising a workload concern?

• A. I feel overwhelmed when the workload is this high, and I’d like to discuss possible adjustments.
• B. You always pile too much on me.
• C. This plan will never work.
• D. Let's just do nothing.

Answer: (A)

Raising a workload concern effectively relies on nonblaming language that centers your experience and seeks collaboration. The best phrasing uses an “I” statement to own how the workload affects you and to invite discussion about solutions. “I feel overwhelmed when the workload is this high, and I’d like to discuss possible adjustments” does this beautifully: it names your emotion, links it to a specific situation, and clearly requests a collaborative path forward. It signals you’re looking for a constructive change, not to accuse anyone. Context helps here: focusing on impact rather than blame keeps the other person from getting defensive and makes it easier to troubleshoot together—perhaps by redistributing tasks, extending timelines, or prioritizing deliverables. The other approaches tend to derail the conversation. Blaming language (“You always pile too much on me”) assigns fault and invites defensiveness. Negative statements about the plan (“This plan will never work”) shut down collaborative problem-solving. Suggesting nothing at all (“Let’s just do nothing”) avoids addressing the issue and postpones a needed adjustment.

Raising a workload concern effectively relies on nonblaming language that centers your experience and seeks collaboration. The best phrasing uses an “I” statement to own how the workload affects you and to invite discussion about solutions. “I feel overwhelmed when the workload is this high, and I’d like to discuss possible adjustments” does this beautifully: it names your emotion, links it to a specific situation, and clearly requests a collaborative path forward. It signals you’re looking for a constructive change, not to accuse anyone.

Context helps here: focusing on impact rather than blame keeps the other person from getting defensive and makes it easier to troubleshoot together—perhaps by redistributing tasks, extending timelines, or prioritizing deliverables.

The other approaches tend to derail the conversation. Blaming language (“You always pile too much on me”) assigns fault and invites defensiveness. Negative statements about the plan (“This plan will never work”) shut down collaborative problem-solving. Suggesting nothing at all (“Let’s just do nothing”) avoids addressing the issue and postpones a needed adjustment.