Diagnostics

Burden Modeler

Quantifies task load, cognitive friction, and risk exposure so you can reroute toil before it burns people out.

Overview

When to use the Burden Modeler.

Best for leaders who need a fast workload snapshot before teams hit a burnout threshold.

  • Scenario name and primary workflow.
  • Rough task volume or handoff counts.
  • Known friction points or escalation paths.

Estimated time: 10–15 minutes

Scholarly metadata

Authorship

Contact: diagnostics@ethotechnics.org

Publication details

  • Published: Dec 3, 2025
  • Last updated: Jan 9, 2026
  • Version: v1.1.0
  • DOI: Pending Zenodo deposit

License: CC BY 4.0

Credit Ethotechnics Institute Diagnostics Lab, include tool name + version, and link to the canonical permalink.

Archive snapshot: Wayback capture

Changelog

  • v1.1.0 · 2026-01-09 — Published method cards, transparency notes, and replicability guidance for each diagnostic.
  • v1.0.0 · 2025-12-03 — Initial diagnostics suite release.

Copy citation (APA/BibTeX)

Cite this page Formats: APA, MLA, Chicago, BibTeX, RIS

Version

v1.1.0

Last updated

Jan 9, 2026

DOI

Pending Zenodo deposit

APA

Ethotechnics Institute Diagnostics Lab. (2026). Burden Modeler. Ethotechnics Institute. https://ethotechnics.org/diagnostics/burden-modeler

MLA

Ethotechnics Institute Diagnostics Lab. "Burden Modeler." Ethotechnics Institute, 2026, https://ethotechnics.org/diagnostics/burden-modeler.

Chicago

Ethotechnics Institute Diagnostics Lab. "Burden Modeler." Ethotechnics Institute. Jan 9, 2026. https://ethotechnics.org/diagnostics/burden-modeler.

BibTeX

@misc{diagnostic_burden-modeler,
  title={Burden Modeler},
  author={Ethotechnics Institute Diagnostics Lab},
  year={2026},
  howpublished={Ethotechnics Institute},
  url={https://ethotechnics.org/diagnostics/burden-modeler},
  version={v1.1.0}
}

RIS

TY  - WEB
TI  - Burden Modeler
AU  - Ethotechnics Institute Diagnostics Lab
PY  - 2026
UR  - https://ethotechnics.org/diagnostics/burden-modeler
ER  -

Methodology

Method, transparency, and replicability.

Inputs, scoring logic, validation notes, and failure modes used in the model.

Inputs

  • Scenario name and primary workflow.
  • Estimated task volume and handoff counts.
  • Known friction points and escalation paths.

Procedure

  1. Weight task load, friction, and risk sliders with the scenario team.
  2. Review the computed burden index and hotspot ranking.
  3. Select mitigation paths and estimate relief impact.

Outputs

  • Burden index score with plain-language findings.
  • Ranked hotspot list with mitigation recommendations.
  • Relief estimates tied to the selected mitigations.

Measures

  • Task load volume across roles and handoffs.
  • Cognitive friction introduced by tooling or policy complexity.
  • Risk exposure across the workflow with weighted severity.

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.
  • Weekly task volume or queue size.
  • Number of handoffs or escalation checkpoints.
  • Friction rating (1–5) for key steps.
  • Risk exposure rating (1–5) for each stage.

Rubric

  • Task load, friction, and risk scored on 1–5 scales.
  • Risk weights adjusted via criticality slider.

Scoring logic

  • Burden index = weighted average of load, friction, and risk.
  • Hotspots rank by combined load and risk scores.
  • Relief estimate computed from mitigations selected.

Validation notes

Piloted across support, operations, and research scenarios to calibrate weights and language.

Inter-rater alignment improves after a shared calibration pass; variance shrinks on second runs.

  • Over-weighting a single friction point can skew results.
  • Underspecified task volume leads to low-confidence outputs.
  • High uncertainty 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.
  • Compare output against historical incidents for calibration.

Example outputs

  • Sample burden index readout with hotspots and relief estimates.
  • Anonymized scenario summary and mitigation plan.

Sample output

Preview the burden readout.

See the summary format, hotspot ranking, and mitigation callouts.

View sample output

Run the tool

Start a new burden scenario.

Run the model and export your scenario readout.

Burden Modeler

Quantify where toil piles up and how to offload it.

Rate how much operational and cognitive load each factor adds to your scenario. The model computes a burden index, highlights hotspots, and suggests mitigations with expected relief. Use it to make the hidden load legible before it burns people out.

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%

Interruptions and escalations

How often are responders pulled into unplanned escalations or urgent asks?

5Manageable

Coverage and staffing

How thin is staffing coverage across time zones and critical roles?

5Manageable

Cognitive friction

Context switching, missing runbooks, and unclear decisions that slow people down.

50%

Handoffs and context switching

How fragmented is work across channels, tickets, or roles?

5Manageable

Tooling friction

How much time disappears to brittle tools, permissions, or missing automation?

5Manageable

Decision debt

How many past decisions or ambiguous policies keep re-opening work?

5Manageable

Risk exposure

Incidents, safety-critical steps, and escalation loops that increase harm potential.

50%

Runbooks and guardrails

How often do people improvise because guardrails or playbooks are missing?

5Manageable

Incident frequency

How frequently do incidents, abuse reports, or outages hit this team?

5Manageable

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.

  1. Interruptions and escalations

    Manageable load

    13% expected reliefQueues, staffing coverage, and surprise work that stack load on operators.
    • Route interrupt-heavy work to rotating buffers or guardrail teams.
    • Block focus windows for deep work and align escalation paths.
  2. Incident frequency

    Manageable load

    13% expected reliefIncidents, safety-critical steps, and escalation loops that increase harm potential.
    • Add protective friction and clearer refusal policies to lower incoming risk.
    • Staff backup responders or on-call rotations during known spikes.
  3. Handoffs and context switching

    Manageable load

    12% expected reliefContext switching, missing runbooks, and unclear decisions that slow people down.
    • Trim the number of active lanes and clarify who owns each decision.
    • Collapse duplicative queues with a single routing checklist.

Off-ramp

Need facilitation?

If the burden index is trending overloaded, route to the Studio for a facilitated session. We help weight inputs with your support partners, validate relief estimates, and shape an escalation-ready plan.

Book a facilitated burden modeling session