Someone on your team drops the ball.
Again.
The email does not get sent. The client follow-up never happens. The meeting gets scheduled for the wrong time. A file is saved somewhere no one can find it. A task sits untouched because everyone assumed someone else owned it.
And your first thought is probably, “I’ve got a people problem.”
But do you?
I understand the reaction. When the same mistake happens repeatedly, it feels personal. You start questioning someone’s attention, ownership, judgment, or commitment.
Before you address the person, take a look at the process.
Was the expected outcome actually clear? Did they have the information and access they needed? Was there a defined handoff? Is the same problem happening with multiple people? Has it happened before with someone else in the role?
If so, replacing or correcting the person might not fix anything.
You may have a process problem wearing a people-problem costume.
That distinction matters because the solutions are completely different. A broken process needs to be fixed. A performance problem needs to be addressed.
Great leaders learn to diagnose before they prescribe.
The question most leaders ask first is usually the wrong one
When something goes wrong, we tend to ask, “Who dropped the ball?”
That question immediately points the spotlight at a person.
A better question is this
“What made it possible for the ball to be dropped?”
That question points toward the conditions surrounding the failure.
Maybe the task was buried under a mountain of competing priorities. Maybe three people were involved, but no one was clearly accountable. Maybe the instructions lived in a hurried conversation that was never documented. Maybe the person was expected to make a decision but did not have the authority to do so.
This is especially common when task stacking has become the unofficial operating system of the business.
One person is handling email, scheduling, client communication, files, follow-up, internal coordination, and urgent requests all at once. Each individual task may seem manageable. Together, they create fog.
Then a task gets missed, and the person gets blamed for failing inside a system that was never designed to support consistent success.
Unclear responsibilities, inconsistent procedures, missing information, weak communication, and poor coordination can all contribute to work being dropped between people.
The opportunity is real. The impact is real. But the diagnosis has to come first.
1. Look for the process problem before blaming the person
A process problem usually leaves clues.
Ask yourself:
- Is the desired outcome written down in a way a reasonable person could understand?
- Does everyone involved know what “done” looks like?
- Is there one clearly accountable owner?
- Does the person have the necessary information, access, tools, and authority?
- Is there a standard place where the work is tracked?
- Is there a defined handoff from one person to the next?
- Has the same failure happened with multiple people?
- Did the failure occur before with someone else in the same role?
If the answer to several of these questions is no, pause before making it a character judgment.
You may not have an unmotivated employee. You may have an undocumented workflow.
You may not have a careless team member. You may have a communication failure.
You may not have hired the wrong person. You may have handed them a vague responsibility and expected them to create clarity from scratch.
This is where the five levels of communication become useful. Communication can move from simple broadcasting to informing, involving, collaborating, and multiplying. Many teams get stuck at the informing level. Someone sends a message, gives an instruction, or mentions a task in passing, then assumes alignment exists.
But information was not the same as ownership.
A person can hear what needs to happen without understanding:
- Why it matters
- What decisions they can make
- What resources they should use
- When the task is due
- Who needs to know when it is complete
- What to do if something changes
That is not a small communication gap. It is a process weakness.
The solution is not immediately more reminders. The solution is to make the work observable, repeatable, and owned.
2. Separate a communication failure from a performance failure
Communication is not just talking more.
It is creating shared understanding.
A strong process answers the questions people need answered before they begin. It removes unnecessary guessing and prevents work from disappearing into the space between one person and the next.
For example, a weak instruction sounds like this
“Can you take care of the client follow-up?”
A stronger handoff sounds like this:
- Review the client’s last two messages.
- Draft a response using the approved format.
- Confirm the requested meeting window.
- Save the draft in the client folder.
- Send it by the end of the day.
- Let the owner know once it is complete.
- Escalate any request outside the standard scope.
The second version is not micromanagement. It is clarity.
It defines the outcome, the inputs, the timing, the location, and the escalation path.
That kind of clarity protects both the leader and the team member.
The leader no longer has to carry the entire task mentally. The team member no longer has to guess what success looks like. The handoff becomes visible instead of relying on memory.
A useful process should make it easy to answer:
- Who is responsible?
- Who is accountable?
- What information is required?
- What decision rights exist?
- What is the deadline?
- Where does the work live?
- How will completion be confirmed?
- What happens when the normal process breaks?
Better outcomes do not come from telling people to “communicate better” in the abstract. They come from building communication into the way work is performed.
That is the difference between hoping people remember and designing a system that helps them succeed.
3. Address the people problem only after the process is clear
Sometimes you really do have a people problem.
That possibility should not be ignored.
If expectations are clear, the systems work for everyone else, the person has the necessary skills and resources, and the issue continues, then you may actually have a performance or conduct problem.
The sequence matters.
First, make sure the process is workable.
Then, make sure the person understands it.
Then, provide the resources and support required to follow it.
Then, give direct feedback when the standard is not met.
Only after those steps should you make a firm conclusion about the individual.
Here is a practical test:
If you replaced the person tomorrow, would the failure likely happen again?
If the answer is yes, fix the process.
If the answer is no, and the process is clear and consistently followed by others, investigate the individual issue more closely.
That may involve:
- A skills gap
- A training need
- A workload problem
- A lack of attention or follow-through
- Conflicting priorities
- A motivation issue
- A pattern of knowingly ignoring expectations
The goal is not to avoid accountability. The goal is to apply accountability accurately.
Blaming a person for a broken process creates frustration. Avoiding a real performance issue creates resentment among the rest of the team. Good leadership requires the courage to do both things well: repair the system and address the behavior.
A Remote Executive Assistant can be especially valuable here because process ownership becomes someone’s responsibility instead of an invisible expectation spread across an already overloaded team.
That may include:
- Documenting recurring workflows
- Managing inbox and calendar processes
- Creating reliable follow-up systems
- Organizing electronic files
- Tracking open tasks and handoffs
- Confirming next steps after meetings
- Maintaining the information people need to act
This is not about adding another person to the task stack. It is about giving the process a clear owner.
When someone owns the process, fewer details depend on the leader’s memory. Fewer tasks live in scattered conversations. Fewer handoffs happen without confirmation.
The fog starts to lift.
Diagnose before you prescribe
The next time something goes wrong, resist the urge to immediately ask, “Who dropped the ball?”
Start with:
“What made it possible for the ball to be dropped?”
Then investigate honestly.
- Was the expectation clear?
- Was the responsibility assigned to one person?
- Was the handoff defined?
- Was the information available?
- Was the deadline realistic?
- Did the person have the authority to act?
- Is this failure isolated or recurring across the team?
- Would a new person inherit the same confusion?
You might discover you have been trying to fix the wrong problem.
You might also discover that your team is not resistant, careless, or incapable. They may simply be navigating a business where too much knowledge lives in your head, too many tasks are stacked on too few people, and too many processes are implied instead of documented.
So ask yourself:
Where has task stacking replaced clear ownership in my business?
Which recurring failure am I treating as a personality issue?
What expectation have I assumed was obvious but never clearly communicated?
What process needs an owner instead of another reminder?
The right question changes the response. The right response changes the system. The right system gives good people a better chance to do good work.
If you need help bringing order to the administrative processes that keep slipping through the cracks, learn more about what a Dream Support Remote Executive Assistant Can Help With. You do not have to keep carrying every task, handoff, and follow-up in your head.