Productivity Metrics: What to Track and Why

Peter Drucker's famous line -- "What gets measured gets managed" -- is both true and dangerous. True because measurement drives attention and improvement. Dangerous because measuring the wrong things can optimize for outputs that do not matter.

Productivity metrics are especially tricky. "Tasks completed" is easy to measure but easy to game (break everything into tiny tasks). "Hours worked" is meaningless if those hours are spent on low-value activities. "Revenue generated" ignores the work that does not directly produce revenue but is essential to the business.

This guide identifies the productivity metrics that genuinely improve your work when tracked, explains what each one reveals, and warns about the metrics that lead you astray.

The Metrics That Matter

1. Tasks Completed (with Context)

Raw task count is a vanity metric. But task completion with context -- how many tasks you finished relative to how many you planned, broken down by priority -- is genuinely useful.

What to track:

• Daily completion rate: tasks completed / tasks planned
• Weekly completion rate by priority: did you finish your high-priority tasks?
• Carryover rate: how many tasks rolled from today to tomorrow?

What it reveals:

• If your daily completion rate is consistently below 60%, you are overplanning.
• If your high-priority completion rate is lower than your low-priority rate, you are avoiding important work.
• If your carryover rate is rising, your backlog is growing faster than you can execute.

2. Focus Time

Focus time is the number of hours spent in deep, uninterrupted work on a single task. This is the most valuable type of work for knowledge workers, and it is typically the scarcest.

What to track:

• Total focus hours per day and per week
• Average uninterrupted session length
• Focus time as a percentage of total work time

What it reveals:

• Most knowledge workers achieve only 2-3 hours of genuine focus time per day. If you are below 2 hours, your schedule is too fragmented.
• If your average session length is under 30 minutes, interruptions are destroying your deep work capacity.
• If focus time is less than 30% of your total work time, meetings and reactive work are dominating.

Tracking focus time is straightforward with a Pomodoro timer -- each completed session is a documented unit of focus. SettlTM's analytics dashboard tracks focus sessions automatically and shows trends over time.

3. Streak Length

A streak is the number of consecutive days you have maintained a specific habit: daily planning, completing at least one MIT, hitting your focus time target, or keeping zero overdue tasks.

What to track:

• Planning streak (consecutive days of morning planning)
• Completion streak (consecutive days of completing all MITs)
• Focus streak (consecutive days of hitting your focus time target)

What it reveals:

• Streaks build momentum and make habits automatic. A 30-day streak is harder to break than a 3-day streak.
• Broken streaks reveal patterns. Do you consistently break on Fridays? After travel? During certain project phases?

4. Velocity (Tasks per Unit Time)

Velocity measures how many tasks (or story points, or effort units) you complete per week. It is a throughput metric that shows your sustained capacity.

What to track:

• Tasks completed per week (absolute)
• Effort points completed per week (if you use effort estimates)
• Velocity trend over 4-8 weeks

What it reveals:

• A stable velocity means your capacity is consistent and your planning can be calibrated to it.
• Rising velocity suggests improving efficiency or increasing work hours (check which one).
• Declining velocity may signal burnout, increasing task complexity, or growing overhead.

5. Cycle Time

Cycle time measures how long it takes from when you start a task to when you finish it. This is different from effort (how much time you spend working on it) because it includes the waiting time, context switching, and delays between work sessions.

What to track:

• Average cycle time by task type
• Cycle time distribution (are most tasks fast with a few outliers?)
• Tasks with unusually long cycle times (potential bottlenecks)

What it reveals:

• Long cycle times with short actual effort times indicate too much work-in-progress. You are starting tasks but not finishing them because you are spread across too many things.
• Consistently long cycle times for a specific task type may indicate unclear requirements, missing skills, or dependency bottlenecks.

6. Overdue Rate

The percentage of tasks that miss their due date.

What to track:

• Number of overdue tasks at any given time
• Average days overdue
• Overdue rate by project or priority level

What it reveals:

• A rising overdue rate means you are committing to more than you can deliver.
• Chronically overdue tasks in a specific project may indicate under-resourcing or unrealistic deadlines.
• If low-priority tasks are always overdue but high-priority tasks are not, your triage is working correctly.

7. Capacity Utilization

Capacity utilization compares actual productive time against available time. If you have 6 hours of available time and spend 5 on productive work, your utilization is 83%.

What to track:

• Available hours per day (after meetings, breaks)
• Productive hours per day (time spent on tasks)
• Utilization rate (productive / available)

What it reveals:

• Utilization below 60% suggests significant time loss to context switching, interruptions, or untracked activities.
• Utilization above 90% is unsustainable -- you need buffer time for unexpected work and cognitive recovery.
• Optimal utilization for most knowledge workers is 70-85%.

The capacity calculator can help you compute your daily available hours based on your calendar and preferred work patterns.

Metrics That Lead You Astray

Hours Worked

Tracking hours worked incentivizes presence over output. A person who finishes their work in 5 focused hours is more productive than someone who spreads the same work over 10 distracted hours. Measure output, not input.

Raw Task Count

Breaking a single task into 10 subtasks does not make you 10x more productive. Task count without priority weighting or effort weighting is meaningless and easily gamed.

Email Response Time

Fast email response time is often inversely correlated with deep work. Responding to every email within 5 minutes means you are checking email constantly, which destroys focus. Unless your role specifically requires rapid email response, this is an anti-metric.

Busyness Indicators

