Capacity Mapping¶
Method — instantiates Implementation Feasibility Alignment
Compares required capabilities and resources against what implementing actors actually possess or can build in time.
Capacity Mapping lays the design's demands side by side with the implementers' actual stock and marks each line as have it, can build it in the window, or gap. It is a supply-versus-demand ledger of who and what: the skills, authority, staffing pattern, equipment, money, and time a design silently assumes, set against the free capacity that really exists and the capacity that can be created before the design must run. Its defining move is to refuse the phrase "we'll figure out staffing later" — it forces the required capabilities into a list now, prices what it costs to close each gap, and flags the one gap that binds. Where a routine-fit study asks whether the design slots into how work already flows, Capacity Mapping asks the blunter prior question: are the hands, skills, and budget even there to do it at all?
Example¶
A county wildland-fire agency wants to adopt night-time drone thermal mapping so incident commanders get fresh perimeter imagery before the morning shift. The concept is sound; the question is whether the county can carry it before fire season. Capacity Mapping lays out the demand: six certified night-UAS pilots (they have two), eight thermal-capable airframes (they have three), and analysts who can turn a raw flight into a crew-ready briefing inside thirty minutes (they have none dedicated). Each line gets a verdict — pilots are buildable (three can be certified in an eight-week course), airframes are buildable (leasable), analysts are a structural gap (no one on staff has the training and hiring runs six months).
The ledger's payoff is the binding gap it exposes: imagery the crews can't use fast enough is worthless, so the analyst shortfall — not the drones — is what decides scope. The map triggers a scope adjustment: launch in the two divisions that share one trained analyst this season, and stage the countywide rollout for next year once analyst capacity is built. That is a very different conclusion from "buy more drones," and it is the map, not the enthusiasm, that produced it.
How it works¶
- Enumerate demand. Read the design and list every capability and resource it requires — skills, certifications, decision authority, headcount, equipment, budget, and calendar time.
- Inventory real supply. Record not gross headcount but free capacity: people already fully allocated do not count, and equipment already committed elsewhere does not either.
- Classify each line. Mark have, buildable in the window, or structural gap, and for buildables, cost the build in time and money.
- Find the binding gap. Identify the single requirement whose shortfall caps the whole design, since that is the one that should drive scope.
- Feed the scope rule. Convert the binding gap into a narrow / phase / fund / pause decision rather than a heroic assumption.
Tuning parameters¶
- Demand granularity — one lumped "we need a team" versus an itemized skills-and-hours breakdown. Finer granularity surfaces hidden roles but costs effort and risks false precision.
- Build-window horizon — how far out "buildable in time" reaches. A generous horizon rescues more gaps but bets on a longer runway holding.
- Slack buffer — how much free capacity you insist on above the bare requirement. More buffer absorbs surprises but makes fewer designs look feasible.
- Buildable-vs-structural threshold — where you draw the line between a gap you can train through and one you must hire or redesign around.
- Refresh cadence — a one-shot map or a re-run as builds land and allocations shift.
When it helps, and when it misleads¶
Its strength is dragging invisible labor[1] and unfunded maintenance into daylight — the analyst nobody budgeted, the maintenance hours assumed to be free, the authority the design needs but no one holds. It turns "we can staff this" from an assertion into a checked ledger, and it makes scope a consequence of real capacity rather than of ambition.
Its central failure mode is counting nominal capacity instead of free capacity: a name on the org chart is not an available person if that person is already at 100%, and a piece of equipment on the asset list is not available if it is committed elsewhere. A map built on gross headcount will always look feasible and always be wrong at rollout. It also tends to under-price the capabilities that resist counting — tacit judgment, relationship capital, the senior operator everyone quietly depends on. The discipline that keeps it honest is to inventory slack, not gross totals, and to re-run the map as commitments shift rather than trusting the first snapshot.
How it implements the components¶
capability_requirement— its core act: enumerating and sizing the skills, authority, and staffing the design needs and matching each to a real holder or a build plan.resource_constraint— the supply side of the ledger, inventorying budget, equipment, and time limits as hard or buildable.scope_adjustment_rule— the binding gap is converted into a narrow / phase / fund / pause decision.
Capacity Mapping says nothing about whether the work threads into how the setting already operates; whether the design fits existing handoffs, timing, and tools (workflow_fit), the routine landscape it lives in (implementation_context), or the incentives that make people follow it (incentive_fit) is mapped by its method-twin Workflow Fit Analysis.
Related¶
- Instantiates: Implementation Feasibility Alignment — Capacity Mapping supplies the have-versus-need evidence the alignment depends on.
- Sibling mechanisms: Workflow Fit Analysis · Feasibility Study · Deployment Plan · Governance Readiness Review · Implementation Readiness Review · Operational Pilot · Process Walkthrough · Training and Support Package
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: The mechanism compares required capabilities with free or buildable supply, classifies each line, and identifies the binding gap that constrains scope, so its operative output is a feasibility assessment.
Nearest alternative: Analysis, Modeling & Optimization — Costing and comparison support the finding, but the mechanism establishes whether real implementation capacity is adequate.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: Implementation and organizational-capacity assessment map required capabilities, resources, authority, and time against what responsible actors actually possess.
Related originating lineages:
- Public Administration & Policy — Policy implementation research distinguishes a designed intervention from the state capacity needed to carry it out.
- Sociology & Anthropology — Invisible-work research reveals labor omitted by formal resource inventories.
Review resolution: Organizational management is the agreed primary lineage because the map inventories who can do what, where, and with what constraints. Public administration contributes institutional and geographic service maps, while sociology contributes informal and community capacity; their independent practice warrants convergent classification.
Review outcome: Reconciled after independent review; high confidence.
References¶
[1] "Invisible work" — labor that is necessary but unrecognized and unaccounted, a concept named by sociologist Arlene Kaplan Daniels (1987). Capacity Mapping exists partly to make such labor countable before it is silently dumped on implementers. registry ↩