Article

Where small teams lose hours every week, and how to find yours

The common places a small team's week leaks away, a simple way to measure your own, and how to decide which leak to fix first.

By Josh Pincus · Published · 5 min read

Ask the owner of a small business where the week goes and you usually get a shrug and a laugh. Everyone is busy. Everything gets done, mostly. But when you sit down with the people doing the work and trace a normal week, the same patterns show up again and again: small jobs, each a few minutes, repeated so often that together they take a real share of the week.

This article covers where those hours tend to hide, how to measure your own without a stopwatch culture, and how to choose what to fix first. We have not included industry averages, because the honest answer is that it varies enormously. What does not vary is the method for finding out.

Why small teams lose more than they think

Large companies have operations teams whose job is to notice waste. Small teams do not. The people who would notice are the same people doing the work, and they are too busy to step back.

There is also a measurement problem. Most lost time comes in pieces too small to register. Nobody feels the four minutes it takes to copy a booking into a spreadsheet. They might feel it if it took an hour once a week. It probably does, spread across forty copies.

Finally, the losses are spread across people. The owner loses some time to reports, the manager to scheduling, the assistant to chasing. No single person's week looks broken, so nobody adds it up.

The seven usual leaks

These are the places we find lost hours most often. Your business will have its own variations, but most teams recognise at least four.

1. Copying between systems

Information arrives in one place and needs to be in another. An inquiry in an email that belongs in a CRM. A booking confirmed by text that needs to be in the calendar. An order that has to be keyed into accounting software. Each copy is quick; the volume is what hurts.

2. Replying to the same questions

Hours, prices, policies, availability, where is my order. Most businesses answer a short list of questions dozens of times a week, often looking up the same details each time.

3. Chasing

Chasing payments, chasing approvals, chasing information from customers, chasing colleagues for an update. Chasing is especially costly because it is unpleasant, so it gets delayed, which makes the next round harder.

4. Building reports

The weekly numbers, the client update, the partner report. Pulling data from several places, cleaning it and arranging it takes longer than reading it, every single time.

5. Rescheduling

Any business with appointments, shifts, lineups or deliveries spends a surprising amount of time moving things around. One change can mean several messages to several people.

6. Handoffs

When work passes between people, the receiver rebuilds context by reading threads and asking questions. Promises made in one conversation get lost before the next.

7. Checking

Comparing one system against another to see if they agree. Stock against listings. Payments against invoices. Schedules against calendars. Checking is invisible until something does not match.

How to measure your own week

You do not need time-tracking software or a consultant. You need one week of honest notes.

Keep a simple log

Ask each person on the team to keep a running list for one ordinary week. Not every task, only the repeated ones. Each entry needs three things:

  • What the job was, in a few words.
  • Roughly how long it took.
  • Which systems or channels it involved.

Tell people this is about the work, not about them. The goal is to find jobs a system could do, not to judge anyone's pace.

Add it up by job, not by person

At the end of the week, group the entries by job type, using the seven leaks above as a starting point. Add up the time for each. This is the moment most owners are surprised, because jobs that felt small for each person turn out to be large in total.

Use examples, not precision

Your numbers will be rough, and that is fine. If one job comes out at roughly an hour a day across the team and another at an hour a week, you know which to look at first. Precision matters later, when you want to measure whether a fix worked.

How to pick the first leak to fix

Once you have the list, score each job on four questions:

QuestionWhy it matters
How much time does it take in total?The obvious one. Bigger is better to start with.
How many systems does it touch?Jobs between systems are the ones products leave behind.
What breaks when it slips?A late reply can lose a sale; a late report rarely does.
Can the rules be written down?If you can explain it to a new hire, it can be automated.

The job that scores well on all four is your first project. Often it is not the most interesting one. Reminders, replies and reports are rarely exciting, but they are the most reliable wins.

What fixing it looks like

There are three broad ways to fix a leak, and it is worth trying them in order:

  1. Stop doing it. Some repeated work exists because of a habit nobody questioned. If a report is never read, the cheapest fix is to stop building it.
  2. Use what you have. Many products already include a setting or simple automation for the job. Check before building anything.
  3. Build the connection. If the job sits between several systems, involves reading and writing messages and grows with the business, a custom platform that runs it end to end is usually the lasting fix. What an AI second shift actually does overnight shows what that looks like day to day.

Whichever route you take, measure the same job again a month later using the same rough log. That before and after is what tells you whether to fix the next leak the same way.

A worked example, in outline

Imagine a small venue team that runs this exercise. Their log might show that confirming performers, answering guest questions and building the weekly sales picture are the three biggest repeated jobs, each spread across two or three people. Scheduling touches a spreadsheet, email and a group chat. Guest questions arrive by phone, email and direct message. The weekly numbers come from ticketing, the bar and a spreadsheet.

Scored against the four questions, scheduling comes out first: it takes the most combined time, touches the most systems and causes the most visible problems when it slips. That becomes the first project, and the other two wait until it is running.

Your list will look different, but the method will land you on a clear first project in the same way.

Start with an outside view

If a week of logging feels like a lot to ask right now, start with something faster. Our free pre-assessment reads your website, asks two short questions about what slows your team down and what you run on, and gives you a score with the leaks that are likely costing you most. It takes about two minutes, and it is a useful way to decide what to log first.

Small teamsOperationsAI assessment