Overview

Lecture URL: https://skill.re/learn/manager/resource-and-capacity-planning.php

AI FOR MANAGERS CERTIFICATION

AI-Assisted Use (Level 2) | Assisted Planning and Prioritization

LECTURE: Resource and Capacity Planning

Lesson 2.3 | Estimated Duration: ~17 minutes

Welcome to the AI for Managers certification program. I am your instructor, and today we are covering one of the essential lessons in the Assisted Planning and Prioritization module: Resource and Capacity Planning.

This is Lesson 2.3 in Level 2, the AI-Assisted Use track. Whether you are joining us as a new manager finding your footing, a seasoned director refining your approach, or a VP setting strategic direction for your organization, the material in this session is designed to meet you where you are and give you something immediately actionable.

In our previous lesson, we covered Prioritization Frameworks With AI. Today we build directly on that foundation. If any of those concepts feel uncertain, I would encourage you to revisit that material before we go further.

Before we begin, let me set expectations. This is not a passive lecture. I will ask you to think, to challenge assumptions, and to connect what we discuss to your own work. The managers who get the most out of this program are those who pause, reflect, and apply. So I encourage you to have a notepad ready, whether physical or digital, and to jot down ideas as they come to you.

Let us get started.

Lesson 2.3: Resource and Capacity Planning

Title

Resource and Capacity Planning: Using AI to Model Workload Distribution, Identify Capacity Gaps, and Draft Resource Requests

Purpose

This lesson teaches you how to use AI to analyze team capacity, model different staffing scenarios, and draft resource requests based on actual workload data. You'll learn to use AI for the analytical and drafting work while you provide the team dynamics knowledge and final decisions.

Why This Matters for Managers

The capacity challenge: Matching team capacity to workload is hard. You need to know: Are we over-committed? Under-utilized? What happens if we hire/lose someone? What does success look like for each team member?

What's at stake: Over-commitment leads to burnout, quality issues, and attrition. Under-utilization wastes resources. Getting this right improves retention, quality, and predictability.

The opportunity: AI can rapidly model scenarios, calculate capacity vs. workload, and help you articulate resource needs to leadership in data-driven terms.

Core Concepts

1. Capacity Planning Components

• Team size: How many people, in what roles?
  - Utilization rate: What % of time is allocated to billable/assigned work? (Usually 60-80% due to overhead, meetings, admin)
  - Current workload: What's planned for the next quarter?
  - Forecast workload: What's expected to come?
  - Velocity/productivity: How much work does your team actually complete per sprint/month?
  - Skill requirements: What roles/skills are needed?
  - Growth projections: Will workload grow? How?

1. Capacity Math

Available capacity (hours) = Team size x Hours per person x Utilization rate

Example:

• 5 engineers x 160 hours/month x 75% utilization = 600 available hours/month
  - Planned workload: 650 hours/month = 50 hours over capacity
  - Gap: Need 0.33 FTE or 1 contractor for overflow

1. Utilization Reality

Not all time is available for assigned work:

• Meetings, planning, admin: 15-25%
  - Support, bugs, interruptions: 10-20%
  - Training, professional development: 5-10%
  - Real utilization for new project work: 50-70%

AI can help you calculate; you know your team's actual patterns.

1. Capacity Planning Scenarios

• Current state: What's capacity today?
  - Optimistic: If we get everything done on schedule
  - Realistic: Accounting for normal delays and overhead
  - Pessimistic: If key person leaves, or major blocker hits

Practical Managerial Use Cases

Use Case 1: Staffing Request Justification

Scenario: You want to hire one more engineer. Leadership wants to know why. You need to make the case with data.

With AI:

1. Document: Current team size, planned workload for next 2 quarters, current capacity, forecasted growth
2. AI generates analysis and request
3. You review and customize with business context
4. Present to leadership with data-backed argument

Time savings: 2+ hours (analysis) to 30 minutes.

Use Case 2: Workload Rebalancing

Scenario: You notice one team member is consistently overloaded while another has capacity. You want to understand the imbalance and rebalance work.

With AI:

