Comparison
Capacity Planning vs Hiring Strategy
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
Hiring Strategy
Leadership
Definition
Hiring strategy determines WHO you hire, WHEN you hire them, and HOW you evaluate fit. A bad hire costs 1.5-3x their annual salary when you factor in recruiting costs, lost productivity, team disruption, and eventual severance. At early-stage startups, one bad hire out of 10 employees is a 10% organizational failure rate.
Common trap
Founders hire for skills and ignore culture fit. A brilliant engineer who can't collaborate destroys 3x more value than they create. Equally dangerous: hiring friends because they're 'trusted' instead of hiring the best person for the role. Netflix famously fired founders' friends when they outgrew their roles โ it's painful but necessary.
Practical use
For every role, define: (1) The exact problem this person solves in the next 6 months, (2) The 3 must-have skills with evidence tests, (3) The culture values with behavioral interview questions. Use structured interviews with scorecards โ unstructured interviews are only 14% predictive of job performance.
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 Hiring Strategy when
For every role, define: (1) The exact problem this person solves in the next 6 months, (2) The 3 must-have skills with evidence tests, (3) The culture values with behavioral interview questions. Use structured interviews with scorecards โ unstructured interviews are only 14% predictive of job performance.
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.