Quick: a team ships 40 tasks this month and last month it shipped 50. Did productivity fall by 20 percent? Not necessarily, and that is exactly why most productivity formulas mislead people.
Learning how to calculate productivity sounds simple: output divided by input. The trouble starts when you decide what counts as output and what counts as input. Here is a practical way to get a number you can trust.
The basic formula
Productivity = Output / Input. For a knowledge team, input is usually hours worked. Output is the hard part, so choose it carefully.
Choosing the right output
Tasks completed. Easy to count, but a ten-minute task and a two-day task look the same.
Weighted tasks. Give each task a size (small, medium, large) and count points. This is fairer and still simple.
Delivered milestones. Best for project work: how many agreed deliverables were completed?
Revenue or billable value per hour. Useful for agencies and services, if tied to the same period.
Choosing the right input
Use actual hours, not scheduled hours. This is where most calculations break: a team scheduled for 160 hours that actually worked 190 did not become more productive by shipping more, it simply worked longer. Measure real effort, including overtime.
A worked example
Last month the team completed 50 weighted points in 190 real hours: 0.26 points per hour. This month it completed 40 points in 140 real hours: 0.29 points per hour. Fewer tasks shipped, but productivity rose, because the team worked fewer hours and kept the pace. The headline number said decline. The ratio said improvement.
Three traps to avoid
Comparing different kinds of work. A sprint of bug fixes and a sprint of new features should not share a benchmark.
Ignoring quality. Count only work that passes review, not work that bounces back.
Tracking individuals by minutes. Productivity is a team and process measure. Used on individuals by the minute, it produces gaming instead of improvement.
Make it a habit
Pick one output measure and one input measure, calculate the ratio every two weeks, and plot it. The trend matters more than any single number. Review it with the team and ask what helped and what got in the way.
Where We360.ai fits
To calculate productivity reliably, you need real hours by project and task. We360.ai's productivity tracking captures them automatically, shows workload and overtime trends, and shares the same view with the team. It is used by 120K+ users across 10K+ companies in 21+ countries and rated 4.7 on G2.
Keep reading
See why your remote team is not slower, your handoffs are and the Monday meeting test for dashboards.
Try the calculation on real data. Start your free We360.ai trial and compare one month of real hours with your output.
