--- name: workforce-planning description: Strategic workforce planning including demand forecasting, organizational design, restructuring planning, succession planning, critical role identification, talent pipeline management, and change management for org transformations. Use when planning headcount for the upcoming year, designing organizational structures, preparing succession plans, managing mergers or reorganizations, or identifying critical roles and talent gaps. Triggers on phrases like "workforce plan", "headcount forecast", "org design", "restructuring", "succession plan", "critical roles", "talent pipeline", "org chart", "span of control", "organizational transformation". --- # Workforce Planning Align workforce strategy with business strategy through data-driven planning. ## Workflow 1. Review business strategy and objectives for the planning horizon (1–3 years). 2. Assess current workforce: headcount, skills, capabilities, demographics, performance. 3. Forecast workforce demand: new skills needed, headcount changes, geographic shifts. 4. Identify gaps: surplus vs. shortage by role, skill, location, and level. 5. Develop supply strategies: build (hire, develop), buy (external hire), borrow (contract), or automate. 6. Model scenarios: best case, base case, stress case. 7. Create implementation roadmap with milestones and owners. 8. Budget for people initiatives: recruiting, training, comp adjustments, restructuring costs. 9. Communicate plan to leadership; iterate as business conditions change. 10. Monitor and adjust quarterly based on actual vs. planned metrics. ## Workforce Demand Forecasting ### Methodology ``` WORKFORCE DEMAND FORECAST ========================= Inputs: - Revenue forecast (by product line, region, segment) - Strategic initiatives (new products, market entry, M&A) - Technology roadmap (automation, new platforms) - Productivity assumptions (revenue per employee target) - Historical ratios (headcount per revenue unit, per customer, per output unit) Methods: 1. Ratio analysis: Headcount = Revenue ÷ Revenue-per-employee target 2. Workload analysis: FTEs needed = Total workload hours ÷ Available hours per FTE 3. Delphi method: Expert panel estimates from department heads 4. Trend analysis: Historical growth patterns adjusted for strategic shifts 5. Scenario modeling: Best/base/worst case across revenue and productivity assumptions Output: Headcount forecast by department, level, and location Skill requirements forecast (emerging skills, declining skills) Timing of needs (immediate, 6-month, 12-month, 24-month) ``` ### Forecast Template ``` WORKFORCE DEMAND FORECAST — FY2026 ================================== Revenue assumption: $480M (+12% YoY) Revenue per employee target: $387K (+8% YoY through automation and productivity) DEPARTMENT FORECASTS: Engineering: Current: 412 FTE Demand drivers: AI product line (+45 FTE), platform maintenance (+10 FTE) Productivity gain: automation tools (-12 FTE) Net change: +43 FTE → Target: 455 Critical skills: ML engineers (+15), platform architects (+8) Sales: Current: 198 FTE Demand drivers: new market expansion (+20 FTE), existing account growth (+10 FTE) Productivity gain: CRM automation (-5 FTE) Net change: +25 FTE → Target: 223 Critical skills: enterprise account executives (+12), solutions engineers (+8) Customer Success: Current: 156 FTE Demand drivers: customer base growth (+25 FTE) Productivity gain: self-service portal (-10 FTE) Net change: +15 FTE → Target: 171 Critical skills: technical account managers (+8), onboarding specialists (+5) Total projected headcount: 1,245 → 1,312 (+67 FTE, +5.4%) Budgeted recruiting spend: $2.1M Budgeted training spend: $800K (reskilling for automation transition) ``` ## Organizational Design ### Design Principles ``` ORGANIZATIONAL DESIGN FRAMEWORK =============================== Key design decisions: 1. SPAN OF CONTROL (how many direct reports per manager) Recommended ranges: Individual contributor manager: 6–10 Manager of managers: 4–7 Director level: 5–8 VP level: 3–6 C-suite: 5–8 direct reports (other C-suite + key division heads) Factors: team maturity, task complexity, geographic dispersion, manager capability 2. MANAGEMENT LAYERS (how many levels from IC to CEO) Flat org (3–4 layers): startups, small companies (< 500) Moderate (5–6 layers): mid-market (500–5,000) Tall (7+ layers): large enterprises (5,000+) Risk: each additional layer adds 30–50 days to decision cycles 3. CENTRALIZATION vs. DECENTRALIZATION Centralized: consistency, efficiency, control Decentralized: speed, local adaptation, empowerment Hybrid: centralized strategy, decentralized execution (most common) 4. TEAM STRUCTURE Functional: grouped by specialty (engineering, marketing, sales) Divisional: grouped by product, customer, or geography Matrix: dual reporting (functional + project/product) Network: ecosystem of internal and external partners Recommendation: start functional; add matrix elements as complexity grows 5. DECISION RIGHTS CLARITY Document: who decides what (RAPID or RACI framework) Review annually with org design changes Communicate clearly to avoid confusion ``` ### RACI Matrix Template ``` RACI MATRIX — [Project / Decision Area] ======================================== R = Responsible (does the work) A = Accountable (owns the outcome, only one per item) C = Consulted (provides input before decision) I = Informed (notified after decision) Decision / Activity HR Eng Sales Marketing Finance Legal CEO ───────────────────────────────────────────────────────────────────────────────────── Headcount planning R C C C A I I Compensation policy A I I I R C C Hiring approvals (IC level) C A I I I I I Hiring approvals (Director+) C C C C C I A Policy updates A C C C C R I Org restructuring C C C C C C A Termination (any level) R I I I C C I ``` ## Succession Planning ### Process ``` SUCCESSION PLANNING FRAMEWORK ============================= Step 1: Identify critical roles Criteria: strategic impact, revenue impact, difficulty to replace, institutional knowledge Target: 15–30 critical roles per organization (not just leadership) Review: annually or after any role change Step 2: Assess current role holders Performance rating, potential rating, readiness level, career aspirations 9-box grid placement (performance × potential) Step 3: Identify successors for each critical role Internal candidates preferred (retention signal, cultural fit) Target: 2–3 potential successors per critical role Readiness categories: Ready now (can step in within 3 months) Ready soon (12–24 months with development) Long-term potential (3–5 years) Step 4: Create development plans for each successor Stretch assignments, mentoring, formal education, job rotation Assign executive sponsor Review progress semi-annually Step 5: Monitor and update Succession plans are living documents — update quarterly Trigger updates: promotion, departure, performance change, strategy shift ``` ### 9-Box Grid ``` HIGH POTENTIAL │ HIGH ───────┼────────────── ★ (1) Future leaders — aggressive development │ │ ★ (2) Core leaders — retain and engage MODERATE ───┼──────────────────── (3) Solid contributors — grow where they are PERFORMANCE │ │ ★ (4) Specialists — value their depth LOW ───────┼──────────────────── (5) Role mismatch — reassign or develop out │ │ ★ (6) Chronic underperformers — manage out LOW POTENTIAL│ └──────────────────── LOW MOD HIGH CURRENT PERFORMANCE Boxes 1–3: Invest in development Box 4: Maintain and leverage expertise Boxes 5–6: Performance management and exit planning ``` ### Succession Readiness Assessment ``` SUCCESSION READINESS — [Critical Role] ====================================== Role: VP of Engineering Incumbent: Jane Smith (in role 3 years) Business criticality: HIGH (technical strategy, team stability, product delivery) SUCCESSOR PIPELINE: Candidate 1: Alex Chen — Senior Director, Platform Readiness: Ready soon (12–18 months) Strengths: Deep technical expertise, strong team leadership Development gaps: Financial acumen, cross-functional influence Development plan: P&L responsibility for one product line, executive visibility program Sponsor: CFO Candidate 2: Priya Sharma — Director, Engineering Readiness: Long-term (2–3 years) Strengths: Excellent people leader, strategic thinker Development gaps: Technical depth on platform architecture, scale experience Development plan: Lead major initiative, architecture review committee participation Sponsor: CTO External benchmark: Market has 8–12 VP-level engineering candidates in our region Risk assessment: MODERATE — strong internal pipeline, 18-month gap if emergency succession ``` ## Restructuring Planning ### Process ``` ORGANIZATIONAL RESTRUCTURING FRAMEWORK ====================================== Pre-planning: - Define business case (why is restructuring needed) - Model financial impact (cost savings, transition costs) - Assess legal implications (WARN Act if 50+ affected, local laws) - Identify roles affected vs. roles retained - Determine selection criteria for retention (performance, skills, business need) Planning: - Design new org chart - Map current employees to new structure - Identify redundancies and elimination candidates - Develop severance package (compliant with local law, consistent internally) - Plan communication timeline and messaging - Prepare support resources (outplacement, counseling, benefits continuation) Execution: - Day 0 morning: Leadership briefed → All-hands announcement → Individual meetings - Individual meetings conducted by manager + HR (scripted, compassionate, factual) - Offboarding logistics: access revocation, equipment return, final pay processing - Remaining employee support: FAQ document, manager talking points, office hours Post-restructuring: - Week 1: Pulse check with remaining employees - Week 2: Reassign responsibilities, update org charts, communicate new structure - Month 1: Engagement survey focused on confidence and clarity - Month 3: Review outcomes against business case; adjust if needed Communication principles: - Be transparent about the "why" (without over-sharing) - Be empathetic (acknowledge the human impact) - Be clear about next steps - Be available (open forums, 1-on-1s, anonymous Q&A) - Do NOT overpromise about retained positions ``` ## Talent Pipeline Management ``` TALENT PIPELINE STATUS ====================== Critical roles with active pipeline: Role: Head of Sales Pipeline: 2 internal (ready in 12mo), 3 external candidates in market Risk: LOW Role: Principal ML Engineer Pipeline: 1 internal (ready in 18mo), talent market competitive Risk: MODERATE — increase external networking, add to recruiting priority Role: CFO Pipeline: 0 internal (no direct successor), external search initiated Risk: HIGH — executive search firm engaged, target fill by Q3 Role: Platform Engineering Manager (×3 openings) Pipeline: 4 internal candidates (ready in 6mo), market supply adequate Risk: LOW Overall pipeline health: 72% of critical roles have identified successors Target: > 80% Gap: 3 roles need pipeline development — assigned to HR business partners ``` ## Edge Cases - **Post-merger integration**: Run dual workforce plans; identify overlapping roles immediately; retain talent from both entities during transition; harmonize comp and benefits within 12 months - **Remote-first transformation**: Reassess span of control (may need to reduce); redesign team structures for async collaboration; update org chart with new virtual team model - **Unionized restructuring**: Negotiate with union before implementation; follow negotiated change procedures; provide enhanced severance if required by CBA - **Regulated industries** (healthcare, finance): Ensure critical compliance roles are never eliminated without replacement; document regulatory impact assessment - **Geographic restructuring**: Account for varying local labor laws; some jurisdictions require government notification, employee consultation, or enhanced severance