Five Numbers That Tell You if Your Team is Struggling   

So what should you be looking at instead? Here are the five things I suggest you look more closely at to get the true picture of your team’s productivity. 

Non-Billable Time Patterns 

Not just how much non-billable time your team spends, but on what. And whose non-billable time is higher than everyone else's. 

If admin time is growing faster than billable time, you've got a process problem. The business is getting more complicated without the systems to support it. 

If certain people consistently have much higher non-billable time than others doing similar work, it needs to be investigated. There could be various things happening, from a knowledge bottleneck to unclear responsibilities, or someone carrying the weight of processes that should be shared across the team. 

Now, I’m absolutely not suggesting this as a means of finding the "unproductive" person and hauling them in for talking to. Look at this as a way to spot where good people are being held back by bad systems. 

What good looks like: consistent, predictable patterns. Everyone's non-billable time follows roughly the same shape because processes are clear and work is distributed sensibly. 

Time Between Work Done and Invoice Raised 

The gap between your team finishing work and that work appearing on an invoice tells you everything about how your processes function. 

Are we talking days or weeks? Because weeks mean the processes are living in someone's head, so the information isn't flowing as it should. Some poor soul is probably trying to remember what happened three weeks ago to get it billed. 

This costs you in three ways. 

First, cashflow. You've done the work, incurred the cost, but money's not coming in because the invoice hasn't gone out. 

Second, revenue leakage. Work that takes too long to bill often doesn't get billed at all. Either it feels too awkward to invoice something from two months ago, or it just gets forgotten entirely. 

Third, client relationships. Try billing someone for work you did eight weeks ago. They'll have questions. Possibly complaints. It looks disorganised because it is disorganised. 

What good looks like: days between work completion and invoice raised, not weeks. If you're hitting that consistently, celebrate! Your processes are working. 

Error Correction Costs 

How much time and money does your team spend fixing mistakes? 

Again, this isn't about blaming people or taking disciplinary action. Everyone makes mistakes; the question is whether those errors are random one-offs or patterns that reveal something about where your team needs support. 

If the same types of errors keep happening, take notice and ask why. Is it a lack of training, unclear processes, or people carrying too much cognitive load? Sometimes systems that require too many manual steps are where mistakes can creep in. 

I’ve seen businesses losing thousands every month to error correction and treating it as just "part of doing business." It isn't. Or it doesn't have to be. 

What good looks like: Declining error-correction costs over time as you identify patterns and fix the root causes. Don't expect zero errors; it’s unrealistic, but it certainly doesn't need to be costing you thousands. 

Knowledge Concentration Risk 

How many critical processes can only one person do? 

You can measure this pretty easily. What stops when someone's on holiday? How long does it take to train someone to cover for them? How many times a week does someone say "I'll ask Sarah, she's the one who knows how to do that"? 

This is expensive in ways that don't show up on your P&L but absolutely show up in your stress levels and business risk. 

You can't grow if critical processes live in one person's head. You can't take a proper holiday if the business needs you to answer questions every day. You can't promote people or redistribute work if only they know how their bit works. 

And if that person leaves? You're reconstructing five years of institutional knowledge from email trails and guesswork. 

What good looks like: documented processes, cross-training, and no single point of failure. Anyone on the team can step in to cover critical tasks with a handover document and an hour of explanation, not three weeks of trial and error. 

Response Time to Financial Questions 

How long does it take to get answers to basic financial questions? 

"Can we afford this purchase?" "What did we spend on marketing last quarter?" "Are we on track to hit our revenue target?" "What's our biggest cost this month?" 

If these questions take days to answer, or you're making decisions based on gut feel because getting the exact numbers is too much work, something's not right. 

Often this points to someone on your team carrying responsibility they're not quite equipped for. Maybe your office manager's picked up the bookkeeping because someone had to. Maybe you've got a junior doing the accounts who's capable but hasn't got the experience to pull meaningful reports together quickly. 

They're doing their best, but they're missing the skills or knowledge to turn raw data into useful answers. So questions sit unanswered, or the answers take ages to pull together, or you're making decisions without the financial visibility you need. 

This costs you in slow decision-making. Missed opportunities because by the time you've figured out if you can afford something, the moment's passed. Team frustration because they can't get the information they need to do their jobs properly. 

What good looks like: being able to answer financial questions in hours, not days. Having someone with the skills to give you that visibility, whether that's upskilling your current team, bringing in proper bookkeeping support, or having someone at a more senior level who can translate the numbers into business insights.