A customer calls, annoyed. The follow-up they were promised never happened. The owner asks around.
The salesperson thought operations would reach out once the job was scheduled. Operations thought the salesperson would close the loop since they made the promise. The office manager saw the email, assumed one of them had it, and moved on.
Nobody dropped the ball, exactly. There was no ball. Nobody was ever handed it.
What the owner thinks is wrong
“We need to communicate better.” That’s usually the first conclusion, and it leads to more meetings, more group texts, more cc’s. The irony is that more people seeing something can make it less likely that any one of them acts on it. Everyone sees it. Everyone assumes.
What I’d investigate
I’d look for recurring work where several people are involved and nobody is named. That’s where this lives. Some common spots:
- Following up with a customer after a sale or after a job
- Ordering materials or supplies that several people use
- Chasing an unpaid invoice
- Updating a shared document or schedule
- Telling the customer about a delay
- Closing out a job or project file
For each one, I’d ask three people separately: who’s responsible for this? If I get three different names, or three people saying “well, kind of all of us,” I’ve found the gap.
What’s underneath it
Nothing was assigned incorrectly because nothing was really assigned. People were involved. Involved is not the same as responsible.
Being involved means you touch the work. Being responsible means that if it doesn’t happen, it’s on you, and you know that ahead of time. Most small businesses run on involvement for a long time, because when there are four people, everyone just handles what they see. As the team grows, everyone sees more and handles less, because surely somebody else has it.
What I’d change
For each recurring outcome, one named owner. Not a team. A person.
Everyone else gets a clear role: they help, or they need to be told. That’s it. You don’t need a complicated chart. A simple list works:
- Customer follow-up after sale: owner is the salesperson until the job is scheduled, then operations. Office manager is informed.
- Late-payment follow-up: owner is the office manager. Owner is informed after 30 days.
The handoff point matters as much as the owner. “Sales until scheduled, then operations” tells everyone exactly when the ball moves.
A quick way to test it: send the list around and ask each person to circle the items they think are theirs. If two people circle the same one, you have a disagreement to settle. If nobody circles one, you have a ball nobody is holding. Both answers are useful, and both are much cheaper to find on paper than through a customer who never heard back.
What I’d leave alone
Collaboration. People should still help each other, jump in, cover when someone’s out. Naming an owner doesn’t mean nobody else can touch it. It means somebody makes sure it happens.
The tradeoff
Naming owners surfaces disagreement. Two people might both think it’s theirs, or both think it isn’t. That conversation can be uncomfortable. It’s still better than finding out from an annoyed customer.
It also puts one person on the hook, and some people don’t love that at first. That’s why the owner has to back it up with authority. If someone owns the outcome, they need to be allowed to make the decisions it takes to get there.
The pattern
When something falls through the cracks, look at whether there was a crack. Usually there was. It was the space between “I was involved” and “I was responsible.”
So here’s a small exercise. List five things that happen every week or every month in your business. Next to each one, write the name of the person responsible. Then ask that person if they agree. If you hesitated on any of them, that’s where the next dropped ball is coming from.
If the list gets complicated, that’s a good conversation for a Systems Fit Call.