Meetings attended, messages sent, documents created -- these are activity metrics, not productivity metrics. Activity can be high while output is low. Focus on outcomes, not activities.

Building a Personal Productivity Dashboard

Pick 3-5 metrics that are most relevant to your role and goals. More than 5 metrics creates tracking overhead that outweighs the benefit.

A recommended starter dashboard:

| Metric | Frequency | Target | |--------|-----------|--------| | Daily completion rate | Daily | 75-90% | | Focus hours | Daily | 3+ hours | | Planning streak | Daily | Maintain 30+ days | | Weekly velocity | Weekly | Stable or growing | | Overdue count | Weekly | Under 5 tasks |

Review this dashboard weekly during your planning session. Look for trends, not daily fluctuations. A bad day is noise. A bad week is a pattern. A bad month is a problem.

Metrics for Different Roles

For Software Developers

Developers should focus on cycle time (how long from starting a task to shipping it), deep focus hours (uninterrupted coding time), and code review turnaround. Pull request count is a weak metric -- one large, well-tested PR is more valuable than five trivial ones.

For Managers

Managers should track delegation effectiveness (how many tasks are completed by the team without re-work), meeting time ratio (percentage of day in meetings vs. focused work), and team velocity trends. Individual task completion matters less for managers than whether the team is productive.

For Freelancers

Freelancers should track billable utilization (billable hours / total work hours), average project cycle time, and client satisfaction. Revenue per hour is a useful meta-metric that combines productivity with business value.

For Students

Students should track study hours by subject (are you allocating time proportional to difficulty?), assignment completion rate (are you submitting everything on time?), and focus session length (are your study sessions long enough for deep learning?).

Setting Up Your Tracking System

The best tracking system is one that runs automatically. Manual tracking requires discipline that competes with the discipline needed for actual work.

Here is a progressive approach:

Week 1: Start with one metric. Track daily task completion rate -- simply note how many tasks you planned and how many you finished. This single metric reveals whether your planning is realistic.

Week 3: Add focus time tracking. Use a Pomodoro timer that counts completed sessions. Each 25-minute session is one unit of tracked focus time.

Week 5: Add a weekly review metric. At the end of each week, rate your week on a 1-10 scale and note one thing that went well and one thing to improve. This qualitative metric captures patterns that quantitative metrics miss.

Week 8: Build your dashboard. By now you have enough data to identify which metrics are genuinely useful for you. Build a simple dashboard with 3-5 metrics and review it weekly.

The Danger of Over-Tracking

There is a point where tracking becomes counterproductive. Signs you are over-tracking:

• You spend more than 15 minutes per week on metric maintenance
• You feel anxious about your numbers rather than informed by them
• You are optimizing for the metric rather than the outcome (Goodhart's Law: when a measure becomes a target, it ceases to be a good measure)
• You have more than 7 metrics on your dashboard

If you notice these signs, simplify. Drop to 2-3 metrics that directly inform your decisions and ignore the rest.

Tracking Without Obsessing

The purpose of metrics is to inform improvement, not to create anxiety. Some guardrails:

• Automate tracking wherever possible. Manual tracking adds friction and is easy to forget. Tools that track automatically (like focus session counters and completion rates) are more sustainable than spreadsheets.
• Review weekly, not daily. Daily metrics fluctuate too much to be actionable. Weekly trends reveal real patterns.
• Use metrics to ask questions, not to judge yourself. A declining focus time does not mean you are failing. It means something changed -- more meetings, a new project, increased interruptions. Investigate the cause rather than blaming yourself.
• Iterate on what you track. The metrics that matter at the start of a new role may differ from what matters six months in. Revisit your dashboard quarterly.

Key Takeaways

• The most useful productivity metrics are contextual task completion rate, focus time, streak length, velocity, cycle time, overdue rate, and capacity utilization.
• Avoid vanity metrics like hours worked, raw task count, and email response time. These measure activity, not productivity.
• Pick 3-5 metrics for your personal dashboard and review them weekly, not daily.
• Automate tracking wherever possible to reduce friction and improve consistency.
• Use metrics to identify patterns and ask questions, not to judge performance on any single day.

Want automatic productivity analytics without manual tracking? Try SettlTM free and get built-in dashboards for focus time, completion rates, streaks, and more.

Frequently Asked Questions

How many productivity metrics should I track?

Start with 3. Add more only when you have a specific question that the current metrics do not answer. Tracking 10+ metrics creates overhead that reduces the time available for actual productive work.

Is it worth tracking productivity if I am the only one who sees the data?

Yes. Self-tracking is about self-improvement, not external reporting. The patterns you discover -- your peak hours, your realistic capacity, your common failure modes -- are useful regardless of whether anyone else sees them.

How do I track focus time accurately?

Use a timer. Start it when you begin focused work, stop it when you are interrupted or take a break. Pomodoro timers do this automatically in 25-minute increments. The key is consistency -- track every focus session, not just the ones you remember.

What is a good daily completion rate?

For most knowledge workers, 75-90% is a healthy range. Below 60% suggests overplanning. Above 95% consistently suggests under-planning -- you may be sandbagging to ensure you always hit your targets. A completion rate that fluctuates between 70% and 90% usually indicates realistic, adaptive planning.

Should I share my productivity metrics with my manager?

That depends on your relationship and organizational culture. Focus time and velocity can be useful context in 1:1s -- they explain why certain weeks were more productive than others. But be cautious about sharing metrics that could be misinterpreted (e.g., a low completion rate that reflects ambitious planning rather than poor performance).