Think Build Implement Repeat
London, UK +44 7367 067226
WhatsApp FOLLOW f in X
  1. Home
  2. Blog
  3. Knowing Whether Work Is Progressing, Without Watching People
Business Automation

Knowing Whether Work Is Progressing, Without Watching People

Measuring team productivity without surveillance: why activity metrics backfire, measuring flow and outcomes instead, and what monitoring software costs.

Updated 2 min readBy SpiderHunts Technologies

Free estimateNo obligation

Get a free estimate

Tell us what you need. A senior engineer reads every enquiry.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →

Quick answer — TL;DR

Measure outcomes and flow — what shipped, how long things take, how much is stuck — not activity. Activity metrics are easy to collect, easy to game, and reliably damage the behaviour they are meant to improve.

Activity metrics make things worse

Lines of code, tickets closed, hours logged, keystrokes. All measurable, all gameable, and all measuring effort rather than value.

Worse, they change behaviour in predictable ways: more small tickets, less refactoring, less helping colleagues, and quiet resentment. The measurement damages the thing it measures.

Measure flow instead

  • Cycle time — how long from starting a piece of work to it being live
  • Work in progress — how many things are open at once, which is usually too many
  • Blocked time — how long things wait, and on what
  • Deployment frequency — how often value reaches customers
  • Failure rate — how often a change causes a problem
Blocked time is the most useful and least measured. In most teams, work spends far longer waiting than being worked on, and the waiting is usually a management problem rather than a capacity one.

Look at the system, not the individual

Flow metrics describe the system. If cycle time is long, the cause is usually queueing, unclear requirements, or too much work in progress — not individuals working slowly.

Using team metrics to assess individuals is how a diagnostic tool becomes a surveillance one, at which point the numbers stop being honest.

Ask the team

The people doing the work know where the friction is. A regular, blameless conversation about what slowed things down this fortnight surfaces more than any dashboard.

Then fix what they name. A team asked repeatedly and never acted upon stops answering honestly.

What monitoring software costs you

Screenshot monitoring and activity tracking damage trust substantially and measure presence rather than contribution. The strongest performers are usually the first to leave when it is introduced.

If the underlying concern is that you cannot see progress, the answer is regular demonstrations of working software, not surveillance.

For outsourced work

The same principle applies: judge on delivered functionality demonstrated regularly, not on hours reported. Time sheets tell you what was spent, not what was achieved.

FAQ

Frequently asked questions

The questions readers ask us after this guide.

Still have a question?

Ask us directly — a senior engineer will get back to you.

Ask about your project

How do we know if someone is underperforming?

Through the work: what is delivered, its quality, and how they collaborate. A manager close enough to the work knows within weeks, without any metric.

Is velocity a useful measure?

As a capacity planning input for a stable team, sometimes. As a target or a comparison between teams, no — it inflates immediately and stops meaning anything.

What about billable utilisation?

Necessary in a service business as a commercial measure, and it is not a productivity measure. High utilisation with poor delivery is worse than moderate utilisation with good delivery.

Should we track time at all?

For client billing and for understanding where effort goes, yes, at a coarse level. Fine-grained tracking costs more in accuracy and morale than it returns.

Keep reading

More on Business Automation

Start here

Wondering whether your team is delivering?

Regular demonstrations of working software answer that better than any metric. Happy to talk through what to look at.

  1. You tell us what you needTwo minutes on the form, or a message on WhatsApp.
  2. A senior engineer reviews itAnd comes back with questions, a realistic range and an honest view on fit.
  3. Free 30-minute scoping callWe talk through scope, options and a realistic estimate — with no obligation.
Free estimateNo obligation

Talk to someone who builds this

Send a short brief and we will come back with an honest view and a realistic range.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →