Small team workflow self-check: a 15-minute checklist
A 15-minute checklist for small teams running on Zalo, Excel and Google Sheets: find where the workflow leaks, score it and pick the first thing to fix.
Written by Phan Lam Duy Khoi
To improve a small team's workflow, pick one repeating task, score it with ten questions in 15 minutes, then fix the point with the highest frequency × steps × risk score first. Often all it takes is one main place for the data and one owner per step, not new software.
How do you know your team's workflow has a problem?
A workflow is how a task moves from start to finish: who does each step, where the information lives, and when it passes to the next person. Small teams rarely write theirs down. It runs on habit, inside Zalo groups and a few Excel files or Google Sheets.
That works while the team and the workload are small. Once orders pick up or someone new joins, these signs start to show:
- Work gets repeated: the same order is typed into Zalo, then Excel, then the delivery book. Every retype is another chance for a typo.
- Nobody is sure who owns the next step: "who is handling this?" appears in the group chat several times a week.
- Data lives in many places: three files with the same name, each updated by a different person, and nobody sure which one is right.
- Mistakes are found late: wrong address, wrong quantity or a missed appointment, and the first person to notice is the customer.
If two or more of these sound familiar, you do not need new software yet. The first step is to see the current workflow clearly, in 15 minutes.
How do you run a 15-minute workflow self-check?
Do not score the whole company at once. Pick one weekly task that feels the messiest and answer the ten questions below. Do it with someone who actually does that task. The person doing it every day usually knows where it sticks better than the owner does.
- Minutes 1–3: write down where the task starts (a customer message, a form, a call) and where it ends (delivered, paid).
- Minutes 4–10: answer the ten questions.
- Minutes 11–15: add up the score, read the table below and circle the three "yes" answers that hurt most.
Pick ONE task that repeats every week (for example: taking orders, handling customer requests, confirming bookings). Answer each question: Yes = 1 point, No = 0. 1. The same information is typed into two or more places (Zalo, Excel, Google Sheets, a notebook…). 2. Sometimes nobody is sure who owns the next step. 3. To find out where something stands, you have to message one specific person. 4. There is one person whose day off slows this task down. 5. Mistakes are usually found when a customer complains or after a deadline has passed. 6. There are several files or Zalo groups for the same task, and nobody is sure which file is the latest. 7. Nothing written down says where this task starts and where it ends. 8. A new hire has to ask several people before they can do this task. 9. Everyone does the same task in a different way. 10. At the end of the week, you cannot quickly answer "how much got done this week, and how much is stuck". Total: ___ / 10
| Score | What it means | What to do |
|---|---|---|
| 0–2 | The workflow is in good shape | Write the current way of working on one page so new people can read it. Check again next quarter. |
| 3–5 | A few leaks | Pick one thing to fix this month, using the scoring in the next section. |
| 6–8 | The workflow is costing the team a lot of effort | Sketch the steps on paper with the people who do them. Fix the highest-priority point first. |
| 9–10 | The task runs mostly on a few people's memory | Stop adding new work to this workflow. Agree on owners and one main place for the data before anything else. |
The score is a quick lens, not a precise measure. It gives the team a shared way to talk about the problem instead of "it just feels messy".
What should you fix first?
After the checklist you will usually have three to five things you want to fix. Do not fix them all at once. Score each one on three factors, 1 to 3 each, and multiply.
- Frequency: 1 is a few times a month, 2 is a few times a week, 3 is every day.
- Number of steps: 1 is one or two steps, 2 is three or four, 3 is five or more or several handoffs.
- Risk of error: 1 means a mistake is easy to fix, 2 means it costs time, 3 means it costs money or a customer.
| What to fix | Frequency | Steps | Risk | Score |
|---|---|---|---|---|
| Copying orders from Zalo into Excel | 3 | 2 | 3 | 18 |
| Month-end revenue report | 1 | 3 | 2 | 6 |
| Asking customers again for their delivery address | 2 | 1 | 2 | 4 |
The highest score is the first thing to fix. Multiplying keeps you from chasing problems that are visible but rare. If two items tie, pick the one you can fix this week without buying a new tool.
What does before and after look like?
The illustrative example below is an eight-person online shop. The task chosen is taking and delivering orders.
| Before | After | |
|---|---|---|
| Where orders arrive | Zalo messages to three sales staff | Still Zalo, but each order goes straight into one shared Google Sheet |
| Where orders are kept | Three separate Excel files, merged at the end of the day | One Google Sheet, one row per order |
| Order status | Asked in the Zalo group | A status column with a dropdown: New, Confirmed, Out for delivery, Done |
| Who owns the next step | Whoever is free | A column with the name of the person owning the current step |
| Catching mistakes | When a customer asks about their order | At the end of each day, filter orders still marked New after 24 hours |
There is no new software in this example. The biggest change is agreeing on one main record and one owner per step. A dropdown in Google Sheets makes everyone record the status the same way, instead of each person typing their own version.
After the change, run the checklist again for the same task in two to four weeks. If the score has not dropped, go back to the people doing the work and ask where they are doing it differently from what was agreed.
What mistakes do teams make when fixing their own workflow?
- Buying software before the workflow is clear. A new tool only helps once you know what each step is and who does it.
- Writing a process without asking the people who do the work. If the document differs from how work really happens, nobody follows it.
- Fixing several things at once. When results improve or get worse, you will not know which change caused it.
- Automating a step that is still messy. Automation only makes a messy step run faster. Before automating, know what success looks like for that step and who handles failures.
When should you get outside help?
This checklist is enough for most small teams to get started on their own. It is worth bringing in someone from outside when:
- The team has fixed things once or twice and the problems keep coming back.
- Everyone sees the bottleneck in a different place and you cannot agree on what to fix first.
- The team uses many tools but still tracks work by hand.
- You are about to invest in a new tool or website without a clear picture of how work runs today.
My Product Workflow Audit is built for these situations. Over 3–5 days, I listen to how the work runs today, find the bottleneck and its cause, and hand back a map of the current workflow, the friction points and risks, priorities ranked by impact, plus quick wins and a direction for what to do next. An audit is not a full design or build project. If it is not the right fit for your problem, I will say so.
Frequently asked questions
Does a team of 5–7 people need a workflow?
Yes, but not a heavy one. Each repeating task needs a start, an end, one owner per step and one main place for the data. That is enough to cut down on repeated questions and duplicated work.
Should we drop Zalo and Excel for project management software?
Not necessarily. Many tasks only need one Google Sheet agreed as the main record, with Zalo used to notify people rather than to store things. Change tools once you know the workflow you want; otherwise the new software just holds the same mess.
How often should we run this checklist?
Once a quarter, or whenever the team changes people, adds a product, or starts seeing the same mistakes again. Keep the last score so you can compare.
When is it worth asking someone outside the team to look?
When the team has tried fixing things and the problems come back, when people disagree about where the bottleneck is, or when you are about to pay for a new tool without a clear picture of the current workflow.
Sources to check
Related articles
- What is Product Operations in a small team?: It is not another layer of process; it is how decisions make it all the way into daily operations.
- The automation finished. Can users verify what happened?: From building Notifly to making workflow status, runs, individual cases and failure recovery understandable.
- Does a café need a website? When it is worth it: Not every café needs a website. Compare a Facebook page, Google Maps and Zalo with a website, plus a checklist of what the page needs if you build one.
- A homestay website for direct bookings and lower OTA fees: What an OTA is, how platform fees work and when guests should book direct. With a comparison table and a booking page checklist for small homestays.