1. List each person: current projects/commitments, estimated hours per week, preferences
2. Ask AI: "Show me utilization by person. Highlight anyone >80% or
   - Feature A (2 engineers, 80% of quarter)
   - Feature B (2 engineers, 50% of quarter)
   - Maintenance/bugs (1 engineer, 100%)
   - Design work (1 designer, 100%)

Forecast Q2:

• Feature A: Continue (2 engineers, 50%)
  - Feature B: Launch & support (1 engineer)
  - Feature C: New project (3 engineers full-time)
  - Maintenance: 20% of 1 engineer
  - Design: 2 features (1 designer, 100%)

Current utilization:

• Engineers: 85% (slightly overloaded)
  - Designer: 95% (overloaded)
  - Growth forecast: +40% workload in Q3

`

Prompt:

> Analyze our team capacity. Current: 4 engineers, 1 designer. Q1 workload: 80% of 2 engineers, 50% of 2 engineers, 100% of 1 engineer maintenance = ~3.3 FTE engineering. Q2 forecast: 3 new features, ongoing maintenance = need ~3.8 FTE. Growth forecast: +40% workload Q3. Calculate: (1) Current utilization rate, (2) Q2 capacity gap, (3) When we'd need to hire to support growth. Create a one-page summary supporting a headcount request.

AI Output:

`

CAPACITY ANALYSIS & STAFFING SUMMARY

CURRENT STATE (Q1):

Team: 4 engineers @ ~75% available capacity per person = 3 FTE available

Current workload: 3.3 FTE committed

Utilization: 110% (OVERLOADED by 0.3 FTE)

Designer: 1 @ 95% utilization (OVERLOADED)

Q2 FORECAST:

Planned workload: 3.8 FTE engineering

Available capacity: 3 FTE

Gap: 0.8 FTE (SHORTFALL)

Current trajectory: No relief in sight

Q3 PROJECTION (40% workload growth):

Anticipated workload: 5.3 FTE

Available with current team: 3 FTE

Gap: 2.3 FTE

HEADCOUNT REQUEST JUSTIFICATION:

Current state: Team is 10% overloaded. Q2 gap: 0.8 FTE. Q3 gap: 2.3 FTE.

To support sustainable growth and maintain quality:

• Hire 1 engineer immediately (covers Q2 gap + 30% of Q3 growth)
  - Plan hire 2 engineer for Q3 (covers remaining Q3 gap)
  - Hire 1 contractor or 0.5 designer support for Q2/Q3 (design is at capacity)

ALTERNATIVE APPROACH:

• Hire 2 engineers now: Brings team to 6 engineers, can handle Q3 growth, allows for attrition
  - Cost: Higher but provides buffer and growth runway

RECOMMENDATION:

Hire 1 engineer now (address immediate crisis). Reassess in Q2 for additional hire based on actual Q3 demand.

Business case: 10% current overload is unsustainable; leads to burnout, quality issues, attrition. Q2 gap delays planned features or forces crunch. Proactive hiring enables sustainable growth and on-time delivery.

`

Manager's Review:

• Math is correct
  - Overload situation is clear
  - ~ "Immediate crisis" is strong language; maybe not accurate
  - Two scenarios presented (conservative vs. proactive)
  - ~ Missing: Cost impact, time-to-hire
  - Clear recommendation

Manager's Customization:

Change "immediate crisis" to "unsustainable load." Add: "If we hire immediately (Feb), engineer onboards by April, in time for Q2 crunch. If we wait, we're already overloaded."

Add cost: "Engineering hire: $X salary + $Y onboarding cost. Conservative ROI: prevents 1 engineer attrition (replacement cost $Z)."

Final Staffing Request (to Leadership):

`

HEADCOUNT REQUEST: 1 ENGINEER

Current Situation:

Our team is 10% overloaded. Q2 forecast shows a 0.8 FTE gap (27% overload). Q3 growth forecast suggests 2.3 FTE gap (77% overload).

Request:

Hire 1 additional engineer immediately (target start: April).

Business Justification:

1. Prevents quality degradation (overloaded teams cut corners)
2. Reduces attrition risk (overload is primary burnout driver)
3. Enables on-time delivery of committed features (Feature C launch needs 3 engineers)
4. Provides buffer for growth

Cost-Benefit:

• Salary + onboarding: ~$X + $Y (Q2)
  - ROI: Prevents one engineer attrition (replacement cost ~$Z), ensures on-time delivery
  - Upside: Positions team for 40% Q3 growth

Timeline:

• Hire now: Engineer onboards April, productive by June
  - Wait until Q2: We're already overloaded; engineer won't catch up until Q3
  - Delay risk: Missed deadlines, team morale, potential departures

Recommendation:

Approve hire. Begin recruitment immediately.

`

Lesson: AI calculated capacity and gaps clearly. Manager added business context (cost, attrition impact, timing). Result is a compelling, data-driven request.

Example 2: Workload Rebalancing

Current Workload by Person:

`

Alice: 90% utilization

• Feature A (60%, primary engineer)
  - Maintenance (20%)
  - Meetings, overhead (10%)

Bob: 60% utilization

• Feature B (40%)
  - Learning/dev (20%)

Charlie: 75% utilization

• Feature A support (30%)
  - Tech debt/refactor (30%)
  - Maintenance (15%)

Diana: 85% utilization

• Feature B (50%)
  - Maintenance (25%)
  - Support (10%)

Target: 70-75% for optimal productivity and growth room

Current state: Unbalanced (Alice overloaded, Bob underutilized)

`

Prompt:

> Analyze utilization by person and suggest rebalancing to get everyone to 70-75%. Current: Alice 90%, Bob 60%, Charlie 75%, Diana 85%. Projects: Feature A (needs 90 engineer-hours), Feature B (needs 70 engineer-hours), Maintenance (30 engineer-hours), Tech debt (20 engineer-hours). Suggest: who should do what, and target utilization.

AI Output:

`

REBALANCING RECOMMENDATION

CURRENT STATE (UNBALANCED):

Alice: 90% (OVERLOADED, burnout risk)

Bob: 60% (UNDERUTILIZED)

Charlie: 75% (healthy)

Diana: 85% (slightly overloaded)

PROPOSED REBALANCING (70-75% target):

Alice: 75% utilization

• Feature A primary (40% = 64 hours)
  - Mentoring Bob on Feature A (10% = 16 hours)
  - Overhead (25% = 40 hours)

-> Reduction: 15% (removes maintenance, reduces overload)

Bob: 72% utilization

• Feature A (40% = 64 hours, with Alice mentoring)
  - Learning (12% = 19 hours)
  - Overhead (20% = 32 hours)

-> Increase: 12% (grows responsibility, develops skills)

Charlie: 72% utilization

• Tech debt/refactor (40% = 64 hours, increased focus)
  - Maintenance (20% = 32 hours)
  - Overhead (12% = 19 hours)

-> Stable, but takes on more tech debt

Diana: 73% utilization

• Feature B primary (50% = 80 hours)
  - Maintenance (10% = 16 hours)
  - Overhead (13% = 21 hours)

-> Stable, clearer focus

IMPACT:

• Feature A: Alice (primary) + Bob (learning + growing), reduces individual load
  - Feature B: Diana focused and confident
  - Maintenance: Distributed across Charlie, Diana (reduced from Alice)
  - Tech debt: Gets dedicated time (Charlie) for quality improvements
  - Growth: Bob develops Feature A expertise; Alice mentors (leadership skill)

RISKS & MITIGATION:

• Bob taking on Feature A: Needs Alice's mentoring. Block 2 hours/week.
  - Charlie's tech debt: May not feel visible/valued. Communicate importance.
  - Feature A timeline: With Bob learning, may be slightly slower. Plan 10% buffer.

RECOMMENDATION:

Implement for next sprint. Check in after 1 sprint; adjust if needed.

