Simultaneous Feasibility and Capacity Test¶
Test or assessment — instantiates Role-Expectation Conflict Reconciliation
Compares time, timing, attention, competence, authority, and resources under realistic peaks.
The Simultaneous Feasibility and Capacity Test takes a single already-flagged pair of demands and asks one quantitative question: can one person actually discharge both at the same moment — specifically at the worst realistic moment, not the average one? It measures the concrete requirements each duty imposes (time, timing, attention, competence, decision authority, information access, physical presence, recovery) and checks them against what the role-holder actually has when both peak together. Its distinctive output is a verdict on type: the collision is staffable overload (more hands fix it), sequenceable tension (ordering fixes it), or structural impossibility (no amount of capacity fixes it). That classification is what decides whether the remedy is resources or something harder — which is exactly the difference between a workload problem and a genuine role conflict.
Example¶
A rural county employs one person, Dale, as both a volunteer firefighter on the on-call roster and the sole system administrator for county IT. On paper both fit inside a 40-hour week, and for months nobody sees a problem. The feasibility test ignores the week and models the peak: a structure fire and a ransomware-triggered server outage at 2 a.m. on the same night. It tabulates each duty's peak requirement — the fire needs Dale physically at a scene for roughly three hours with full attention and a hand on the radio; the outage needs him at a keyboard within thirty minutes or the backups corrupt. Then it tests whether the enabling conditions travel: can he run the server restore from a fire scene? No — no network, no free hands, no attention to spare. The measured result is that at peak the two duties demand the same body in two places with non-overlapping presence requirements.
The verdict is not "Dale is overloaded"; it is structural impossibility — and that word matters, because the county's instinct ("hire a part-time backup admin for busy weeks") only cures a staffable-overload reading. The test shows extra hands during ordinary weeks would leave the 2 a.m. collision fully intact. That single distinction is what escalates the case out of capacity management and into real reconciliation.
How it works¶
- Model the peak, not the average. Fix the worst realistic co-occurrence of the two duties before measuring anything; averaged load hides the collision that lives in the tails.
- Quantify each duty in concrete units — minutes, attention, competence, authority, information, presence, recovery — rather than a lumped sense of "effort."
- Test whether enabling conditions travel. Does the authority, information, or tooling one role needs survive being physically or attentionally inside the other?
- Return a typed verdict — staffable overload / sequenceable tension / structural impossibility — and name the single binding constraint that drives it.
Tuning parameters¶
- Peak definition — how extreme the modeled worst case is (95th-percentile week versus absolute worst night). Too mild and it clears a real impossibility; too extreme and it condemns a workable pairing.
- Requirement granularity — lumped "effort" versus separated time / attention / authority / presence. Separation is what surfaces the non-substitutable constraint (you cannot buy presence with money).
- Recovery accounting — whether emotional labor and rest between peaks are counted as real requirements or assumed free.
- Feasibility threshold — how much slack must remain before a pairing is called feasible rather than merely survivable.
- Substitutability assumption — whether a given duty is treated as transferable to added staff at all; assuming yes when it is false is how impossibility gets misread as overload.
When it helps, and when it misleads¶
Its strength is that it is the single test that separates a problem you can staff your way out of from one you cannot — and it does so in numbers a budget conversation respects. It converts "she's stretched thin" into "these two duties require the same person in two places at 2 a.m., and no headcount changes that."
Its failure mode is that it is only as honest as its peak assumption. Averaged over a month, almost any two roles look feasible, so a test run on typical load will happily clear an impossible pairing — the flaw of averages[1]: planning around a mean systematically hides the collisions that only appear in the tails. The classic misuse is running it on comfortable numbers to ratify a pairing management already wants. The guarding discipline is to fix the peak scenario before measuring, treat "feasible on average" as no answer at all, and, when competence or authority (not time) is the binding constraint, state plainly that added capacity cannot help.
How it implements the components¶
The test realizes the archetype's measurement-and-diagnosis work — quantifying capacity and typing the conflict, not cataloguing or resolving it:
role_capacity_authority_and_boundary_test— it is this test in operation: realistic time, peaks, attention, competence, decision authority, information access, presence, and whether enabling conditions cross the role boundary.role_incompatibility_classifier— it converts the raw measurement into the overload / sequenceable-tension / structural-conflict verdict that determines whether resources can dissolve the collision.
It does NOT implement role_expectation_and_principal_inventory or affected_party_and_nonwaivable_duty_map — enumerating the full demand set and mapping who is exposed is the Role-Expectation Conflict Matrix's work; nor role_transition_and_residual_strain_monitor, the after-the-fact check owned by the Role-Conflict Recurrence Audit.
Related¶
- Instantiates: Role-Expectation Conflict Reconciliation — supplies the impossible/possible verdict the reconciliation choice depends on.
- Consumes: Role-Expectation Conflict Matrix — it tests the specific pairs the matrix has already flagged, rather than scanning the whole demand set itself.
- Sibling mechanisms: Role-Expectation Conflict Matrix · Duty-Priority and Harm Comparison · Recusal, Delegation, or Separation Gate · Protected Role-Conflict Conference · Role-Conflict Recurrence Audit
Editorial Notes¶
Form Classification¶
Form family: Analysis, Modeling & Optimization
Rationale: Simultaneous Feasibility and Capacity Test operates as an analytical, modeling, inference, comparison, or optimization procedure that derives insight or a solution because it compares time, timing, attention, competence, authority, and resources under realistic peaks.
Independent corroboration: The frozen evidence defines Simultaneous Feasibility and Capacity Test as 'Compares time, timing, attention, competence, authority, and resources under realistic peaks', so its operative form is Analysis, Modeling & Optimization.
Nearest alternative: Assessment, Review & Assurance — Simultaneous Feasibility and Capacity Test includes features of a bounded evaluation of existing evidence or work that produces a finding or disposition, but its defining operation is an analytical, modeling, inference, comparison, or optimization procedure that derives insight or a solution.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Operations Research
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Testing whether time, competence, authority, attention, and resources jointly suffice under peak demand is capacity and feasibility analysis.
Related originating lineages:
- Engineering & Design — Peak-load qualification tests simultaneous resource constraints.
- Mathematics — Mathematical modeling, proof, and abstract-structure practice supplies a parallel or contributing lineage for the mechanism's defining operation: compares time, timing, attention, competence, authority, and resources under realistic peaks.
- Organizational & Management Science — Role authority and staffing determine executable capacity.
- Psychology — Attention and fatigue impose human capacity ceilings not captured by material counts.
Review resolution: The blind reviewers agree that operations_research is the primary origin and differ only on alternate origin disagreement, origin mode disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain cross_disciplinary_synthesis because the combined evidence shows material contributions from several lineages. The broader reach of universal records portability separately from historical provenance; encyclopedia_synthesis=true preserves the affirmative synthesis judgment where either reviewer identified one.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
References¶
[1] Savage, S. L. The Flaw of Averages: Why We Underestimate Risk in the Face of Uncertainty. John Wiley & Sons (2009). Identifies the flaw of averages as the failure of plans built on average assumptions. registry ↩