Most small teams are not short of effort. They are short of uninterrupted, well aimed hours. The day fills with messages, meetings, quick questions and small admin tasks, everyone stays busy until the end of it, and yet the work that actually moves the business, the quote that needed finishing, the job that needed planning, the customer problem that needed solving, keeps slipping to tomorrow. That gap between effort and output is rarely a motivation problem. It is usually a small set of repeatable drains, built into how the working day is organised, and most of them sit within the owner’s power to change. This guide names the seven that matter most, shows what each looks like inside a small business, and gives a fix for each that needs no budget and no reorganisation.
In short: the biggest productivity killers
The biggest productivity killers in a small team are structural, not personal: constant interruptions and notifications; too many meetings, run without a decision at the end; unclear priorities that push people to switch tasks all day; work with no single owner; decisions that queue up waiting for the owner; software that creates as much admin as it removes; and tired people working long hours at low quality. Each one is fixable with changes to habits, defaults and expectations rather than spending. The order that works for most teams is to protect focus time first, then fix meetings, then make priorities and ownership explicit, then clear the decision bottleneck.
Busy is not the same as productive
The large workplace studies agree on the shape of the problem. In Asana’s Anatomy of Work Global Index 2023, which surveyed 9,615 knowledge workers across six countries, people spent 58 percent of their day on what Asana calls work about work: coordinating, chasing updates and administering the work rather than doing it. The skilled work they were hired for took 33 percent, and strategy just 9 percent. The same workers estimated that better processes could give them back 4.9 hours a week. Microsoft’s 2023 Work Trend Index, built from a survey of 31,000 people in 31 countries and from Microsoft 365 usage data, found the same imbalance from the other side: the average employee spent 57 percent of their time communicating, in meetings, email and chat, and 43 percent creating.
Those numbers describe big companies, but the drains are not big company property. In a team of six, the owner is often the helpdesk, the meeting, the approval chain and the person everyone interrupts, all at once. The seven killers below are the small business version of the same pattern. None of them is a character flaw in the team. All of them are defaults that nobody has got round to changing.
1. Constant interruptions and notification load
In a small team this looks like a question called across the room every few minutes, a phone face up on every desk, chat messages that everyone treats as urgent, and an email inbox that stays open all day like a second job. Nobody decides to work this way. It is simply what happens when no response times have ever been agreed, so every message arrives with the same implied demand: now.
The cost is measured better than most owners expect. Gloria Mark, Chancellor’s Professor of Informatics at the University of California, Irvine, has tracked attention in real workplaces for two decades. Her team found that the average time people keep their attention on one screen has fallen from two and a half minutes in 2004 to about 47 seconds in recent years. More expensive is what happens after an interruption: people typically spend about ten and a half minutes on a project before switching, and once interrupted, they take about 25 and a half minutes to pick the original project up again, usually working on one or two other things in between. Mark also found that people interrupt themselves about as often as they are interrupted by anything external, which is why willpower alone does not fix this. In Microsoft’s survey, 68 percent of people said they do not have enough uninterrupted focus time during the workday.
The fix. Protect two blocks of quiet time a day, ninety minutes each if the work allows, during which phones go face down, notifications go off and questions wait unless they are genuinely urgent. Agree response windows out loud and write them down: chat answered within the half day, email within the working day, and one genuinely urgent channel, usually a phone call, for the rare thing that cannot wait. Work through messages in two or three set batches instead of continuously. If customers are the reason the team feels it must react instantly, run a simple rota so one person covers enquiries while the others work undisturbed, and swap. Customers end up with a reliable response time rather than an instant but distracted one.
2. Too many meetings, and meetings that decide nothing
The small business version is the weekly meeting that outlived its purpose years ago, the catch up that is really a status readout nobody needs spoken aloud, and the discussion that ends with everyone clear about the problem and nobody clear about what happens next. People attend just in case something relevant comes up, which means most of the room is paying full attention to a fraction of the agenda.
Workers rank this at the top of the problem list themselves. In Microsoft’s 2023 Work Trend Index, people named inefficient meetings as the number one disruptor of their productivity, with too many meetings third on the same list. Most said the outputs are murky too: 55 percent said it is usually unclear what the next steps are at the end of a meeting, and only 35 percent thought they would be missed in most of the meetings they attend. Asana’s index puts hours on the waste: unnecessary meetings cost knowledge workers 2.8 hours a week, and senior leaders 3.6 hours.
The fix. Every meeting has to earn its place with a question it must answer or a decision it must make, stated in the invite. If the meeting is only passing information, send the information in writing instead; status updates are reading, not meeting. Cut the default length to 25 minutes and see how little is lost. End every kept meeting by naming the actions, the owner of each one and the date, out loud and in a short note. Then audit the recurring meetings once a month and cancel the weakest one. In a small team, one cancelled weekly hour is a working day a month handed back.
3. Unclear priorities, and the task switching they cause
When everything is the priority, people spend the day reacting to whoever asked last or loudest. Three jobs are half finished, the important one is waiting on a piece of the unimportant one, and at the end of the day a busy team has moved many things a little and finished almost nothing. This is usually described as a time management problem in the team. It is more often a decision the owner has not made, or has made and not said out loud.
The evidence connects unclear direction with lost output directly. In Microsoft’s survey, lacking clear goals was the second biggest obstacle to productivity, behind only inefficient meetings, and 62 percent of respondents said they struggle with the amount of time spent searching for information during the workday, a symptom of work that has never been properly organised or assigned. The switching itself carries the cost described earlier: Gloria Mark’s research shows people average only about ten and a half minutes on a project before moving to another, and each move carries the restart cost when they return. A day of ten open tasks is not ten tasks progressing. It is ten tasks paying restart costs.
The fix. Give each person three named priorities for the week, in order, on one list the whole team can see. Three is a deliberate limit: a list of twelve priorities is a description of the workload, not a decision. When urgent new work arrives, and in a small business it will, say out loud what it displaces. That single habit, naming the trade instead of silently adding to the pile, is what turns a priority list from wall decoration into an agreement. Re-rank the list in a ten minute conversation at the start of the week rather than by interruption all week long.
4. Work with no single owner
This killer hides behind a friendly word: we. We are handling the complaint. We are chasing the supplier. We are updating the price list. A task that belongs to everyone in general belongs to no one in particular, and it moves at the speed of whoever happens to feel most guilty about it this week. In a small team the symptoms are easy to spot once you look: the same job done twice by two people, or not done at all because each assumed the other had it; deadlines that slip without anyone feeling the date was theirs; and an owner who has become the team’s memory, following up on everything because nobody else is sure what they own.
There is no large survey that isolates this one drain, and it would be dishonest to dress it up with a borrowed statistic. But it feeds the drains the surveys do measure. Coordination, the chasing and checking that Asana counts as work about work, grows fastest exactly where ownership is vague, because every hand off has to be negotiated instead of assumed. Microsoft’s finding that 55 percent of people leave meetings unsure of the next steps is the same failure in miniature: a discussion ended, and the doing was assigned to the room.
The fix. Put one name on every task, not a team, not a department, one person who owns the outcome even when others help. Attach a date and a plain statement of what done looks like: not “look into the delivery problem” but “find out why Tuesday’s deliveries ran late and tell me the cause by Thursday”. Owners of tasks report blockers early rather than apologies late, and the weekly priority list from the previous section is where ownership lives, reviewed as a list of commitments rather than a judgement of people. Where a job genuinely needs two people, name the lead and the helper. The lead owns the date.
5. Decisions that wait on the owner
In many small businesses, the business runs at the speed of one person’s inbox. Quotes wait for the owner’s approval. A refund waits. A reorder waits while stock runs down. Staff stand idle, or worse, guess, because the decision they need sits behind twenty other decisions in the same queue. The owner feels this as being constantly in demand and slightly behind. The team feels it as stalls they cannot clear, and the cost compounds quietly: work that was ready on Tuesday ships on Friday, and the team learns to pad every estimate to allow for the wait.
This is the small business version of the approval chains that large company research keeps finding inside work about work. The mechanism scales down brutally. A big firm has layers of managers to absorb delay; a team of six has one approver, who is also doing the selling, the hiring and often some of the delivery. Every routine decision that travels up to that one desk is queueing behind every other one, and a decision that takes the owner four minutes to make can still cost the business two days of elapsed time.
The fix. Write down the decision rules that currently live only in the owner’s head. Most are simple thresholds: spending up to a set amount without asking, offering a discount up to a set level, rescheduling a job, reordering stock that has fallen below a set point, approving a refund for a clear cut case. Give repeat situations standing approvals, so the third occurrence does not need a fresh decision at all. Hold one short decision window a day, a set time when the team brings everything that genuinely needs the owner, instead of a drip of interruptions that fragments the owner’s own work as badly as anyone else’s. Deciding on time is a leadership behaviour the whole team can observe, and our guide to improving leadership effectiveness at work covers the wider set of habits, including this one, that teams judge their leaders by.
6. Tools that create admin instead of removing it
Software is sold as the cure for admin, and some of it is. But every tool a small business adds brings its own upkeep: another inbox to check, another place the same information must be typed, another set of notifications competing for the same eyes. The common end state is a customer’s details living in a spreadsheet, a contact app and a paper diary, three versions of the truth, and staff spending real time each week copying updates between systems and hunting for the current one.
Asana’s 2023 index counted the tool load in larger workplaces: knowledge workers used 8.8 apps on average, and 10 for director level staff and above. The more apps, the more work leaked between them: 15 percent of workers using 6 to 15 apps said they miss messages and actions, rising to 25 percent among those using 16 or more. In a small team the numbers are smaller but the pattern is identical, and the admin lands on people the business can least spare, because there is nobody whose job is only admin.
The fix. Give each kind of information one home: one place for tasks, one for customer records, one for files, and let everything else be a view of those, not a rival copy. Kill duplicate entry first; if a figure must be typed twice, one of the systems is not earning its place. Turn off cross app notifications and let the quiet blocks from the first section do their work. Twice a year, list every subscription and login the team uses and retire whatever nobody has opened in a month. The test for any tool is simple: it should hand back more hours than it takes to feed it.
7. Presenteeism and fatigue
The last killer is the one that looks most like dedication. People stay late, answer messages at night, skip breaks and carry holidays forward, and the hours look impressive right up until the quality is examined: the quote with the error in it, the job that had to be redone, the short temper with a customer who deserved better. Output in a small team is not measured honestly in hours present. Tired people produce less per hour and make more mistakes per hour, so the long day can quietly deliver less than the focused shorter one it replaced.
The surveys show how widespread the strain is. In Microsoft’s 2023 Work Trend Index, 64 percent of people said they struggle with having the time and energy to do their job. Gloria Mark’s attention research explains part of the mechanism: attention is a limited resource that drains across the day, people have natural rhythms of stronger and weaker focus, with a peak for most in the mid to late morning and another around two to three in the afternoon, and the expectation of nonstop focus for hours at a stretch is simply not how people are built. A team scheduled as if attention were unlimited will spend its best hours on meetings and messages and its worst on the work that mattered.
The fix. Put the demanding work in the peak windows and the routine work around them, instead of letting the inbox decide the order of the day. Protect finishing times as a team norm, and let the owner visibly keep them too, because the team reads the real rule from what the boss does. Treat breaks as part of the work, short and away from screens, rather than a reward for finishing. And watch rework instead of hours: a rising pile of corrections is the earliest reliable sign that the team is running on empty. The daily experience of work, what it feels like to do the job in your business, is a business cost or a business asset, and our guide to the benefits of prioritising employee experience works through what changes when an owner treats it as one.
An honest note on named productivity systems
Anyone researching this topic meets named methods quickly: numbered rules, timed block systems, percentage principles, daily formulas with memorable shapes. Some of them help individuals organise a day, and any method that protects a block of focused time is pointing at a real problem. But a named system cannot cancel a standing meeting, name the owner of a task, or approve a quote while the owner is on holiday. Systems arrange the hours of a day. The killers in this article are what fills those hours, and they are properties of how the team works, not of how one person plans. Fix the structure first, then let each person use whatever personal method helps them keep the new habits. The reverse order, buying the team a system while leaving every drain in place, is why so many productivity drives fade by the second month.
Where to start: one fix a week, in this order
Seven killers is a long list, and a small team cannot change everything at once. This order works because each step makes the next one possible:
- Week one: protect focus. Set the two daily quiet blocks, agree the response windows for each channel, and start the customer cover rota.
- Week two: repair meetings. Cancel or shorten the recurring meetings, move status updates into writing, and end every kept meeting with named actions.
- Week three: make priorities and ownership visible. One shared list, three priorities per person in order, one named owner and a date on every task.
- Week four: clear the decision bottleneck. Write down the owner’s thresholds and standing approvals, and start the daily decision window.
None of this requires new software, a consultant or a reorganisation. It requires the owner to make a handful of decisions once, out loud, and then hold the line while the new defaults settle. That is a skill like any other in running a business, and it sits alongside the rest of the set covered in our guide to the skills needed to run a business. Expect the first week to feel slower. The second week is when the finished work starts to show it.
Sources used for this article
- University of California, Can’t pay attention? You’re not alone (interview with Gloria Mark, University of California, Irvine, on her attention research and her book Attention Span): https://www.universityofcalifornia.edu/news/cant-pay-attention-youre-not-alone
- Microsoft, Work Trend Index 2023, Will AI Fix Work? (survey of 31,000 people in 31 countries, with Microsoft 365 usage data): https://www.microsoft.com/en-us/worklab/work-trend-index/will-ai-fix-work
- Asana, Anatomy of Work Global Index 2023 (survey of 9,615 knowledge workers in six countries, conducted by GlobalWebIndex): https://asana.com/resources/anatomy-of-work
Frequently asked questions
What are the biggest productivity killers at work?
The biggest are constant interruptions and notifications, too many meetings that end without a decision, unclear priorities that push people into task switching, tasks with no single owner, decisions that wait on one person, software that creates extra admin, and fatigue from long hours. In a small business they usually appear together, which is why fixing one at a time, in order, works better than a general push to work harder.
How much time do meetings actually waste?
In Asana’s Anatomy of Work Global Index 2023, knowledge workers said unnecessary meetings cost them 2.8 hours a week, and senior leaders 3.6 hours. In Microsoft’s 2023 Work Trend Index, workers ranked inefficient meetings as the number one disruptor of their productivity, ahead of lacking clear goals, and 55 percent said the next steps at the end of a meeting are usually unclear.
Why does multitasking make people less productive?
Because switching is not free. Research led by Gloria Mark at the University of California, Irvine found that people now keep their attention on one screen for about 47 seconds on average, and that after an interruption it takes about 25 and a half minutes to return to the original project. Work done in fragments also gets picked up and put down repeatedly, so a task that needs one focused hour can take most of a day.
What is work about work?
Work about work is Asana’s term for time spent coordinating work instead of doing it: chasing status updates, sitting in progress meetings, searching for information and moving updates between apps. In the 2023 Anatomy of Work Global Index, knowledge workers spent 58 percent of their day on it, against 33 percent on the skilled work they were hired to do and 9 percent on strategy.
How can a small team cut interruptions without ignoring customers?
Agree how fast each channel really needs an answer, and make one channel, usually the phone, the genuinely urgent route. Set two or three fixed times a day for working through messages, protect blocks of quiet time between them, and use a simple rota so someone is always covering customers while the others work undisturbed. Customers get a reliable response time instead of an instant but distracted one.
What should a manager fix first?
Protect focus time. It is the fix every other fix depends on, because clear priorities, owned tasks and better meetings still fail if nobody gets an uninterrupted hour to act on them. Set the quiet blocks and response windows in week one, then repair meetings, then write down priorities and owners, and finally the decision rules that stop work queueing behind one person.
