How to Manage Tasks in a Small Business

Small businesses do not usually decide to introduce task management. They arrive at it after a specific bad week — a customer chased something nobody had started, a routine that had run for two years quietly stopped, or a person left and took a process with them.

The signals are consistent enough to be worth listing, because recognising them early is cheaper than recognising them late:

• Staff ask the owner what to do next. Not because they are unwilling, but because the owner is the only place the answer exists.
• The same question is answered repeatedly. "Which supplier?" and "has this been approved?" get asked every time, because the answer lives in a conversation rather than on the job.
• Nobody can say what is outstanding without opening three chat threads and asking two people.
• Work stops when one person is away. Their absence is not an inconvenience — it is an outage.
• The owner is working evenings on things that are not the business, but the coordination of the business.

One owner, named

Work addressed to a group belongs to nobody. That is not a comment on anyone’s character — it is arithmetic. If four people could do it and none was asked, the expected number who start it is somewhere between zero and two, and both outcomes are bad.

The exception is when you genuinely do not know who should take it. Then the answer is not to broadcast it but to raise it for a team in a way somebody can claim exclusively — see department task management.

A description someone else could act on

The test is simple: could a person who was not in the conversation start this within a minute of reading it? "Sort out the Sharma order" fails. "Refund the duplicate charge on order 4471 and email the customer confirming it" passes.

A date, where the date matters

A due date on everything is the same as a due date on nothing. Use dates where something genuinely depends on the timing, and use priority for relative urgency. They answer different questions.

A record of what happened

This is the one small businesses skip and the one they miss most. Three weeks later, a customer disputes a date, a staff member disputes an instruction, or you simply want to know why something took nine days. Without a record, all three become arguments about memory.

1. 01Departments. Even three or four. They decide who is eligible for which work and how reports group, and creating them afterwards means reassigning everyone.
2. 02Roles. Built from the permissions people actually need. Someone who needs to read reports should get that permission, not an administrator account.
3. 03People. Added individually or imported from a spreadsheet in one pass.
4. 04One task form. For your most common request type. This is the step most small businesses skip and most regret — see custom task forms.
5. 05The routine. Turn the work that repeats into recurring schedules before anyone re-types it manually again.
6. 06Notifications last. Switch them on once there is something worth being notified about, so the first messages people get are useful rather than noise.

For a team of twenty to thirty this is an afternoon, not a project. Treating it as a project — with a steering group, a training day and a phased plan — is itself a risk, because none of that survives a busy week.

Do not migrate anything

The instinct is to move existing work in so everything is in one place. Resist it. A migration is a day of data entry followed by two live systems, and the old one always wins because it already contains everything. Let in-flight work finish where it started and raise only new work in the new system. Within about three weeks the old one is empty by attrition.

Keep WhatsApp, move the record

If your team lives on WhatsApp — and in most small businesses they do — do not ask them to leave. Send task notifications there instead, so the alert arrives where they already read while the state of the work lives on the task. Task management with WhatsApp covers which events are worth sending.

One rule, announced once

"From Monday, if you want someone to do something, raise it as a task." That one sentence works better than a training session, because everything else can be learned by doing.

The owner has to go first

The fastest way to kill this is for the owner to keep assigning work by message. Staff will correctly conclude the system is optional. The fastest way to secure it is to reply to a verbal request twice with "raise it as a task and I will pick it up".

In most small businesses the owner is the routing table. Every incoming request passes through them because they are the only person who knows who is free, who has done it before and what the customer was promised. That works, and it caps the business at whatever one person’s attention can process.

Two changes remove most of it:

• Route work to a team, not a person. A task raised for a department is claimed by whoever is free. The owner no longer has to know who that is.
• Make the state readable. When status, progress and blocked reasons are on the task, checking in becomes reading rather than interrupting — and the reason to route everything through one person disappears.

The second is what makes delegation feel safe enough to keep doing. Task delegation goes into what a properly delegated piece of work actually contains.

1. 01Week one — raise everything. All new requests become tasks. Nothing else changes. Expect the first tasks to be badly written; that corrects itself.
2. 02Week two — notifications on. Creation and handover alerts to the channel the team reads. This is usually when adoption becomes self-sustaining.
3. 03Week three — forms and schedules. By now you know which questions keep being asked in comments and which requests repeat. Turn the first into fields and the second into schedules.
4. 04Week four — look at the numbers. Overdue work and workload first. Do not draw conclusions about people from four weeks of data; do draw conclusions about queues.