— Organisation & Workforce

Workforce scenario comparison

Runs gap analysis for base, upside and downside workforce scenarios against org and skills evidence, bucketing and comparing what changes between them.

  • Organisation & Workforce
  • Traceable reasoning
  • Runs anywhere
Preview methodology

2–3 weeks → ~40 minutes

For a full population, not a sample

No coding required

Input
Strategy, plan or forecast documents
Output
Gap analysis per scenario, bucketed and compared
Runs in
Skillsize · ChatGPT · Claude · Copilot
Export
SKILL.md · MCP
Time saved
~2–3 weeks per run

— USE CASES

What people use Workforce scenario comparison for

Planning under uncertainty

Show the workforce implications of three trading assumptions instead of committing to one forecast.

Board-level planning conversations

Present the gap and cost consequence of each scenario side by side.

Trigger planning

Identify the decisions that change between scenarios and when they must be taken.

What it works from

  • Strategy, plan or forecast documents
  • Org map, team and skills evidence
  • The scenario assumptions to model

What you get back

  • Gap analysis per scenario, bucketed and compared
  • The differences between scenarios named explicitly
  • A scenario comparison table for an exec pack

— HOW IT BEHAVES

How Workforce scenario comparison produces its result

The mechanics behind this specific template — what it reads, what it calculates, and where a human stays in the loop.

Scored against your criteria

Each role is assessed against criteria you control and weight, so the same standard applies to every role in the organisation in scope.

The gap named and sized

What the organisation in scope requires and what it currently has are set against each other role by role, so each gap is quantified rather than described in general terms.

Roles banded, not argued

Every role lands in a defined band, so thresholds you set decide the outcome instead of whoever is interpreting it that day.

Capability read from the evidence

Skills and requirements are read out of org data, role documentation and headcount exports as structured data rather than inferred from job titles.

Grounded in your own context

Your strategy, standards and prior work are loaded first, so conclusions about the organisation in scope are anchored to your situation.

Anchored to your actual structure

Analysis runs against your real reporting lines and roles rather than an assumed org shape.

Why this is expensive by hand

In organisation & workforce work, workforce scenario comparison is one of those tasks that looks straightforward until you are three documents deep and the details stop agreeing with each other. Planning under uncertainty is the typical trigger — show the workforce implications of three trading assumptions instead of committing to one forecast. Get it right and the conclusion holds up in the room; get it rushed and it gets picked apart. Either way it costs roughly 2–3 weeks of experienced attention.

How this Skill produces it

Here the same job runs as a Skill. Your material goes in; gap analysis per scenario, bucketed and compared comes out, alongside the differences between scenarios named explicitly. The judgement is built in — how items are broken up, what standard they are held to, and where the run stops for a human review. In effect, 2–3 weeks of senior time compresses into ~40 minutes — and the output is comparable across clients, quarters and colleagues instead of shaped by whoever ran it.

Who it's for

  • Org design and workforce planning leads
  • COOs and functional leaders reshaping teams
  • Transformation consultants sizing people impact
  • HR business partners supporting redesign

Run it in Skillsize — or export it anywhere

Workforce scenario comparison exports as a structured SKILL.md file and is MCP-ready, so the same method runs in ChatGPT, Claude, Copilot or your own AI products. Adapt it to your methodology, and the intelligence stays yours — not locked to one vendor.

ChatGPTClaudeCopilotAI Products (MCP)