GNFS Aptitude Test study materials
GNFS Aptitude Test study resources

GNFS Aptitude Test: Problem Solving and Decision Making

GNFS Aptitude Test · Work through your exam, one topic at a time.

All guide sections

Problem Solving and Decision Making

What this domain tests

This domain tests structured judgement: identifying the objective, constraints and dependencies, prioritising under limited time or resources, and choosing the option with the best overall outcome rather than the most obvious one. Scenarios are usually workplace-based and contain one or two hard constraints that eliminate several attractive answers.

Core rules

  • State the goal in one sentence before comparing options.
  • Separate hard constraints (deadline, budget, safety, legal requirement) from preferences.
  • Map dependencies: a task that unlocks other tasks must come earlier.
  • Rank by urgency and impact; do mandatory and irreversible tasks first.
  • Ignore sunk costs; base the decision on future costs and benefits.
  • Check second-order effects: a cheap option that creates rework is not cheap.
  • When two options tie, choose the one that preserves flexibility or has the lowest downside.

Worked example

You have 80 minutes. A mandatory briefing takes 20 minutes. A report needs a data check (15 minutes), analysis (25 minutes) and review (10 minutes), in that order, and is due at the end of the 80 minutes. An optional networking session takes 20 minutes. What do you do?

The report chain is 15 + 25 + 10 = 50 minutes and has a hard deadline plus a strict sequence, so it cannot be compressed without risk. Mandatory briefing (20) + report (50) = 70 minutes, leaving 10 minutes of buffer. The optional session (20) does not fit without eating the buffer or the review step. Decision: attend the briefing, run the report chain, skip the optional session, and use the 10 minutes for a final check. The trap is to attend the optional session first because it is short and agreeable, then compress the review.

Traps that cost marks

  • Prioritising the easiest or most visible task over the deadline-critical one.
  • Treating a preference as a constraint.
  • Forgetting that a dependent task cannot start early.
  • Choosing on cost alone and ignoring failure risk.
  • Defending a previous decision because of time already spent.