`

Manager's Review:

• Clear recommendations
  - Addresses overload and underutilization
  - ~ Bob learning Feature A: Is that realistic given current complexity?
  - Identifies mentoring needs
  - Calls out risks

Manager's Conversation:

"Alice, I want to reduce your load because you're at 90%. This means you'd shift some of your Feature A work to Bob, and you'd mentor him. Would that be motivating for you?

Bob, I have a growth opportunity: taking on more of Feature A with Alice's help. Interested?

Charlie, I want to invest in tech debt because our codebase needs it. You'd own this focus. It's not glamorous, but it's critical for our ability to move fast."

All say yes. Plan implemented.

Lesson: AI suggested rebalancing. Manager contextualized with team relationships and growth opportunities. Result is a change that improves utilization, reduces overload, and develops people.

Anti-Patterns / Misuse Risks

Anti-Pattern 1: Capacity Plans Divorced from Reality

Risk: You create beautiful utilization charts that don't reflect how work actually happens.

Why it happens: Assuming 75% utilization, but reality is 50% due to meetings, interruptions, context-switching.

What goes wrong: Plans assume more capacity than you actually have. You overcommit.

How to avoid: Track your actual utilization. If meetings eat 30% of time, plan for 45% real utilization, not 75%.

Anti-Pattern 2: Not Accounting for Ramp-Up Time

Risk: You hire someone new and expect them to contribute full capacity immediately.

Why it happens: Math says 1 FTE = 160 hours/month, so you assign 160 hours of work.

What goes wrong: New hire spends 4 weeks learning. Existing team supports them. Capacity actually decreases initially.

How to avoid: Plan ramp-up: new hire at 20% capacity Week 1, 40% Week 2, 60% Week 3, 75% Week 4+.

Anti-Pattern 3: Ignoring Skill-Based Constraints

Risk: You balance workload by hours, but people have different skills and can't swap work.

Why it happens: Treating engineers as interchangeable units.

What goes wrong: You say "Bob has capacity" but the work needs frontend skills and Bob does backend.

How to avoid: Model capacity by skill/specialization, not just headcount.

Anti-Pattern 4: No Buffer for Unknowns

Risk: You plan at 100% of capacity, leaving no room for surprises.

Why it happens: Wanting to maximize utilization; treating planning numbers as fact.

What goes wrong: One urgent bug hits, or one person gets sick. The plan breaks.

How to avoid: Plan for 70-75% utilized capacity, leaving 25-30% for unknowns, learning, and growth.

Human Judgment Checkpoints

Before finalizing a capacity plan:

1. Reality Check: Does this match your actual team pace?

• Are meeting/admin hours realistic?
  - Do utilization numbers feel right?

1. Skill Check: Is work allocatable by skill?

• Can this person actually do this work?
  - Does the team have needed skills?

1. Growth Check: Are you planning for growth and learning?

• Or just maximizing short-term utilization?

1. Sustainability Check: Can the team sustain this load?

• 85%+ utilization long-term leads to burnout
  - 50% or less = waste/morale issue

1. Contingency Check: What's your buffer for unknowns?

• Unexpected bugs?
  - Sick leave, PTO?
  - Urgent requests?

Responsible AI Considerations

Protecting Team Wellbeing

• Don't use AI-generated capacity plans to push people beyond sustainable limits.
  - 80%+ sustained utilization leads to burnout and attrition.

Honesty About Utilization

• Be realistic about utilization rates. Don't inflate them to justify overcommitting.

Transparency

• Share capacity constraints with team and stakeholders.
  - If you're overloaded, say so. Don't hide behind AI analysis.

Practice / Reflection Prompts

Exercise 1: Current Capacity Analysis

Map your team:

1. List each person, projects, estimated hours per week
2. Calculate utilization percentage
3. Identify over/under-utilized people
4. Ask: Is this sustainable? Are there imbalances?

Exercise 2: Workload Rebalancing

Identify one person who's overloaded and one underutilized:

1. What work could move?
2. What skills are required?
3. How would you structure the transition?
4. What would the impact be?

Exercise 3: What-If Scenario

Model a growth scenario:

1. If workload grows 30%, what's the capacity gap?
2. When would you need to hire?
3. How would you staff to handle growth?

Exercise 4: Hiring Case

Build a staffing request:

1. Current capacity vs. workload
2. Forecast gap
3. Cost-benefit analysis
4. Timing and recruitment plan

Key Takeaways

1. Know your team's actual utilization. Don't assume 80%; measure what you actually achieve.
2. Plan for 70-75% utilization. This leaves room for growth, learning, and unknowns.
3. Account for real constraints. Meetings, admin, context-switching eat time. Plan for it.
4. Skill matters as much as headcount. You can't reallocate work if people lack skills.
5. Sustainability beats efficiency. Overloading the team to maximize utilization leads to burnout and attrition.
6. Use AI for analysis, not final decisions. The math is valuable; your judgment about team dynamics is critical.
7. Plan ramp-up for new hires. Don't expect full productivity in week one.

Terms / Glossary Items

Utilization rate: Percentage of available time allocated to assigned work.

Available capacity: Total hours team could work on assigned projects (headcount x hours x utilization).

Workload: Total hours of work needed; burndown or backlog.

Capacity gap: The difference between available capacity and workload (positive = overload, negative = underutilized).

Ramp-up period: Time new hire takes to become fully productive.

Skill-based constraint: Work that can only be done by people with specific skills; limits reallocation flexibility.

Related Lessons

• Lesson 2.1: Creating Project Plans (depend on accurate capacity)
  - Lesson 2.2: Prioritization Frameworks (priorities drive workload allocation)
  - Lesson 2.4: Risk Identification and Mitigation (capacity risk assessment)
  - Lesson 4.1: Verification Workflows (tracking actual vs. planned)

Next: Move to Lesson 2.4 to learn risk identification and mitigation.

[SYNTHESIS AND APPLICATION]

Let us step back and look at the bigger picture of what we have covered in this session on Resource and Capacity Planning.

The concepts here are not abstract frameworks meant to sit in a binder on your shelf. They are practical tools for the decisions you make every day as a manager. Whether you are leading a small team or a large department, whether you work in technology, finance, healthcare, education, or any other sector, the principles we discussed apply to your work right now.

Here is what I want you to take away from this session:

First, the conceptual understanding. You now have a clearer mental model of resource and capacity planning and how it fits into the broader landscape of AI-augmented management. This mental model is what allows you to make good decisions rather than reactive ones.

Second, the practical application. We walked through specific scenarios, examples, and frameworks that you can apply in your work this week. Not next quarter. This week. I want you to identify one specific situation in your current work where you can apply what we discussed today.

Third, the judgment dimension. Perhaps most importantly, we discussed when and how to exercise human judgment. AI is a powerful tool, but it requires an informed, thoughtful manager at the helm. That is you. Your judgment, your context awareness, your understanding of your team and your organization, those are irreplaceable.

[REFLECTION EXERCISE]

Before we close, I would like you to spend two minutes, just two minutes, on this reflection:

Think about your work this past week. Identify one task, one decision, one communication where the concepts from today's lesson would have changed your approach. What would you have done differently? What would the outcome have been?

Write that down. That connection between concept and practice is where real learning happens.

[CLOSING REMARKS]

In our next lesson, we will explore Risk Identification and Mitigation, which builds directly on what we have covered today. I would encourage you to complete the reflection exercises before moving on, as they will prepare you for the next set of concepts.

This has been Lesson 2.3: Resource and Capacity Planning, part of the Assisted Planning and Prioritization module in Level 2: AI-Assisted Use of the AI for Managers certification.

Remember: the goal is not to know more about AI. The goal is to be a better manager because of how you use AI. Those are very different things, and this program is designed for the latter.

Thank you for your time, your attention, and your commitment to growing as a leader in an AI-transformed workplace. I look forward to our next session together.

END OF TRANSCRIPT

AI for Managers Certification Program

Level 2: AI-Assisted Use | Assisted Planning and Prioritization | Lesson 2.3

A SkillsClinic initiative by No Worker Left Behind and The Work Company.

Duration: ~17 minutes | Word Count: ~2646