How to manage team tasks comes down to this. Give every task one owner, one date and one finish line, and keep them all in one list that everyone can open. Review that list once a week and look at what is late first. A chat group is good for talking, but it cannot show you what is open, who has it or what is late.
Key takeaways
- A task is only a task when it has one named owner, a date and a clear finish line. "Someone should send the quote" is a wish.
- Tasks lost in a WhatsApp group are rarely forgotten out of laziness. They are buried under the next ninety messages.
- You need one list, not one list per person. The test is simple: can you answer "what is late, and who has it?" in under a minute?
- A weekly review of the list, with overdue items first, catches most slips before a customer does.
- A free tool is enough for a team of five. Pay when you need more people, not before.
Why do tasks get lost in the WhatsApp group?
Here is a scene from a composite example, the kind of week many Lagos and Abuja offices will recognise. On Monday at 8:10, the operations manager, Ngozi, writes in the team group: "Please send the revised quote to Mr Bello today and confirm delivery for Thursday." Two people react with a thumbs-up. By lunchtime there are 94 new messages about a broken generator, a delivery van and someone's birthday. At 5 pm nobody can say who was meant to send the quote, because three people reacted and none replied.
None of this is anyone's fault. A chat group is built so that the newest message is the most visible one. That is perfect for conversation and poor for work, because work has to stay visible until it is finished.
Chat groups lose tasks in five predictable ways:
| What goes wrong | Why it happens in a chat | What it costs |
|---|---|---|
| No owner | The message was addressed to "everyone" or "team" | Everyone assumes someone else has it |
| No date | "Soon", "this week" or "ASAP" | Nothing is ever late, so nothing is ever chased |
| Buried | New messages push the request out of sight | The request is only found when the customer calls |
| No status | Nobody can tell started from not started | You ask "any update?" and interrupt people |
| No history | A decision lives in someone's phone | A new hire or a colleague on leave cannot find it |
If you recognise three or more of these, the fix is not a stricter group rule. It is a list that sits outside the chat. We say more about this in outgrowing WhatsApp and Excel.
What does a task need before it counts as a task?
Before something goes on the list, check that it has these five things. If one is missing, the item is a topic, not a task.
| It needs | In plain words | Weak version | Strong version |
|---|---|---|---|
| One owner | One name, not a team | "Sales team to follow up" | "Chinedu follows up with Mrs Okafor" |
| A due date | A day, and a time if it matters | "Soon" | "Thursday 14:00" |
| A finish line | How you will know it is done | "Look into the supplier" | "Three written quotes in the shared folder" |
| A size | Roughly how long it takes | Nothing said | "About 2 hours" |
| A place | Where it lives, and what it serves | A voice note | Under the customer, project or goal it belongs to |
The last row matters most for a growing business. A task that sits under a customer, a project or a goal tells you why it matters, and helps you decide what to drop when the week is full.
One owner is not negotiable. If two people need to do something, make two tasks, or make one task and a sub-task. When two people own a task, neither does.
How to manage team tasks, step by step
This is a routine for a team of three to thirty. You can run it on paper, a spreadsheet or a task app. What matters is that you run it every week.
- Pick one home for tasks. One list, one place. Tell the team that anything not on the list does not exist. This is the hardest step, because it means saying "please put it in the list" when someone sends you a message.
- Capture tasks where they are born. Most tasks start in a meeting, a call or a message. Write them down in that moment with an owner and a date. Do not plan to "collect them later".
- Write the task so a stranger could do it. A task such as "Follow up with the cement supplier" needs the person, the thing and the date: "Call Mr Adeyemi about invoice 0412 and confirm payment date by Friday".
- Size it. Ask for a rough number of hours. If a person has 45 hours of tasks due this week, you have found a problem before it arrived.
- Review weekly, overdue first. On Monday, spend fifteen minutes with the team on three questions: what is late, what is blocked, and what is due this week. Skip what is on track.
- Move blocked tasks, do not nag them. A task that cannot move needs a name next to the obstacle ("waiting on the bank's reply"). That tells you whose help is needed.
- Close the loop. When a task is done, tick it. When it is dropped, say so and why. A list full of tasks nobody will do teaches people to ignore the list.
The review is where the list earns its keep. Without it, the list becomes another place where tasks go to be forgotten.
What should you look at each week?
You do not need a dashboard. You need four numbers, and you can count them by hand if you have to.
| Measure | The question it answers | A warning sign |
|---|---|---|
| Due this week | What is the load? | One person carries most of it |
| Overdue | What slipped? | The same names every week |
| Blocked | What needs my help? | A task blocked for over a week |
| Unassigned | What has no owner? | Anything above zero |
Notice what is missing: hours online, messages sent, or minutes at a desk. Those do not tell you whether the work is moving, and people feel watched when you count them. See who has what, and what is late. That is all the manager needs.



