Most small teams do not need a project tool with dozens of fields, swimlanes and sprint reports. They need one place where the work lives, a short list everyone can read in under a minute, and a habit of looking at it once a week. This post covers how to set that up for a team of two to ten people who run their own web apps and sites.
What a team of two to ten actually needs
A team this size needs four things from a task tracker:
- A list of tasks that anyone on the team can add to and close.
- A way to see who is doing what, without a meeting.
- Somewhere to put the reason a task exists, such as a client request or an error you noticed on a monitor.
- A record of what got done, so you can answer "did we ship that?" without digging through chat.
You do not need time tracking for every hour, custom workflows per project, or a reporting dashboard nobody opens. Each extra field adds a small cost every time someone creates a task, and those costs add up fast when the whole team is five people.
AperioFlow is built for this size. You can plan work, catch errors, watch uptime and tell your customers when something breaks, all in one place. It is run from the UK and hosted in France. The Team plan is 29 pounds a month flat for up to 10 people, as on the pricing page, so you are not paying per seat as the team grows to the limit. The free plan includes 10 monitors if you want to try the monitoring side first.
Keep a short list: now, next, done
The simplest working setup is three columns: now, next and done. Nothing else is required.
- Now holds at most three or four tasks per person. These are the things being worked on this week. If a person has more than that in progress, something is probably half-finished.
- Next holds the things you have agreed to do but not started. Keep this list ordered. The top item is what the next person to free up should pick up.
- Done is a record. Do not spend time tidying it. Its job is to show what happened.
Write each task as a short sentence that starts with a verb. "Fix the contact form on the Parkside site" is useful. "Website" is not. If a task needs more than a sentence of context, put the detail in the task description and keep the title short enough to read in a list.
The main rule is that a task has one owner. Shared tasks tend to sit untouched because everyone assumes someone else has it. If two people really need to work on something, split it into two tasks.
Weekly planning in 20 minutes
A weekly planning session keeps the short list honest. Set a fixed time, for example Monday at 9:30, and keep it to 20 minutes. Use a timer if it helps.
Work through these steps in order:
- Move everything from done that is not needed for the record to an archive or leave it alone. Do not reopen it.
- Check each person's now column. If a task has not moved in two weeks, ask whether it is still needed. If yes, break it down. If no, delete it.
- Look at the next column. Move the top items into now, up to each person's limit.
- Check for anything new from clients or from your monitors since the last session. Add a task for each real problem. Skip anything that is only noise.
- Say out loud what is most likely to slip this week. Note it, and move on.
The session works best when it is short and predictable. If it regularly runs to an hour, the list is probably too long, and the fix is to delete tasks, not to plan longer.
Link errors and incidents to tasks
Most of the work for a small team comes from things breaking. A monitor shows a site down, a backup job fails silently, or a client emails about an error they saw. Each of these should become a task, so the fix has an owner and a record.
A practical pattern looks like this:
- When an alert arrives, create a task straight away. Put the time, the page or job affected, and the first thing you saw in the title or description.
- Paste the link to the error or the monitor page into the task. That way the person picking it up does not have to search for the evidence.
- When the fix goes out, write one line in the task about what caused the problem and what changed. This is the most useful sentence in the whole record, because it is what you will look for the next time the same thing happens.
- If customers were affected, post an update on your status page and note in the task that you did so.
For cron jobs and backups, a heartbeat monitor helps here. The job pings the monitor when it finishes. If the ping stops arriving, you get an alert, and that alert becomes the task. Without a heartbeat, a backup that stopped running last month can stay unnoticed until you need it.
Alert emails only go to people in your organisation, so the person who receives the alert is the person who creates the task. Agree in planning who checks alerts on which days, so nothing waits on someone who thinks it belongs to someone else.
Avoid features you will not use
The tools that fail small teams are usually the ones that offer everything. Before you add a feature, ask whether a specific person will use it in the next month. If the answer is no, leave it switched off.
Some habits help:
- Start with the smallest set of statuses and fields that works. Add one only after the team has run into a real problem it would have solved.
- Do not build a custom process for each client. One list with clear labels is easier to read than five slightly different ones.
- Keep notifications to the minimum. Too many messages teach people to ignore them, including the important ones.
- Review your setup every few months. Remove anything nobody has touched.
You can always download your data, so starting small does not lock you in. If you outgrow the setup later, you can take your records with you.
Tweed Tyne runs its own work on AperioFlow, and the same approach applies there: a short list, a weekly plan, and tasks created from the alerts that matter. It is not a complicated system, and it does not need to be.
If you want to try this with your own team, you can plan your work free on AperioFlow at https://app.aperioflow.co.uk/#/signup. Start with the short list, run one planning session, and see whether it fits how you work before you add anything else.