Standard Deviation Calculator
Enter comma-separated numbers to calculate standard deviation, variance, mean, and coefficient of variation. Measure data variability and consistency. Choose between population and sample calculations.
Enter comma-separated numbers to calculate standard deviation, variance, mean, and coefficient of variation. Choose between population (all data) or sample (subset of data) calculations. Essential for analyzing demand variability, quality control, and KPI dispersion.
Separate values with commas. Example: 10, 15, 20, 25, 30
Sample for subset data, Population for complete dataset
Formula
Mean = Σx ÷ n | Variance = Σ(x - Mean)² ÷ (n-1 or n) | SD = √Variance | CV = (SD ÷ Mean) × 100
Standard deviation measures how spread out data is from the average. A low SD means values cluster near the mean; a high SD indicates wide dispersal. Use the sample formula (n-1) when analyzing a subset; use population (n) for a complete dataset. The coefficient of variation (CV) shows relative variability and is useful for comparing datasets with different means. For example, a delivery time SD of 2 hours with a 10-hour mean is less variable than a 3-hour SD with an 8-hour mean (CV: 20% vs 37.5%).
Worked Example
Quality Control: Analyzing tablet weights (sample of 5):
Data: 500mg, 502mg, 498mg, 501mg, 499mg
Mean = (500 + 502 + 498 + 501 + 499) ÷ 5 = 500 mg
Variance = [(0)² + (2)² + (-2)² + (1)² + (-1)²] ÷ 4 = 2.5
SD = √2.5 = 1.58 mg
CV = (1.58 ÷ 500) × 100 = 0.32%
The tablets consistently weigh around 500mg with minimal variation (CV = 0.32%). This indicates tight quality control.
Demand Forecasting: Analyzing weekly sales (sample of 8 weeks):
Data: 1000, 1200, 950, 1100, 1050, 1300, 900, 1250 units
Mean = 1093.75 units
SD = 127.39 units (sample)
CV = 11.65%
Weekly demand varies by about 127 units from the average of 1094 units, indicating moderate demand variability (CV = 11.65%). This helps with inventory safety stock planning.
Common Mistakes
1. Confusing sample SD with population SD
Sample SD uses (n-1) divisor, population SD uses (n). For most business scenarios (forecasts, test batches), use sample SD.
Wrong: Using population SD on a sample of 10 monthly revenues. Right: Use sample SD (divide by 9) because this is a subset representing future variability.
2. Using variance instead of SD for interpretation
Variance is in squared units (hard to interpret); SD is in original units. SD is more intuitive. A variance of 100 (for prices in dollars) means SD = $10.
3. Ignoring outliers that distort SD
One extreme value can significantly increase SD. Investigate outliers: are they errors, genuine anomalies, or special causes? A delivery time of 48 hours among 2-4 hour deliveries will skew the SD.
4. Comparing SDs without considering mean (ignoring CV)
Don't compare SD = 5 across datasets with means of 50 and 500—the first is far more variable. Use CV instead: first = 10%, second = 1%.
5. Forgetting the context of variability
High variability in delivery times suggests process inconsistency or external factors (traffic, inventory levels). Low CV in quality metrics is good. High CV in customer satisfaction scores signals inconsistent experience. Always interpret SD in business context.
Frequently Asked Questions
Use this in your workflow
After analyzing data variability, use the Z-Score Calculator to standardize individual values, or the Confidence Interval Calculator to build ranges around your mean. Use the Percent Change Calculator to track how variability shifts over time. Explore all Business Calculator Hub tools.
When to use this calculator
- →Analyzing delivery time variability to understand service consistency and plan contingencies
- →Forecasting demand with historical sales data to calculate safety stock and inventory buffers
- →Measuring quality control consistency in product specifications across production batches
- →Evaluating KPI consistency (conversion rates, response times, customer satisfaction scores)
- →Comparing variability across different processes or time periods using coefficient of variation
- →Supporting statistical process control (SPC) to detect when processes drift out of expected bounds