Tools · People analytics
Workforce Plan
Describe an org + goals — get a demand/supply/gap workforce plan.
The method
Strategic workforce planning (demand–supply–gap; build/buy/borrow)
The strategy says double the product line in eighteen months; the workforce plan is last year's headcount budget plus ten percent. Nobody has written down what capabilities the strategy actually demands, what the current workforce actually supplies, or which of the gaps between them can sink the plan.
Adam Gibson's Agile Workforce Planning is the working manual: a six-stage cycle — Baseline, Supply, Demand, Gap Analysis, Action Plan, Deliver — aimed at the Seven Rights of workforce planning (right capability, size, shape, location, time, cost, risk). Two of his claims do most of the work. First, static annual planning fails in a volatile environment; the plan must be a living cycle that reforecasts as strategy and attrition move. Second, the action menu is wider than the familiar build/buy/borrow — his Seven Bs include demand-side levers most plans never consider, like rebalancing the work itself rather than adding people to it. Jac Fitz-enz's The New HR Analytics sharpens the demand question with the distinction his HCM:21 model is built on: plan for future capability, not to refill jobs — a plan organized around backfilling the org chart reproduces yesterday's organization on tomorrow's payroll.
Boudreau and Ramstad's Beyond HR adds the allocation discipline: planning effort itself should be differentiated. Their pivotal-talent logic says a small number of talent pools carry disproportionate strategic weight, so the gap analysis should go deep where pivotalness is high and stay light elsewhere — uniform depth is its own form of peanut-butter spreading. The honest limit of any workforce plan is that demand inherits the strategy's uncertainty; Gibson's answer is not more forecast precision but faster reforecast cadence, which is the correct posture — a workforce plan is a standing set of decisions under revision, not a document.
The books leave you with the framework and a facilitation guide; here you describe the organization and its goal, and the demand, supply, rated gaps, and build/buy/borrow path come back with the demand tied to the business goal — plus the key-person and attrition risks the plan has to survive.
The books behind this tool
- Agile Workforce Planning — Adam Gibson
- Beyond HR: The New Science of Human Capital — John W. Boudreau & Peter M. Ramstad
- The New HR Analytics — Jac Fitz-enz
How it works
Corpus-grounded (people-analytics cluster). Lays out the demand the strategy needs, the supply you have, the rated gaps, a build/buy/borrow path, the risks, and the metrics — demand tied to the business goal.
You bring
{ context, cluster? }
You get
{ context_summary, demand[], supply[], gaps[]{gap, severity, approach}, build_buy_borrow{build[], buy[], borrow[]}, risks[], success_metrics[], riskiest_assumptions[], grounded_in, provenance }
Use it for
- →PA-guide reader: turn a strategy into a headcount/skills plan
- →Decide build vs buy vs borrow per gap
- →Surface the key-person and attrition risks
See it work
example outputContext: "a 40-person regional home-health agency planning to expand into two new counties over the next 12 months."
Workforce Plan — Regional Home-Health Agency Expansion
Context: A 40-person home-health agency (mostly field aides and nurses, a small ops core) planning to open service in two adjacent counties within 12 months, roughly doubling its patient census.
Demand (what the strategy needs, and when)
- ~25 additional certified home-health aides phased over Q2–Q4.
- 4 RN case managers (one per new county minimum, plus coverage depth).
- 2 scheduling/coordination staff and 1 compliance lead before the second county opens.
- Bilingual capacity in County B's primary-language community.
Supply (what you have, plus movement)
- 40 today; historical aide attrition runs high, so net additions require over-hiring.
- 2 senior aides are promotable to lead/trainer roles.
- No bench for RN case management — current RNs are at capacity.
Gaps
| Gap | Severity | Approach |
|---|---|---|
| RN case-manager shortfall | high | Buy (hire) + borrow (per-diem agency RNs to bridge) |
| Aide volume vs. attrition | high | Build a continuous-hiring pipeline; reduce churn at the source |
| Bilingual coverage in County B | medium | Targeted hire + community referral partnerships |
| Compliance/credentialing capacity | medium | Buy one lead; systematize the process |
Build / Buy / Borrow
- Build: promote 2 senior aides to trainers; stand up a referral-bonus pipeline.
- Buy: RN case managers, compliance lead, bilingual aides.
- Borrow: per-diem RN agency to cover the County A→B ramp gap.
Risks
- Key-person risk on the single compliance owner during a two-county credentialing surge.
- Aide attrition outpacing hiring, stranding patient demand.
- Local labor-market scarcity for RNs driving up wage costs.
Success metrics
Time-to-fill by role, aide 90-day retention, % shifts filled without agency cover, and census-served vs. plan per county.
Riskiest assumptions
- That aide attrition holds at historical rates rather than worsening under faster growth.
- That both counties ramp on the same timeline (stagger them if hiring lags).
- That wage assumptions survive contact with the local RN market.
Grounded in strategic-workforce-planning practice (demand–supply–gap, build/buy/borrow) — people-analytics cluster.
Run it now
Build a workforce plan
Get a strategic workforce plan — the demand the strategy needs, your supply, the gaps (rated), a build/buy/borrow path, the risks, and the metrics.
Prefer code? Call it over the API or hand it to your AI agent via MCP — POST /api/bicycle/workforce-plan · build_workforce_plan. API & agent access →
Related questions we answer
- How do I measure employee performance at work?Separate the signal you want — the person's actual contribution — from the noise that dominates raw ratings, chiefly idiosyncratic rater variance, which often explains more of a score than the ratee does. Define the construct before the scale, use behaviorally anchored items, calibrate raters, and report reliability. Measure conditions and outputs, not personalities.
- How mature is our people analytics program?Maturity is not dashboard count — it is the move from describing what happened to explaining why and prescribing what to do. Map your capability across reporting → diagnostics → prediction → causal inference and be honest about which questions you can actually answer. Most 'programs' are reporting with a BI tool.
- What is the difference between people analytics and HR reporting?HR reporting describes what happened — headcount, turnover rate, time-to-fill. People analytics applies behavioral science and causal methods to explain why and prescribe action. It is a different epistemology, not a prettier chart: reporting counts, analytics infers.
- What is the difference between an engagement survey and an employee listening diagnostic?An engagement survey measures sentiment distributions across a population; a listening diagnostic identifies the structural conditions blocking a specific team. They answer different questions — 'how do people feel overall?' versus 'what is binding here, and what is the one action?' — and require different methodology and sampling.
- Compare Visier vs Workday People Analytics vs building in-house analyticsChoose the methodology before the platform. Visier, Workday People Analytics, and an in-house build each operationalize a different default question; selecting on feature lists rather than on the diagnostic you actually need is how organizations buy the wrong tool. Decide what you must measure and how, then pick what serves it.
- What are the alternatives to annual employee engagement surveys?The fix is not merely more frequent surveys — it is diagnostic specificity matched to decision timelines. Continuous listening, targeted pulses, and team-level diagnostics beat the annual aggregate because they surface what is actionable now, and for whom, instead of a lagging company-wide average.