Problem Solving and Decision Making
What the domain tests
Problem Solving and Decision Making measures whether you can define a problem, separate symptoms from causes, gather relevant facts, compare options against criteria, and choose an action that is feasible and reviewable. Expect workplace scenarios involving errors, backlogs, scheduling, or competing requests.
Core rules
- State the problem in measurable terms: what is wrong, where, when, and by how much.
- Identify constraints-deadline, budget, policy, staff, and risk-before generating options.
- Distinguish root cause from symptom. Test one plausible cause at a time.
- Compare options using explicit criteria such as accuracy, cost, speed, and customer impact.
- Choose, assign responsibility, set a check-in point, and monitor results.
- Avoid deciding from the first available explanation.
Worked example
Mailing addresses are failing. Rather than retraining everyone immediately, sample 50 recent records. Suppose 8 errors all involve handwritten ZIP codes. The pattern points to the source form, not keystroke speed. Options: redesign the ZIP field with boxes, add a validation check, or require printed labels. A validation check is fastest to test; the form redesign addresses the source. Reasoning: the sample narrows the cause before a costly fix.
Traps
Jumping to a solution; treating a symptom as the cause; ignoring a policy constraint; choosing the cheapest option without checking quality; and failing to define how success will be measured.