The Ball Was Never Dropped.
"The team keeps dropping the ball."
If you've said some version of that in conversation, you're not alone.
It's one of the most common things a business owner or leader brings to that table, and it usually comes with real frustration attached. Same person missing the same step. Same tasks falling through. Same apologies.
From where you're sitting, the pattern could look personal.
But an audit tends to change the picture.
An audit doesn't ask who dropped the ball. It asks where the ball was supposed to be caught, and by what. And there are quite a few times, not always, but quite a few, the answer isn't a person; it's a gap.
Do These Sound Familiar?
Take work that's genuinely finished, but nobody flags it as finished to the person who needs to invoice it.
⏰ Three weeks pass before anyone notices.
From where you're standing, that reads as forgetfulness - somebody just didn't follow through.
On the audit floor, it usually reveals something narrower: "done" was never defined anywhere except in one person's head. There was no shared trigger - no tracker update, no tick-box, no message - telling the next person in the chain that the work had crossed the finish line. The task wasn't dropped. It was never handed over in the first place, and therefore no where to drop it from.
How about …
the one you've probably lived through more than once: everyone on the team can tell you, individually, exactly what they're supposed to be doing.
Ask any one of them and they'll say it back to you clearly. 📋
And yet, the dial still doesn't move - but wwwhhhyyyy?!?!?! It’s simply because each person is quietly assuming somebody else already has it in hand. Nobody's lying. Nobody's (purposely) being lazy. Everybody genuinely believes the ball is in hand.
BUT, it really sits, not in hand, until it becomes urgent and that one person (usually the most conscientious or the most responsible one) scrambles to pick it up at the last minute and absorbs the cost of a gap they didn't create. That's not a motivation problem. It's a structure where "everyone knows" has become the reality for "someone owns."
And there's the quieter version:
a process that lives entirely in someone's head, shared verbally whenever someone asks.
It works, until they are on leave or leave, and suddenly the balls are everywhere but in the air. That could read as a staffing problem, but it's really an undocumented single point of failure. A process nobody wrote down, because it never needed to be, until it did.
Now, this is not an argument that people are blameless in every operational failure.
People make mistakes, miss things, and underperform. But the pattern serious enough to be worth your frustration is rarely one person failing repeatedly. It is the symptoms of invisibility (no shared definition of ‘ done’, so nobody flagged it done), diffusion (no clear ownership where everyone knows, nobody owns), and undocumented knowledge (important things live in someone’s head).
If you don’t address the structure and only blame the person, nothing will get resolved and whoever holds that role next will drop the same ball, because the ball was never secured.
And plain talk; nobody enjoys being quietly blamed for a gap they didn't create, that is a quick way to demotivating a conscientious or responsible team member.
Operational reality cuts both ways: assuming something is "obvious" that was never written down, and a team member working inside undefined boundaries, doing their best with instructions that exist only in someone else's head.
An good audit will hold both truths at once. It doesn't let the system off the hook by blaming the people in it and vice versa. A honest audit puts responsibility where the balanced evidence points to.
A quick test: is this the system, or is it the person?
Before you reach for a difficult conversation, it's worth running the situation through a short check. A genuine systems gap and a genuine performance issue tend to look identical from the outside - same missed deadline, same dropped ball.
But, they answer these questions very differently.
❓Has this happened with more than one person in this role, not just this one?
✅ Yes? that's a structural signature, not a personal one.
❓Could you, right now, point to where the responsibility for this task is written down?
❌ No? the gap is in the documentation, not the person.
❓If this person left tomorrow, would the next person walk into the same failure?
✅ Yes? you're not managing a person problem. You're inheriting a system failure or gap.
❓Has this same individual repeatedly underperformed on a task that is clearly defined, documented, and owned by them alone with reasonable support already in place?
✅ Yes, that's a different, and likely difficult, conversation, and it's most likely time to have it.
That is a quick DIY way to make sure you're solving the actual problem, instead of holding one person accountable or responsible for a structure or workflow that makes the whole team struggle.
And an audit takes the presenting complaint, "the team keeps dropping the ball," "communication is broken", and tests it against what's on paper: the workflows, the handoffs, the definitions everyone assumes exist but nobody has actually written down, and what’s actually happening.
We Converse and Observe: where assumptions get tested against reality, before anything gets adjusted.
Your audit is the beginning of your next phase of clarity and growth. And like every motivator for growth, you have to find your weak spots and unearth where the documented system or process and the lived one, diverge.
Without this, you’d probably build a fix on top of an (incorrect) assumption and end up with a beautifully documented process nobody actually follows. And 18 months from now, finding the exact same problem wearing a different name.
✶
Before your team gets concerned, an audit isn’t about tightening control over them. It's about protecting everyone’s capacity to think clearly, instead of firefighting the same dropped ball, week after week, in a dozen different disguises.
Every unresolved systems gap becomes something someone has to hold in their head, because nothing else is holding it.
It’s not sustainable, and it is pricey! it's hours, attention, and decision-making capacity, spent compensating and firefighting.
Fixing the system isn't a soft option.
It's how you get your time, attention and bandwidth back.
take care of you,
ZB.
Wi,Mi is based in Trinidad and Tobago and works with SMEs across the Caribbean and internationally. If your business is ready for that work, wherever you are, the conversation starts via 📋contact form, 📧 email hello@whatismustis.comor 📆 book a chat one time.
