Measure employee productivity by comparing output with the time or cost needed to produce it, using a few metrics that fit each role: what was delivered, how good it was and how long it took. Activity data such as active hours helps explain the numbers but should not replace them. No single metric works for every job.
Key takeaways
- Productivity is output divided by input. Hours are the input, not the result.
- Use two or three metrics per role, and always include one for quality.
- Activity data explains results. It does not prove them.
- Review trends monthly. Daily numbers are noise.
What is employee productivity?
Productivity is output per unit of input. The US Bureau of Labor Statistics defines labor productivity as the ratio of output per hour of work.
Productivity = output รท input
For a factory the output is units. For knowledge work the hard part is deciding what the output is. That decision is most of the job of measuring.
Which productivity metrics should you use?
Pick one metric from each column for each role.
| Role | Output | Quality | Time |
|---|---|---|---|
| Customer support | Tickets resolved | Satisfaction score, reopen rate | Handling time |
| Sales | Deals closed, pipeline created | Win rate | Length of sales cycle |
| Engineering | Issues or features shipped | Defects and rework | Cycle time |
| Design and content | Deliverables published | Rounds of revision | Turnaround time |
| Back office | Cases processed | Error rate | Processing time |
| Consulting and agencies | Milestones delivered, billable hours | Client satisfaction | Utilization |
Output without quality rewards speed over substance. Quality without time ignores cost. You need all three.
What are the three layers of measurement?
Outcomes
The result the business wants: revenue, retention, a shipped product.
Outputs
What a person or team produced toward it.
Inputs
Hours and activity.
Measure from the top down. Inputs are the easiest to collect and the least meaningful alone.
Where does activity data fit?
Time and activity data answer "how" and "why" questions about the numbers above:
- How many hours went into each project?
- How fragmented was the day?
- How much time went to meetings and communication tools?
- Is someone working long hours to hit the same output?
Many monitoring tools also calculate a productivity score, the share of tracked time spent in applications classed as productive. Treat it as a description of where time went. It says nothing about whether the work was good.
Which traps distort productivity numbers?
- One metric. People optimize for whatever is counted. This is Goodhart's law: when a measure becomes a target, it stops being a good measure.
- Activity as performance. Active hours reward presence, and they invite fake activity.
- Comparing different roles. A designer and a support agent cannot share a scale.
- Measuring individuals on team work. Much output belongs to a team.
- Trusting impressions. Microsoft found that 87% of employees said they were productive, while only 12% of leaders were fully confident their team was. Impressions on both sides are unreliable.
How do you set up productivity measurement?
- Define the outcome for each role with the people in it.
- Choose two or three metrics, including one for quality.
- Collect a baseline for a month before setting any targets.
- Review monthly. Look at trends, and compare people with their own history.
- Use the data to remove obstacles first. If the first action is help, the measurement will be trusted.
How does BirdsEye help measure productivity?
BirdsEye supplies the input layer, accurately and without effort.
- Tracked time by person, team and project.
- A productivity score based on rules you control. Every tracked minute is classed as productive, neutral or unproductive by application name, website domain or words in the window title.
- Starter rules for common development, office, communication and entertainment tools, and suggestions for the applications and sites no rule covers yet.
- Analytics with tracked time, productivity score, idle time and peak day, each compared with the previous period.
- Re-running rules over history, so reports stay comparable after you change a rule.
BirdsEye measures how time was spent. It does not measure the quality of the work, so pair it with the output and quality metrics above. See the features.
- VS Codeproductive
- Figmaproductive
- Outlookneutral
- Video streaming sitesunproductive
Frequently asked questions
What is the formula for employee productivity?
Productivity equals output divided by input. For example, 120 tickets resolved in 40 hours is 3 tickets per hour.
What are the best employee productivity metrics?
The best set combines an output metric, a quality metric and a time metric that fit the role. There is no universal best metric.
Can you measure productivity by hours worked?
No. Hours are an input. Two people can work the same hours and produce very different results.
How do you measure the productivity of remote employees?
The same way as anyone else: by output and quality first. Automatic time tracking adds a factual record of when and on what people worked. See How to monitor remote employees.