Decision-Making Speed and Accuracy
What is actually tested
This domain measures judgement under time constraint: choosing between competing options, prioritising a queue of tasks, allocating limited resources, and spotting the response that is good enough rather than perfect. The scoring usually rewards total correct answers, so both raw speed and raw accuracy lose on their own - the optimum is a fast, steady pace with controlled errors.
The recurring traps
The first is the speed-accuracy collapse: candidates sprint for the first half, then their error rate triples. The second is sunk cost - continuing to invest in an item or option because of effort already spent rather than because it is now best. The third is anchoring on the first plausible option and failing to read the rest. The fourth is answering before reading the whole question, which is fatal when the stem ends in "NOT" or "except". The fifth is second-guessing: changing a considered answer under time pressure usually lowers the score.
Worked example
Four tasks compete for one hour: a deadline in 20 minutes worth 30 points, a deadline tomorrow worth 40 points, a low-value task worth 5 points, and one requiring a colleague who is unavailable. Rank by (value x urgency) and by feasibility - the 30-point task first, the 40-point task next, the 5-point task last, and the blocked task dropped or delegated.
Rule of thumb
Use a two-pass strategy: on pass one answer everything you can resolve in a few seconds and flag the rest; on pass two spend the remaining time only on flagged items. Never let one hard item consume the time of three easy ones.