Task ownership in a small business: a practical guide

In a small business, almost everyone is willing. Jobs still go missing. The reason is rarely effort — it's that too much work belongs to everyone, which in practice means it belongs to no one.

This guide sets out a simple approach to ownership that works in teams of five to fifty: what it means, the one rule that does most of the work, and the exceptions that matter in real life.

Why shared ownership fails

"Can someone sort that out?" feels efficient. Everyone hears it, so surely someone will do it. In practice, each person assumes another has picked it up, and the job waits.

The same thing happens with jobs given to a department ("the office will deal with it"), to two people at once, or to whoever "usually does that". Shared responsibility spreads thin. Nobody feels it's theirs to chase, so nobody does.

It isn't a character flaw. It's what happens to any group when a job has no single home.

The one-owner rule

The rule is simple: every job has one owner and one date.

One owner means one named person, not a team. They don't have to do all the work themselves, but they're the one who makes sure it gets done, or comes back and says it can't be.
One date means a real day — the deadline, or at least the day someone will next look at it.

If you can't say who and when, you don't yet have a task. You have an idea, and ideas are fine — but they belong somewhere else until someone takes them on.

What an owner is (and isn't)

Ownership gets resisted when people think it means doing everything alone, or being blamed when things go wrong. Neither is true.

An owner:

makes sure the job moves, and knows its status;
asks for help, delegates parts or brings in others;
raises their hand early if the date won't be met;
hands it back if it isn't really theirs.

An owner is not the only person allowed to work on it, and not the person who takes the blame for a shared problem. Helpers are fine. What matters is that one person is holding the thread.

Dates are review points, not just deadlines

Some jobs have a hard deadline. Many don't — "call the supplier about the delay", "look into new vans". Without a date, those jobs never become overdue, so they never get noticed.

Give them a date anyway: the day you'll next look at it. If nothing has happened by then, the owner either does it, sets a new date on purpose, or drops it. Any of those is better than letting it drift.

Handing work back without blame

Ownership only works if it can be declined. If someone is given a job they can't do — wrong skills, no time, not really their area — they need an easy way to say so and hand it back, without it feeling like failure.

Teams where handing back is awkward don't end up with fewer mistakes. They end up with jobs that were silently accepted and quietly not done.

A good rule of thumb: handing back is fine; handing back on the due date isn't.

Visible, not verbal

The biggest single improvement most teams can make is to assign work where everyone can see it, not just in conversation.

A word in passing, a forwarded email with no message, a quick "can you…?" at the end of a call — each one feels like assigning, but none leaves a trace. A week later, both people remember it differently.

Talk all you like for context. But the job itself should be written down in the shared list, with the owner's name and the date. If it isn't on the list with their name on it, it hasn't been assigned.

Where formal methods fit

You may have come across RACI charts, which split each task into who's Responsible, Accountable, Consulted and Informed. They can be useful on large projects with many people involved.

For most small businesses, the full chart is more than you need. "One owner, plus anyone helping" covers almost every day-to-day job. If a project is big enough that people regularly argue about who decides what, that's the moment a more formal chart might be worth the effort.

Starting this week

Write down the open jobs — the ones in your head, inboxes and chats.
Give each one a single owner. If you hesitate, ask who already has the most context: the person who spoke to the customer, quoted the job or did it last time.
Give each one a date — a deadline or a review day.
Agree one rule with the team: nothing goes on the list without a name and a date.
Make handing back easy. Say out loud that it's fine, and mean it.

For the first couple of weeks it will feel like extra effort. Then the chasing drops, because people can see what's theirs.

Going deeper

How to stop chasing your team for updates — making progress visible instead of asking for it.
How to assign tasks clearly: what every task needs — the four things to hand over with every job.
How to stop being the bottleneck in your own business — getting out of the middle of every decision.
Task management for small teams: a practical system — one list, one owner, one date and a weekly look.
Why work falls through the cracks — and how to spot it early — the warning signs that a job is slipping.