Measures
- Task load volume across roles and handoffs.
- Cognitive friction introduced by tooling or policy complexity.
- Risk exposure across the workflow with weighted severity.
Workload modeler
Rate seven sources of workload, such as interruptions, handoffs, and incidents. Get a burden score out of 100 and the three places where reducing load would help most.
Estimated time: 10–15 minutes. When to use it · How it is scored
Start a new burden scenario
Run the model and export your scenario readout.
Readout: The burden index, the hotspot ranking, and the mitigations listed for each hotspot. View sample output
Workload modeler
See where the workload piles up and what would reduce it
Rate from 0 to 10 how much operational and cognitive load each factor adds to your scenario. The model returns a burden index, ranks the hotspots, and lists mitigations. Each mitigation shows how far the index would fall if that driver were zero; that is arithmetic on your ratings, not a measured result.
Reference a release, queue, or incident stream so the results stay linkable.
Rating scale
0 = resting, 10 = unsustainable.
025810
RestingLightManageableHeavyUnsustainable
Task load
Queues, staffing coverage, and surprise work that stack load on operators.
50%
Cognitive friction
Context switching, missing runbooks, and unclear decisions that slow people down.
50%
Risk exposure
Incidents, safety-critical steps, and escalation loops that increase harm potential.
50%
Baseline
Burden index
Composite score across task load, cognitive friction, and risk exposure.
50
Watch
Burden is rising. Pick one hotspot to mitigate before the next release cycle.
Average rating
5.0
Top category
Task load
Top driver
Interruptions and escalations
Imbalance threshold
12 pts
Task load
50%
Queues, staffing coverage, and surprise work that stack load on operators.
Cognitive friction
50%
Context switching, missing runbooks, and unclear decisions that slow people down.
Risk exposure
50%
Incidents, safety-critical steps, and escalation loops that increase harm potential.
Segments
Top impacted segments
Compare category scores against the category baseline.
SegmentScoreDeltaFlag
Task load50%On baselineStable
Cognitive friction50%On baselineStable
Risk exposure50%On baselineStable
Hotspots
Where burden is peaking
Top factors sorted by weighted score with suggested mitigation paths.
- 13 index points if this driver were zero (a formula, not an observed change)Queues, staffing coverage, and surprise work that stack load on operators.
- Route interrupt-heavy work to a rotating on-call person or team.
- Block focus windows for deep work and align escalation paths.
- 13 index points if this driver were zero (a formula, not an observed change)Incidents, safety-critical steps, and escalation loops that increase harm potential.
- Add checks that slow risky requests, and clearer rules for when to refuse them.
- Staff backup responders or on-call rotations during known spikes.
- 12 index points if this driver were zero (a formula, not an observed change)Context switching, missing runbooks, and unclear decisions that slow people down.
- Cut the number of active work queues and clarify who owns each decision.
- Collapse duplicative queues with a single routing checklist.
Outside help
Running a healthcare AI system?
If the index reads Overloaded, a safeguards review lists the gaps, ranked by the harm they could do. Kanav Jain, who wrote this framework, does them under commission.
This diagnostic rates the workload a system creates for the team that runs it. To score the time a journey takes from the person it decides about, use the VAL-01 Journey burden check defined under STD-01.
When to use the workload modeler
Leads who need to see where workload concentrates before a team runs past its capacity.
- Scenario name and primary workflow.
- Rough task volume or handoff counts.
- Known friction points or escalation paths.
Method, transparency, and replicability
Inputs, scoring logic, validation notes, and failure modes used in the model.
Show inputs, procedure, scoring, assumptions, and validation
Inputs
- Scenario name and primary workflow.
- A 0–10 rating for each of seven workload drivers. The tool does not take task volume or handoff counts; note them beside the ratings if you have them.
- Known friction points and escalation paths.
Procedure
- Rate each driver with the people who carry the work.
- Read the burden index and the hotspot ranking.
- Pick mitigations and read the relief estimate for each.
Outputs
- Burden index score with plain-language findings.
- Ranked hotspot list with mitigation recommendations.
- Relief estimates tied to the selected mitigations.
Does not measure
- Individual performance or productivity.
- Legal compliance posture or audit readiness.
- Long-term cultural or morale shifts beyond the scenario window.
Assumptions
- Inputs reflect cross-functional consensus, not a single point of view.
- Task volume estimates are directionally accurate for the period.
- Risk weights reflect the scenario's actual severity bands.
Instrument prompts
- Scenario name and workflow summary.
- A rating from 0 to 10 for each of seven drivers: interruptions, handoffs, tooling, runbooks, incidents, coverage, and decision debt.
Rubric
- Each driver carries a fixed weight, from 1.0 for decision debt to 1.4 for interruptions.
- Drivers roll up into three categories: task load, cognitive friction, and risk exposure.
Scoring logic
- Burden index = weighted sum of the ratings over the maximum possible, as a score out of 100. Below 35 is Healthy, below 70 is Watch, and 70 or more is Overloaded.
- Hotspots are the three drivers with the highest weighted scores.
- Each driver shows a relief estimate, scaled from its rating and weight and capped at 30 points.
Collection cost
Ten to fifteen minutes for a group rating together. If rating runs past fifteen minutes, record the scenario as unscored; the tool does not stop the group.
- Respondent-supplied. The cost falls on the people who do the workflow, which is where the burden already sits.
- Handoff counts and task volume come from ticketing and workflow logs where they exist.
- Escalation frequency comes from the escalation and appeal record.
- Friction points listed during prep are already written down somewhere, such as a ticket or a runbook.
- A workflow nobody will rate is not a workflow without burden. The readout records the gap and stops there.
Validation notes
Driver weights are fixed in the tool, from 1.0 for decision debt to 1.4 for interruptions. Change them only in the source, where the change is visible.
Ratings are self-reported, so two groups rating the same workflow can score it differently. Rate together and record the reason for each rating.
- Overweighting a single friction point can skew results.
- Underspecified task volume leads to low-confidence outputs.
- Uncertainty is high if scenario owners are not present for scoring.
Replicability
- Gather a cross-functional scoring group.
- Use the prompt list and rubric to score the scenario.
- Record weighting decisions and rationale.
- Check the hotspots against the incidents the team has already had.
Example outputs
- Sample burden index readout with hotspots and relief estimates.
- Anonymized scenario summary and mitigation plan.
Cite this page · v1.6.0 · updated Oct 2, 2026 · CC BY-SA 4.0
APA
Ethotechnics Institute Diagnostics Lab. (2026). Workload modeler. Ethotechnics Institute. https://ethotechnics.org/diagnostics/burden-modeler
MLA
Ethotechnics Institute Diagnostics Lab. "Workload modeler." Ethotechnics Institute, 2026, https://ethotechnics.org/diagnostics/burden-modeler.
Chicago
Ethotechnics Institute Diagnostics Lab. "Workload modeler." Ethotechnics Institute. Oct 2, 2026. https://ethotechnics.org/diagnostics/burden-modeler.
BibTeX
@misc{diagnostic_burden-modeler,
title={Workload modeler},
author={Ethotechnics Institute Diagnostics Lab},
year={2026},
howpublished={Ethotechnics Institute},
url={https://ethotechnics.org/diagnostics/burden-modeler},
version={v1.6.0}
}
RIS
TY - WEB TI - Workload modeler AU - Ethotechnics Institute Diagnostics Lab PY - 2026 UR - https://ethotechnics.org/diagnostics/burden-modeler ER -