Stop Measuring Productivity by Hours


Somewhere in Australia right now, a manager is looking at timesheets and concluding that the person who logged 50 hours last week is more productive than the one who logged 38. This conclusion is almost certainly wrong.

Hours worked is the laziest productivity metric there is. It measures presence, not output. Effort, not results. And in an era where the most valuable work happens between someone’s ears, it’s actively counterproductive.

How We Got Here

The hours-equals-productivity equation made sense in factories. If you’re assembling widgets, more hours generally means more widgets. Simple.

But most modern work isn’t widget assembly. It’s thinking, planning, communicating, creating, and problem-solving. A software developer who solves a critical bug in two hours has produced more value than one who spends eight hours writing code that creates three new bugs. A marketing strategist who writes one brilliant campaign brief in a morning outperforms the one who churns out mediocre content all week.

We know this intuitively. Yet we keep tracking hours as if they matter.

The Damage Hours-Tracking Does

When you measure hours, you incentivise hours. People stay late to be seen. They spread work across more time to fill the day. They attend meetings they don’t need to attend because being “busy” is rewarded.

Research from Stanford has shown that productivity per hour drops sharply after 50 hours per week. Beyond 55 hours, the additional time produces almost nothing. You’re not getting more work — you’re getting more presence.

Worse, hours-focused cultures punish efficiency. If someone finishes their work in six hours and leaves, they’re seen as less committed than the person who takes ten hours to do the same amount. That’s insane. You’ve just penalised your best performer.

What to Measure Instead

The alternative isn’t “measure nothing.” It’s measuring the right things. Here are approaches that actually work:

Output-based metrics. What did you deliver this week? Not how long it took, but what got done. For developers, that might be features shipped or bugs resolved. For salespeople, pipeline generated or deals closed. For content teams, pieces published and their performance.

Outcome-based metrics. Even better than output: did the work actually achieve something? A marketing team could write ten blog posts (output) that nobody reads, or three posts (less output) that drive significant traffic. Outcomes matter more than volume.

Quality indicators. How many revisions did this need? Did it hit the brief the first time? Quality work done efficiently should be celebrated, not punished because it “only” took half a day.

The Manager’s Challenge

This requires managers to actually understand what their team does. You can’t evaluate output if you don’t know what good output looks like. Hours tracking is popular partly because it’s easy — anyone can compare two numbers.

Managing by outcomes requires judgment, context, and regular communication. You need to set clear expectations, define what “done” looks like, and trust your team to manage their own time. That’s harder than reading a timesheet. It’s also vastly more effective.

The Trust Problem

Let’s address the elephant in the room. Some managers resist outcome-based measurement because they don’t trust their employees. They worry that without hours tracking, people will slack off.

Here’s the thing: if someone is going to slack off, they’ll do it whether you track hours or not. They’ll just do it more creatively. Browsing the internet, having unnecessary meetings, doing busywork that looks productive but accomplishes nothing.

Trust is a better bet. A study published by Harvard Business Review found that employees in high-trust organisations are 50% more productive than those in low-trust ones. Trust isn’t naive — it’s strategic.

Practical Steps to Shift

You don’t have to abandon timesheets overnight (especially if clients require them for billing). But you can start changing the culture:

  1. Stop praising long hours. When someone stays until 8pm, don’t call it dedication. Ask why the workload requires it.
  2. Celebrate efficiency. When someone finishes a project ahead of schedule, that’s a win. Treat it as one.
  3. Set clear deliverables. Every week, every team member should know what they’re expected to produce. Not how many hours they should work — what they should deliver.
  4. Have real conversations. Replace timesheet reviews with brief weekly check-ins about what’s working, what’s stuck, and what’s next.
  5. Measure team outcomes. Revenue, customer satisfaction, project completion rates — these tell you more about productivity than any timesheet ever will.

The Australian Context

Australia already has a cultural advantage here. We’re not a country that glorifies overwork the way the US or Japan do. The concept of a fair go extends to fair working conditions. The Fair Work Ombudsman has been increasingly clear about the right to disconnect and the importance of reasonable working hours.

Let’s lean into that. Australian businesses can lead in building work cultures that value output over attendance, results over ritual. The companies that figure this out will attract better talent, retain them longer, and get more done with less burnout.

The Point

Stop counting hours. Start counting what matters. Your best employees already know the difference. It’s time management caught up.