How to Tell Someone Their Work Isn't Good Enough

You tell someone their work isn't good enough by stating the specific gap between their output and the expected standard, then outlining the impact and required changes. This isn't about criticizing the person. It's about addressing a performance deficit directly and practically.

Delivering tough feedback is uncomfortable. Most managers and colleagues avoid it or sugarcoat it. They say things like, "It needs a bit more work," or "Let's revisit this." This vague language doesn't help. It leaves the recipient confused, frustrated, and without a clear path forward. The work doesn't improve. The problem persists.

Why "It Needs Work" Fails Every Time

Imagine your manager says, "The Q2 report you submitted needs work." What does that mean? Is it the data? The formatting? The analysis? The conclusion? You're left guessing. You might spend hours revising the wrong sections, only to deliver another version that still "needs work."

Vague feedback creates ambiguity. Ambiguity breeds resentment and wastes time. The person receiving the feedback can't improve if they don't know what specifically needs improvement. They can't meet expectations they don't understand. This isn't kind. It's inefficient and ultimately damaging to both the individual's growth and the team's output.

Your goal is not to make someone feel good. Your goal is to ensure work meets standards. Be specific. Be direct. That's the only way to drive actual change.

The Plain Truth: Specificity is Kindness

Effective feedback pinpoints the exact discrepancy between what was delivered and what was expected. It removes guesswork. It provides a clear target for improvement. This requires you to have a clear understanding of the standard yourself. If you can't articulate the expected quality, you can't give useful feedback.

Instead of "The Q2 report is weak," say: "The Q2 sales projections in your report lack detailed analysis for regions 3 and 4, specifically missing historical conversion rates and competitor analysis. The executive summary also doesn't clearly state the key takeaways for leadership."

This is not an attack. It's a diagnosis. It gives the recipient actionable information. They now know exactly which parts of the report need attention and why.

The Conversation Structure: O.I.E.S.

This four-step framework provides a robust structure for delivering performance feedback. It ensures clarity, focuses on the work, and offers a path forward.

1. Observation: State the Facts, Not Your Opinion

Start with objective, observable facts. Describe the specific work or behavior. Remove emotion and judgment. Stick to what you saw or heard.

Scenario: A junior designer submitted a logo draft for a new client, but it clearly doesn't meet the brand guidelines discussed in the brief.

What to say: "I've reviewed the logo draft for the 'Acme Corp' project. I noticed the primary color palette used is #C0C0C0 and #0000FF. The brand guidelines we established require a palette of #FF0000 and #00FF00. Also, the design incorporates a serif font, while the brief specified a sans-serif font for all branding elements."

Notice there's no "I think," "I feel," or "It looks bad." Just concrete details.

2. Impact: Explain the Consequences

Clearly articulate the consequences of the observed work or behavior. Why does this matter? What's the cost? This connects the performance gap to tangible outcomes for the project, team, or business.

What to say: "Using the wrong color palette and font means this design doesn't align with the client's established brand identity. If we present this, it will likely be rejected, requiring a full redesign. This directly impacts our project timeline, potentially delaying the launch by a week and costing us additional billable hours."

The impact statement makes the feedback relevant. It shows the employee why their performance matters beyond just 'following rules.'

3. Expectation: Define the Required Change

State precisely what needs to be done differently or what the new standard is. Be clear, measurable, and time-bound if possible. This is not a suggestion; it's a requirement.

What to say: "I need you to revise the logo design. Ensure the primary color palette strictly adheres to #FF0000 and #00FF00, and all text elements use a sans-serif font. The revised draft needs to be submitted by 5 PM on July 23, 2026."

There's no room for misinterpretation. The employee knows exactly what they need to deliver and when.

4. Support: Offer Resources and Assistance

This isn't about softening the blow. It's about demonstrating your commitment to their success and providing the tools they need to meet expectations. It transitions from evaluation to development.

What to say: "To help you with this, I've linked the full brand guidelines document again in our chat. I've also booked 30 minutes for us tomorrow morning at 9 AM to review your progress and answer any questions you might have before you finalize the revision."

This shows you're invested in their improvement, not just pointing out flaws. It also creates accountability for both parties.

Handling Tears or Defensiveness

Even with a clear structure, people react emotionally to feedback. Be prepared for defensiveness, frustration, or tears. Your job is to stay calm, focused on the facts, and maintain the professional boundary.

When They Get Defensive:

Acknowledge without agreeing: "I hear your perspective on the challenges you faced."
Re-anchor to the facts: "My concern remains the missing data points in regions 3 and 4, which were a core requirement for this report."
Repeat the expectation: "The priority now is to get those sections updated to meet the standard. How can we ensure that happens?"
Avoid argument: Do not get drawn into a debate about who is right or wrong. Focus on the required outcome.

When They Get Emotional (Tears/Frustration):

Pause and offer space: "I can see this is difficult. Would you like a few minutes to compose yourself?" Offer a tissue if appropriate.
Acknowledge the emotion, not the validity of their feelings as an excuse: "I understand this is tough to hear."
Re-center on the work: "My intention here is to help you develop and ensure the project meets its objectives. The feedback is about the work, not you personally."
Maintain professional distance: Avoid getting overly sympathetic or veering into therapy-speak. Keep the conversation focused on performance and solutions.

Your role is to guide the conversation back to the objective: improving the work. Don't let emotions derail the purpose of the feedback session.

Delivering direct feedback isn't easy, but it's essential for professional growth and project success. The O.I.E.S. framework gives you a concrete method to ensure your message is clear, actionable, and productive. It moves you past the discomfort of vague criticism into the realm of specific, impactful guidance.

The fastest way to internalise this is repetition. Practice in ConvoForge lets you run the conversation ten times in ten minutes with an AI that pushes back, helping you refine your delivery and handle tough reactions before the real thing. Practice until these structured conversations become second nature. You'll deliver feedback with confidence and clarity, every time.