When a capable team keeps dropping balls, the problem is almost never laziness or incompetence. Dropped balls happen because of five systemic failures: unclear ownership, uncommitted agreements, broken handoffs, invisible progress, and unrealistic capacity. Fix these system issues and the same team that frustrated you will start executing reliably. Keep blaming individuals, and you will keep having the same problems with different people.
I see this pattern constantly in businesses between £3M and £20M. A founder looks at a team of smart, hardworking people and wonders: “Why can’t they just follow through?” So they try harder. They send more reminders. They attend more meetings. Eventually, they start doing things themselves because it feels like the only way to guarantee results.
Meanwhile, the actual root causes go unaddressed. The balls keep dropping. The founder’s workload keeps growing. And the team’s initiative keeps shrinking because they have learned to wait for instructions rather than take ownership.
This article is part of the Building Accountability Without Micromanagement series.
The Five Root Causes Behind Every Dropped Ball
Before you can fix execution problems, you need to understand what is actually causing them. In over twenty years of working inside growing businesses, I have found that dropped balls trace back to five root causes. Most companies have at least three of these operating simultaneously.
Root Cause 1: Unclear Ownership
When multiple people are involved in something, it is remarkably easy for everyone to assume someone else has it covered. Without explicit ownership, accountability diffuses into nothing.
Gallup’s 2025 engagement research found that only 47% of employees strongly agree they know what is expected of them at work. That means more than half of the typical workforce is operating without clear understanding of their responsibilities. In a team of 20, that translates to roughly 10 people who are not entirely sure what they should be prioritising.
You will recognise the symptoms immediately. Tasks get assigned to “the team” rather than to a specific individual. When something drops, nobody can point to who should have caught it. Conversations include phrases like “I thought you were handling that” or “I assumed marketing was taking care of it.”
The fix: Every commitment needs a single owner. One person who is accountable for making sure it happens. That person can delegate work to others, but the accountability stays with them. In meetings, never leave an action item without a named owner and a specific deadline.
Root Cause 2: Uncommitted Agreements
There is a critical difference between hearing a request and genuinely committing to deliver on it. Many workplace “agreements” are actually one-sided instructions that the recipient never truly accepted.
Think about how tasks typically get assigned. A manager mentions something needs doing during a meeting. Everyone nods. The manager assumes it is now on someone’s list. Meanwhile, the person who nodded may have heard the request but never assessed whether they have the capacity, clarity, or resources to actually deliver.
Genuine commitment requires three elements: the person understands what is being asked, they believe the timeline is achievable, and they explicitly agree to deliver. Without all three, you have a hope, not a commitment.
Pro Tip
After assigning a task, ask the recipient to confirm their understanding in their own words: “Can you tell me what you are taking away from this and when you will have it done?” This single question catches more misunderstandings than any project management tool.
Root Cause 3: Broken Handoffs
Work rarely stays with one person from start to finish. It moves between individuals, teams, and departments. Every handoff point is a potential failure point, and most organisations treat handoffs as informal afterthoughts rather than the critical process junctions they actually are.
Consider what happens when marketing generates a lead and passes it to sales. Or when a project manager hands deliverables to a client success team. Or when a developer completes a feature and passes it to quality assurance. At each transition, information gets lost, context disappears, and ownership becomes ambiguous.
The fix: Define explicit handoff protocols for your recurring workflows. Each handoff should answer three questions: What exactly is being transferred? Who is the new owner? What does “complete” look like from this point forward? Document these transitions and treat them as formal accountability transfer points.
Root Cause 4: Invisible Progress
When nobody can see the status of work in progress, problems stay hidden until deadlines arrive and things are not done. By that point, the opportunity to course correct has passed.
Most growing businesses rely on informal communication to track progress. The founder checks in with people individually, sends Slack messages asking for updates, or waits until the weekly meeting to find out what is happening. This approach works when you have five people. It falls apart entirely with fifteen or twenty.
Research consistently shows that transparency drives accountability more effectively than oversight. When people know that their progress is visible to peers and leadership, they naturally self manage. The visibility itself creates the accountability, removing the need for you to chase updates.
Build the right visibility systems: KPIs That Actually Drive Performance
Root Cause 5: Unrealistic Capacity
Sometimes balls drop for the simplest reason of all: people have more on their plate than they can realistically deliver. Yet in many organisations, admitting you are overloaded feels like admitting weakness.
This problem is especially acute in growing businesses where the work is expanding faster than the team. People who were hired when the company was smaller are now carrying responsibilities that have doubled or tripled. Nobody formally reassessed their capacity. Everyone just kept adding tasks.
The fix: Create a culture where capacity conversations are normal and expected. When assigning new work, ask: “What is your current load, and what would need to move to accommodate this?” Give people explicit permission to push back on unrealistic timelines without fear of being seen as uncommitted.
A Self Assessment: Where Are Your Balls Dropping?
Before jumping to solutions, it helps to diagnose which root causes are most active in your organisation. Rate each area on a simple three point scale: Strong (this works consistently), Moderate (sometimes works, sometimes does not), or Weak (clearly a problem).
- Ownership clarity: Does every task and project have a single named owner?
- Commitment quality: Do people explicitly commit to deliverables, or are tasks simply assigned?
- Handoff reliability: When work moves between people, is the transfer clean and documented?
- Progress visibility: Can you see the status of key work without asking someone directly?
- Capacity honesty: Do people have realistic workloads, and can they push back when overloaded?
Focus your improvement efforts on your lowest scoring areas first. Trying to fix everything simultaneously spreads your attention too thin and rarely produces lasting change.
The Systematic Fix: Building Reliable Execution
Once you know where the breakdowns are occurring, the fixes follow a logical sequence. Here is how to address each root cause practically.
Fix 1: Establish an Ownership Protocol
Change the language your organisation uses around task assignment. Instead of saying “Team, please handle this,” shift to “Sarah, can you own making sure this happens by Friday?” After every meeting, confirm: “To recap, Sarah owns the client proposal by Friday, and James owns the supplier outreach by Wednesday. Correct?”
For complex projects, create a simple accountability map that identifies who owns each major deliverable. This does not need to be elaborate. A shared document listing deliverables, owners, and deadlines is sufficient. The act of writing it down transforms vague expectations into specific commitments.
Fix 2: Replace Assumptions with Genuine Commitments
Introduce what I call the Commitment Confirmation practice. When someone takes on a task, they confirm three things: what they will deliver, when they will deliver it, and what they need from others to make it happen. This takes thirty seconds and prevents hours of wasted effort later.
If someone cannot commit to a deadline, that is valuable information. It is far better to know upfront that a Thursday delivery is unrealistic than to discover it on Thursday afternoon. Encourage honest pushback on timelines. A commitment you can trust is infinitely more useful than a promise nobody believes.
Fix 3: Formalise Your Handoff Points
Map your most common workflows and identify every point where work transfers between people or teams. For each handoff, define what a complete transfer looks like. What information must accompany the work? Who confirms receipt? What happens if the receiving party identifies gaps?
One manufacturing client I worked with discovered that 60% of their quality issues traced back to a single handoff between their design team and production floor. The design specifications were technically complete, but production consistently misinterpreted certain elements. Adding a 15 minute handoff review where both teams confirmed understanding eliminated the majority of those errors within a month.
Fix 4: Make Progress Visible
Choose a system that makes work status visible without requiring you to ask. This could be a project management platform like Asana or Monday, a shared Kanban board, or even a whiteboard in the office. The tool matters less than the discipline of keeping it current.
The critical rule: if it is not in the system, it does not exist. Every commitment should be captured somewhere that both the owner and their stakeholders can see. When progress is visible, people self manage. When it is invisible, you become the tracking system, and that does not scale.
Create the right check-in rhythm: The Meeting Rhythm That Keeps Teams Aligned
Fix 5: Normalise Capacity Conversations
Build capacity check-ins into your regular management rhythm. During weekly reviews, ask each team member: “What is at risk this week, and where do you need help?” Normalise the answer “I am overloaded” by responding with problem solving rather than disappointment.
Create a simple escalation language that removes the stigma. For example: green means on track, amber means at risk and needs attention, red means will miss the deadline without intervention. When people can signal problems early using a standardised system, you catch issues while there is still time to fix them.
When the Problem Truly Is an Individual
Sometimes, after fixing the systems, you still have individuals who consistently drop commitments. At that point, it becomes a performance conversation rather than a systems conversation.
Here is how to tell the difference. If your systems work for most of the team but one person consistently falls short despite clear expectations, adequate resources, and reasonable capacity, then you have an individual performance issue. The key indicator is whether the systems support everyone else successfully.
When that is the case, use the Accountability Conversation Framework from the hub page. State the observable facts. Describe the business impact. Ask for their perspective. Agree on the forward action. Document it and follow up.
The progression should be coaching first, then formal feedback with clear expectations, then consequences if the pattern continues. Most people respond to the coaching stage when the conversation is direct and supportive rather than punitive. Those who do not respond after repeated coaching and clear expectations are telling you something important about their fit for your organisation.
Key Takeaway
Your team keeps dropping balls because of system failures, not people failures. Fix ownership clarity, commitment quality, handoff protocols, progress visibility, and capacity management, and the same team that frustrated you will start executing reliably. The difference between chaos and consistency is not better people. It is better systems around the people you already have.
Measuring Whether Your Fixes Are Working
You will know your execution systems are improving when you see these shifts:
- Leading indicators: Commitments are being captured systematically. Early warnings surface before deadlines, not after. Capacity conversations happen proactively.
- Lagging indicators: Fewer missed deadlines. Fewer surprises about incomplete work. Less time spent personally following up. Better client and stakeholder outcomes.
- Red flags to watch for: The same types of drops recurring. Systems exist but people are not using them. Workarounds developing around the systems rather than through them.
Track these indicators weekly for the first 90 days. After that, the systems should be generating enough momentum that monthly reviews are sufficient.
Continue Reading