What is Throughput Variance?
Throughput variance measures how much the number of completed tasks fluctuates over time; it shows how predictable your output is from day to day or week to week.
Throughput is the count of tasks or work items you finish in a given period (day, week, sprint). Throughput variance is a measure of how much that count changes across multiple periods. In simple terms, it answers whether you consistently finish roughly the same amount of work, or whether your productivity spikes and drops unpredictably. Practically it’s calculated by looking at a series of throughput values (for example, tasks completed each week) and summarising their spread using statistics like standard deviation or the coefficient of variation (standard deviation divided by the mean). High variance means your capacity is unstable; low variance means your output is steady and easier to plan around.
Usage example
If you complete 4, 9, 3, 8, and 6 tasks over five consecutive weeks, your average weekly throughput is 6 and the spread of those numbers is the throughput variance. A manager or solo founder noticing this high variance would know commitments should include buffers or smaller, better-defined tasks to improve predictability.
Practical application
Knowing your throughput variance helps you make realistic plans, reduce overcommitment, and lower decision fatigue. For example: - Forecasting: Low variance makes it safer to promise delivery dates; high variance suggests longer buffers or fewer concurrent commitments. - Workflow design: If variance stems from task size, breaking work into smaller items will smooth throughput. - Prioritisation: High variance often correlates with interruptions or context switches; reducing these improves both throughput and well-being. - Personal habits: Tracking variance over time highlights which routines (time-blocks, batching, or environmental changes) reliably stabilise output—valuable for neurodivergent people who benefit from consistent structure. Tools that log completed tasks and visualise trends can surface throughput variance automatically and suggest where to stabilise workflow; for example, nxt can help collect completion data and point out patterns so you can act on them without manual tracking.
FAQ
How is throughput variance different from velocity?
Velocity is the average amount of work completed over a period; throughput variance describes how much that velocity jumps up and down between periods. Think of velocity as the central tendency (how much you usually get done) and variance as the reliability of that amount.
Is high throughput variance always bad?
Not always. Short-lived variance can reflect legitimate differences in task complexity (e.g., a week of big projects). Persistent high variance, however, makes planning hard and increases stress. The goal is to understand causes and reduce avoidable variability.
How often should I measure throughput variance?
Choose a cadence that matches how you work—daily for highly interrupt-driven roles, weekly for knowledge work, or per sprint for product teams. Use at least 6–8 periods to spot meaningful patterns rather than random noise.