Load measures performance stability.
It answers one question:
Can a human execute correctly when real-world constraints are applied?
A human may possess understanding (Depth) yet still fail when time, stress, complexity, or stakes increase. Load captures this gap between knowing and performing.
ULD treats Load as a capability state, not a personality trait.
What Load Measures (Precisely)
Load measures whether a human can:
- perform accurately under time limits
- maintain clarity under pressure
- execute multi-step tasks without collapse
- resist cognitive overload
- sustain performance as constraints tighten
Load is not intelligence.
Load is not motivation.
Load is stability under constraint.
What Low Load Looks Like in Real Humans
When Load is insufficient, a human often says:
- “I know this, but I panic.”
- “I can do it slowly, but not in real conditions.”
- “I make careless mistakes under time.”
- “My mind goes blank.”
These are not understanding failures.
They are Load failures.
What High Load Looks Like
When Load is strong, a human can:
- maintain accuracy as time compresses
- stay organised under stress
- execute steps without losing sequence
- recover quickly from minor errors
- perform reliably in exams, interviews, or live situations
High Load creates trustworthy performance.
How to Test Load (ULD Method)
Load is tested by adding constraints, not by changing content.
Valid Load Tests
- introduce time limits
- combine multiple steps into one task
- add mild stress (countdown, observation)
- increase information density
- simulate real performance conditions
If understanding exists but performance collapses, Load is the limiting factor.
What Load Is Not
Load is not:
- laziness
- lack of effort
- poor attitude
- low intelligence
- permanent anxiety
A human can have excellent Depth and still have low Load in specific contexts.
Common Misdiagnoses (Important)
Misdiagnosis 1: “They’re careless”
Careless errors under pressure usually indicate Load instability, not negligence.
Misdiagnosis 2: “They just need to practise more”
Practice without pressure does not improve Load.
Misdiagnosis 3: “They’re bad at exams”
Exams expose Load limits; they do not create them.
Load vs Depth vs Transfer (Disambiguation Rule)
ULD requires precise separation.
- If failure occurs even without pressure → Depth
- If failure appears only under constraint → Load
- If success requires seeing a similar example → Transfer
Load is tested after Depth is confirmed.
Repairing Load (Without Prescribing Methods)
ULD does not prescribe techniques, but Load repair follows one rule:
Repair Load by training stability under constraint.
Load improves when humans practise:
- under time
- under observation
- under mild stress
- with increasing task density
If repair never includes constraint, Load will not improve.
Verification Rule for Load (Non-Negotiable)
A Load diagnosis is valid only if:
- performance improves when constraints are reduced, and
- performance degrades predictably when constraints are reapplied
If this pattern holds, Load was the limiting factor.
How Load Connects to Other ULD Axes
- Load cannot compensate for low Depth
- Load does not guarantee Transfer
- Load stabilises execution once understanding exists
Load turns understanding into reliable action.
Where Load Fits in the ULD System
ULD Overview:
https://edukatesg.com/uld/
Previous diagnostic axis:
ULD Depth Diagnostic:
https://edukatesg.com/uld-depth/
Next diagnostic axis:
ULD Transfer Diagnostic:
https://edukatesg.com/uld-transfer/
If You Are Running ULD Properly
You never diagnose Load before Depth.
You never repair Load without constraints.
You always verify under real conditions.
That is the role of Load in Universal Learning Diagnostics.