Productivity sounds like a vague idea until you have to put a number on it. Then it turns out to be one division: how much you got done, divided by what it took.
This guide gives you the formulas, three worked examples, a calculator you can use right here, and the mistakes that make the number meaningless. The arithmetic is easy. Choosing what to count is the hard part.
Quick answer: Productivity = output ÷ input. If you produce 100 units in 20 hours, productivity is 5 units per hour. To see whether you improved, compare two periods: (new ÷ old − 1) × 100 gives the percentage change.
Calculate it now
Pick the calculator that matches your question. Everything runs in your browser and nothing is saved.
1. Productivity (output per hour)
2. Change between two periods
3. Actual versus target
The three formulas (they answer different questions)
Many guides blur these together. They are not the same measure.
| Question | Formula | Example |
|---|---|---|
| How much do I get done per hour? | Output ÷ input | 100 units ÷ 20 hours = 5 units per hour |
| Did I get better or worse? | (New ÷ old − 1) × 100 | (8 ÷ 5 − 1) × 100 = +60% |
| Did I hit my target? | (Actual ÷ target) × 100 | 90 ÷ 100 × 100 = 90% |
The third formula is a target attainment rate, not productivity. It tells you how close you got to a goal, not how much you got per hour of input. A person who hits 100% of a target in 30 hours is less productive per hour than one who hits it in 20, even though both score 100%.
What the official statisticians do
The US Bureau of Labor Statistics defines its labor productivity measures this way: "Measures of labor productivity compare the growth in output to the growth in hours worked." Its productivity page labels the measure "Labor productivity (output per hour)," and for the nonfarm business sector it reports "Real value-added output" (BLS).
For you, the useful takeaway is the structure: one measure of output, one measure of hours, and a comparison over time. A single number means little by itself. The trend is the point.
Three worked examples
These numbers are made up to show the arithmetic.
1. A writer. Draft 4,000 words in 8 hours: 4,000 ÷ 8 = 500 words per hour. A month later, the same 4,000 words take 5 hours: 4,000 ÷ 5 = 800 words per hour. Change: (800 ÷ 500 − 1) × 100 = +60%. Output per hour rose. The number alone doesn't tell you why. Maybe the draft got easier, or maybe the quality dropped.
2. A support team. Five people work 8 hours each and close 60 tickets. Input is 5 × 8 = 40 hours. 60 ÷ 40 = 1.5 tickets per hour. If a new tool lifts the team to 72 tickets in the same 40 hours, that's 1.8 per hour, a +20% change.
3. Revenue per hour. A freelancer brings in $50,000 over 400 working hours: $50,000 ÷ 400 = $125 per hour. That is revenue per hour, not profit. Take out costs before you compare it with a wage.
Pick the right "output"
Productivity is only as honest as the output you choose. Some options:
| Work | Easy-to-count output | Risk |
|---|---|---|
| Writing | Words | Rewards length, not quality |
| Support | Tickets closed | Rewards closing, even when the issue returns |
| Sales | Calls made | Rewards activity, not deals |
| Design | Screens finished | Ignores revisions |
These pairings are our reading, not research findings. The pattern is simple: the easiest thing to count is often the wrong thing. Where you can, use a measure that includes quality, such as tickets closed and not reopened, or articles published and still ranking.
Pick the right "input"
Input is usually hours, but which hours?
- Hours worked is the cleanest. Track them with a time tracking app or a time audit for a week.
- Hours at your desk includes breaks, meetings and drift. It will make your number look lower, and that may be the useful finding.
- Money or tools can be the input too, such as cost per unit made. Keep it consistent from period to period.
Mistakes that skew the number
- Changing the definition mid-way. If you count words one month and finished articles the next, you can't compare them.
- Comparing different tasks. Editing and first drafts run at different speeds. Measure like with like.
- Using too short a window. One day tells you about that day. A few weeks tells you more.
- Ignoring quality. A faster number that comes with more errors isn't an improvement.
- Reading it as a verdict on effort. A 60% rise in output per hour doesn't prove you worked harder, or smarter. It shows a change that needs explaining.
What to do with the number
- Find what changed. If the number went up, what did you do differently that week? If it dropped, look at interruptions and meeting load before blaming yourself.
- Protect your best hours. Our guide to time blocking vs time boxing shows how to reserve time for your main work.
- Look at the bigger picture. Productivity is one lens. Productivity vs efficiency explains how it differs from related ideas, and how to improve productivity at work covers what to try next.
Frequently asked questions
How do you calculate productivity? Divide output by input. With 100 units in 20 hours, productivity is 5 units per hour.
What is the formula for employee productivity? Output per employee ÷ hours worked is the usual starting point. Choose an output that fits the job, and include quality where you can.
How do you calculate productivity as a percentage? To show change, use (new productivity ÷ old productivity − 1) × 100. To show how close someone came to a goal, use (actual ÷ target) × 100. The second is target attainment, not productivity.
How often should you measure it? Weekly is a sensible rhythm for most people. A longer window smooths out unusual days.
What does "productivity" mean? In short: valuable output relative to the input it took. Our guide to the meaning of productivity goes through it with examples.
Updated 18 October 2026: we separated productivity from target attainment, added the calculators and removed an unsourced claim about wages. The BLS wording was checked on its productivity page.
Sources