Decision Making
Outline & Learning Goals
In this chapter you will learn:
- What "Decision Making" questions actually test (and what they don't).
- The standard format: a situation, a set of conditions, and a candidate's data.
- The Condition-Matching method — the only reliable way to solve these fast.
- How to handle "data insufficient" and "course of action" style variants.
- The traps examiners plant, and how to step around them.
By the end, you should be able to solve a full decision-making question in under 60 seconds without re-reading the passage.
1. A Hook: The Exam Is Not Testing Your Wisdom
Imagine you are a bank manager. A loan application lands on your desk. The applicant earns well, but his documents show one gap in employment. Do you approve? Reject? Refer it to your senior?
Your real-life answer would be: "It depends. I'd need more information."
But in the exam, "it depends" is not an option. You must pick one of four answers in 45 seconds — and the examiners have already decided which one is "correct" based on a fixed set of rules given in the question itself.
That is the whole secret of this chapter: Decision Making questions are not about your judgement. They are about following the given rules mechanically. The student who treats it like an essay loses. The student who treats it like a checklist wins.
2. Why Students Struggle Here
Most aspirants make one of three mistakes:
- They use real-world logic. "But in real life, the manager would call the candidate first!" Irrelevant. The question's rules are the entire universe.
- They re-read the passage for every sub-question. This burns 3–4 minutes. The conditions must be converted into a compact table *once*.
- They panic at the length. The passage looks scary — 8 lines of conditions. But every condition is just a simple "if-then" filter.
🧠 Active Recall: Before reading further, answer this — in a Decision Making question, where does the "correct" answer come from: your experience, or the conditions printed in the question? (Say it out loud.)
3. The Standard Format
A typical question has three parts:
Part A — The vacancy/role. "A company wants to recruit Marketing Officers."
Part B — The conditions. Usually structured like this:
The candidate must:
(i) be a graduate with at least 60% marks;
(ii) be between 21 and 28 years of age as on 01.01.2024;
(iii) have at least 2 years of work experience.
However, if a candidate satisfies all conditions except:
(a) condition (i), but has a postgraduate degree, the case is to be referred to the General Manager;
(b) condition (iii), but has worked as an intern for 1 year, the case is to be referred to the HR Head.
Part C — The candidate's data + answer options. Typically:
(a) Select the candidate
(b) Do not select
(c) Refer to General Manager
(d) Data inadequate
Your job: run the candidate through the checklist, in order.
4. The Condition-Matching Method (The Core Skill)
Follow these five steps religiously:
Step 1 — Number the main conditions. Write (i), (ii), (iii) on your rough sheet with one keyword each: *Grad 60%*, *Age 21–28*, *Exp 2yr*.
Step 2 — Number the exceptions. Write (a) and (b) below them with their outcomes: *(a) → GM*, *(b) → HR*.
Step 3 — Check the candidate against each main condition, one by one. Tick ✓ or cross ✗.
Step 4 — Apply the rule of outcomes:
- All ✓ → Select.
- Exactly one ✗, and an exception covers it → Refer to the authority named in that exception.
- Exactly one ✗, and no exception covers it → Reject.
- Two or more ✗ → Reject (exceptions almost never cover two failures — read carefully).
- A required fact is simply not given → Data inadequate.
Step 5 — Watch the reference date. Age and experience are always calculated "as on" a specific date. This is where most marks are lost.
🧠 Active Recall: A candidate fails condition (ii) on age, and there is no exception clause for age. What is the decision? What if he fails both (i) and (iii)?
5. A Worked Example
Conditions: A candidate must (i) be a graduate with ≥ 60%, (ii) be 21–28 years old as on 01.01.2024, (iii) have ≥ 2 years of experience. Exception (a): fails (i) but is a post-graduate → refer to GM. Exception (b): fails (iii) but has 1 year of internship → refer to HR Head.
Candidate: Ravi, born 15.03.1997, B.Com with 58%, M.Com (post-graduate), 3 years of experience.
Solution:
- (i) Graduate with 60%? He has 58% → ✗
- (ii) Age on 01.01.2024: born March 1997 → 26 years → ✓
- (iii) 3 years experience → ✓
- Exactly one failure: (i). Exception (a) covers it (he is a post-graduate) → Refer to GM.
Notice: we never asked "is referring fair?" We just matched.
6. Variant 1: "Data Inadequate"
This option is a trap magnet. Choose it only when a fact needed to test a condition is genuinely missing from the candidate's data.
- "Ravi is a graduate" — but no percentage given, and condition (i) needs 60% → Data inadequate (unless another condition already disqualifies him).
- If the candidate clearly fails a condition that has no exception, the answer is Reject — not "data inadequate" — even if other data is missing. One confirmed failure with no exception is enough.
🧠 Active Recall: When is "data inadequate" correct, and when is it a trap?
7. Variant 2: Courses of Action
A cousin of this chapter: a problem is stated, and you judge which of the suggested actions logically follow.
Rules:
- An action follows if it is practical, directly addresses the problem, and is within the authority implied.
- An action does not follow if it is extreme ("shut down the department"), irrelevant, or merely repeats the problem.
- "Either I or II follows" applies only when the two actions are genuinely mutually exclusive and one of them must happen.
8. Mnemonic: "CLEAR"
Run every candidate through CLEAR:
- C — Conditions: list them with keywords.
- L — Look at the reference date (age/experience cut-off).
- E — Exceptions: which failures do they cover, and who decides?
- A — All pass = Accept; one covered failure = Refer; else Reject.
- R — Recheck for missing data before marking "data inadequate."
Say it once before every practice set: *"Stay CLEAR, don't think, just match."*
9. Summary Table
| Situation | Decision |
|---|---|
| All main conditions satisfied | Select / Accept |
| Exactly one condition failed, exception covers it | Refer to the named authority |
| One condition failed, no exception for it | Reject |
| Two or more conditions failed | Reject |
| A needed fact is missing (and no confirmed rejection) | Data inadequate |
| Age/experience check | Always compute "as on" the given date |
Review this after 2 days. Redo the worked example from memory using CLEAR, then attempt one practice set. If you can solve 5 questions in 5 minutes without re-reading the conditions, this chapter is done.
⚠️ Caution: Examiner's Trap
Trap 1 — More than one plausible-looking relationship between conditions.
The examiner writes exceptions that *partially* overlap, so two options (e.g., "Refer to GM" and "Refer to HR Head") both look possible. Rule: identify which single condition failed, then apply only the exception attached to that condition. Never mix two exceptions for one candidate.
Trap 2 — Heavy vocabulary to confuse you.
Words like "incumbent," "remuneration," "provisional," "notwithstanding" are decoration. Translate each condition into plain keywords on your rough sheet (*Grad 60%*, *Age ≤ 28*) before looking at the candidate. Students who read the passage three times usually lose to students who tabulate it once.
Trap 3 — The double-failure question disguised as a referral.
A candidate fails two conditions, but the data loudly highlights the one failure that *has* an exception — tempting you to mark "Refer." Rule: check every condition first. Two failures = Reject, no matter how attractive the exception looks. Also beware the reverse: a candidate who fails one condition with an exception, but whose data for that exception is incomplete — that is "data inadequate," not "refer."