Every small business has a few jobs that "everyone knows about." The invoice that needs a nudge on day 10. The quote that should get a second email. The customer who asked a question on Friday and is still waiting on Tuesday.
Ask who owns each one and you get a pause. Then a shrug. Then "I think Sam usually does that."
That pause is the whole problem.
Why it keeps happening
A job without an owner does not fail loudly. It just happens when the person who remembers it is in that day, has time, and is not buried in something louder. Some weeks it gets done three times. Some weeks it gets done zero times. Nobody is lazy. The job simply belongs to nobody, so nobody can be late on it.
This is why a new tool rarely fixes it. A reminder app sends a reminder to whom? If the answer is "the team," the reminder lands in a channel everyone sees and nobody answers.
What to write down instead
For each recurring job, put four short lines on one page:
- What starts it. A signed quote, a missed call, an invoice that is 10 days old.
- Who does it. One name. Not a team, not "whoever is free."
- What done looks like. A sent email is not done. A reply received, or a date logged for the next try, is done.
- What happens if the person is out. A named backup, not a hope.
That is it. No software needed to start. Ten minutes per job, and most businesses have fewer than ten of these jobs that really matter.
The part people skip
Line three is where most plans fall apart. "Sent" feels like done, so the job gets ticked off and the customer is still waiting. Writing down what done actually means gives you something you can check on Friday afternoon in under a minute: open the list, see which ones have no result, and ask the one named person.
Why this comes before any automation
If you automate a job that has no owner, you get a faster version of the same gap. The automation runs, nobody watches it, and when it hits an odd case it stops quietly. If the job has a named owner and a clear finish line, an automation has something to hang on to. It knows who to tell when it is stuck.
So the order is simple. Name the owner. Define done. Then decide what, if anything, should run on its own.
A small test for this week
Pick the one job that annoys you most. The one you keep saying "we should really stay on top of that." Write the four lines. Put one name next to it. Check it on Friday.
If you can't name the person, you just found the real problem, and it was never the tool.
If you have a recurring job in your business that keeps slipping, tell us in the comments what it is and who you think owns it right now. We build and run AI systems for ops teams, and some of our work is at octyn.co/casestudies.
Top comments (0)