Decision Making and Judgement Under Pressure
What this domain tests
This domain asks how you reason when time, information and resources are all short. Concepts to understand: risk-based prioritisation (harm likelihood × severity, not loudness of the requester), sufficiency of information (deciding with enough, not perfect, information and recording assumptions), escalation thresholds (what you may decide yourself versus what must go up), reversibility (move fast on reversible decisions, slow down on irreversible ones), and accountability (owning the outcome, including the decision not to act).
Traps to expect
- Paralysis dressed as diligence. "Gather more data before doing anything" when a person is at immediate risk. Urgent protection comes first; investigation follows.
- The heroic solo fix. Bypassing procedure to solve something quickly. Speed never justifies breaching a control designed to prevent harm.
- Anchoring on the first complaint. The loudest or most senior voice is not automatically the highest risk.
- Ignoring the recorded rationale. Options that decide well but leave no audit trail are weaker than ones that decide well and document why.
Rule of thumb
Use a four-step sequence: (1) What is the worst realistic outcome and how soon? (2) What must I do in the next few minutes to prevent it? (3) What can wait for more information? (4) Who must know, and by when? Then write a one-line rationale: decision, reason, review point.
Worked example
Mid-shift you receive two urgent requests: a routine report due today for a senior manager, and a front-line report of a possible safety breach affecting the public. Best action: act immediately on the safety matter, notify the appropriate duty contact, and send the manager a brief note that the report will be delayed with a revised time. Not: complete the report first because the requester is senior, and not: silently miss the deadline.