A Script for the "I Think You Dropped the Ball" Conversation

There are five words that make a coworker stop listening:

“I think you dropped the ball.”

The annoying part is that occasionally they did.

The deck was due Tuesday. The copy never landed. The ticket has been sitting in the same column since last week. Now your part of the work is stuck, and somehow you are the person who has to say the uncomfortable thing.

This is where new grads either wait too long or turn one missed handoff into a courtroom scene. I get it. Nobody wants to sound like they are auditioning to become the office hall monitor.

But there is a middle move. You do not accuse someone of being irresponsible. You name the missed handoff, the impact, and the next commitment.

That is the difference between blame and accountability. Blame asks for a villain. Accountability asks for the next working plan.

“Dropped the ball” is a character judgment

When you say, “You dropped the ball,” the other person hears more than a missed deliverable.

They hear:

• “You are careless.”
• “You made me look bad.”
• “I am keeping score.”

Maybe none of that is what you meant. It still lands that way.

The safer version is boring and specific:

“The launch deck is blocked because the customer quotes did not land by Tuesday.”

That sentence is harder to argue with. It does not diagnose their work ethic. It does not guess at their intent. It points to the fact, the timeline, and the downstream problem.

This is close to the feedback structure the Center for Creative Leadership calls Situation-Behavior-Impact: name the situation, describe the observable behavior, explain the impact. I like that frame because it keeps you from wandering into amateur psychology.

You are not saying, “You do not care about this project.”

You are saying, “This part is missing, and this is what it blocks.”

That difference saves relationships.

Start with a prep note, not a speech

Before you send the Slack or ask for five minutes, write down the facts.

Not because you are building a legal case. Because your brain will want to add adjectives once you are annoyed. Mine does too. The first draft in my head has occasionally been much sharper than the version I should have said out loud. The sharp version feels satisfying for four seconds, then creates two more meetings.

Use this instead.

If you cannot fill out those six lines, you may not be ready for the conversation yet. You may be irritated, but you are not clear.

Clarity comes first.

The script to use

Send a short note first. Do not write “we need to talk.” That line makes normal people assume they are being fired, dumped, or both.

Then, in the conversation:

That last line matters.

You are not threatening them. You are telling them the project needs a new plan if the old one no longer works. There is a real difference.

Why this works

The script does four useful things.

First, it keeps the conversation private. A peer reset should not start in a public channel unless the work truly requires it. Public correction creates a second problem: now the person has to manage the work and their embarrassment.

Second, it gives them room to explain. Maybe they missed it. Maybe the original deadline was vague. Maybe they were blocked by someone else and never said so. You do not have to pretend all reasons are equally good, but you should hear the reason before you decide what to do next.

Third, it turns the conversation toward the next handoff. The goal is not to get a confession. The goal is to keep the work from failing twice.

Fourth, it creates a clean record if you do need to escalate later. If the person misses the reset deadline too, you can tell your manager: “I checked with Jordan on Tuesday. We agreed on noon Wednesday. The file still has not landed, and the QA slot is now at risk.”

That is much stronger than: “Jordan keeps dropping the ball.”

One sounds like a person trying to protect the work. The other sounds like a person trying to win a blame round.

If you are new, use the softer version

If you are in your first few weeks, slow down.

A week-two employee telling a peer they “dropped the ball” can read as overreach, even when the employee is technically right. That does not mean you stay silent. It means you frame the conversation as a dependency check.

That protects you from sounding like you are grading someone else’s performance before you understand the team.

It also surfaces the real issue. Sometimes the ball was dropped. Other times, no one ever agreed who was holding it.

When to skip the peer script

Skip this if the issue is harassment, sabotage, retaliation, discrimination, or anything that belongs with HR, legal, compliance, or your manager right away.

Also skip it if your manager has already told you not to direct this person. In that case, escalate the dependency, not the coworker. Say, “I am blocked on X because Y has not landed,” and ask your manager how they want to handle the ownership.

For remote teams, be extra plain. Written tone can turn a normal reset into an ominous message. Avoid “per my last email” energy. Use short context, then talk live if the relationship matters.

For foreign professionals, one US-office norm is useful here: calm directness about work impact is read as professional in many teams. Vague hints may be missed. You do not need to be harsh. You do need to be specific.

If this is part of a bigger communication pattern, you may also want the Slack vs. email decision tree or the guide to resolving conflicts with coworkers.

---

Yes, this whole thing is slightly corporate. You are taking an emotion — “I am mad this did not happen” — and turning it into a tiny project-management artifact.

Do it anyway.

The point is not to make someone feel bad. The point is to keep the work from failing twice.

---