Comparison
Capacity Planning vs Lean Operations
Use this comparison to separate adjacent concepts, understand where each one fits, and avoid solving the wrong business problem with the wrong metric or framework.
Capacity Planning
Operations
Definition
Capacity planning is the process of determining how much work your team can handle and aligning resources to demand. The core calculation is: Available Capacity = Team Size ร Working Hours ร Productivity Factor (typically 0.6-0.8 after meetings, admin, and context-switching). A team of 5 engineers working 40h/week at 70% productivity has 140 productive hours/week, not 200. Companies that do capacity planning well ship 35% more features per engineering dollar by eliminating both overwork (burnout โ turnover) and underutilization (idle teams โ wasted salary).
Common trap
The capacity trap is planning at 100% utilization. Organizations that load teams to 95-100% see throughput DECREASE by 20-30% because there's no buffer for bugs, urgent requests, sick days, or creative thinking. McKinsey's research shows optimal knowledge work utilization is 70-85% โ above that, quality drops, bugs increase, and burnout skyrockets. Another trap: headcount-based planning. Adding 1 engineer doesn't add 1 engineer's worth of output โ it adds 0.5-0.7 due to onboarding, mentoring overhead, and increased communication costs (Brooks's Law).
Practical use
Calculate your team's true capacity: (Number of ICs ร Weekly Hours ร Productivity Factor) - Planned meetings - On-call hours = Actual Weekly Capacity. Track velocity (story points or tickets completed) over 4-week rolling average. If actual output is consistently below 70% of theoretical capacity, audit where time goes โ most teams lose 30-40% to meetings, Slack, and context-switching. Set a 'capacity budget': 70% planned work, 15% unplanned/bugs, 15% tech debt and improvements.
Formula
Lean Operations
Operations
Definition
Lean operations systematically eliminates waste โ any activity that consumes resources without creating customer value. Toyota identified 7 types of waste: overproduction, waiting, transport, over-processing, inventory, motion, and defects. Lean companies can operate at 50-70% lower cost than non-lean competitors while delivering higher quality.
Common trap
Teams apply 'lean' as an excuse to under-invest. Real lean isn't about cutting corners โ it's about cutting WASTE. Eliminating your QA team isn't lean, it's reckless. Automating repetitive QA tests so your team focuses on complex edge cases? That's lean.
Practical use
Start with a value stream map: list every step from customer request to delivery. For each step, ask 'Would the customer pay for this?' If no, it's a candidate for elimination. Target: eliminate 20% of non-value-adding activities each quarter until your process is 80%+ value-adding.
Formula
Decision framing
Focus on Capacity Planning when
Calculate your team's true capacity: (Number of ICs ร Weekly Hours ร Productivity Factor) - Planned meetings - On-call hours = Actual Weekly Capacity. Track velocity (story points or tickets completed) over 4-week rolling average. If actual output is consistently below 70% of theoretical capacity, audit where time goes โ most teams lose 30-40% to meetings, Slack, and context-switching. Set a 'capacity budget': 70% planned work, 15% unplanned/bugs, 15% tech debt and improvements.
Focus on Lean Operations when
Start with a value stream map: list every step from customer request to delivery. For each step, ask 'Would the customer pay for this?' If no, it's a candidate for elimination. Target: eliminate 20% of non-value-adding activities each quarter until your process is 80%+ value-adding.
Use the comparison, then pressure-test the decision.
Browse the library for more context, open a diagnostic to model the tradeoff, or start an inquiry if this comparison maps to a live business bottleneck.