Reasoning Ability — Quick Reference
Puzzle-solving method
1. Read all clues once, no writing — get the puzzle's shape
2. Start from the MOST DEFINITE clue (fixed position/relationship),
not the first clue listed
3. Build incrementally — mark confirmed vs. tentative distinctly
4. Re-verify EVERY clue (including negative ones) against the
final arrangement before answering
Topic map
|---|---|
| Puzzles & Seating | Most-definite-clue-first, grid for multi-attribute |
|---|
| Syllogism | Venn diagram — conclusion must hold in EVERY valid diagram |
| Coding-Decoding | Practice recent-year patterns specifically |
| Blood Relations | Draw the tree — never track mentally beyond 3 relations |
| Direction Sense | Sketch every problem — "turn right" is state-dependent |
| Input-Output | Confirm rule against EVERY given step before extrapolating |
| Inequality | Watch mixed >/≥ chains and distinct "either-or" conclusions |
Syllogism check
A conclusion is valid ONLY if true in every possible diagram
consistent with the statements — not just the first diagram drawn.
Practice: draw 2-3 alternative valid diagrams per statement set.
Inequality chain example
A > B ≥ C > D
Valid: A > D, A > C, B > D
Watch for: mixed > and ≥ in the same chain, and "either-or"
conclusions as a DISTINCT category from individual validity checks
Mains-level elimination technique (when direct placement stalls)
1. List ALL remaining valid possibilities for the stuck variable
2. Check EACH against every other already-placed clue
3. Eliminate any that create a contradiction
4. Often only one possibility survives — even with no single
clue directly determining it
Time budgets
Prelims puzzle (4-5 variables): 2-3 minutes
Mains puzzle (6-7 variables, elimination required): 5-8 minutes
Don't force a Prelims time budget onto Mains-level difficulty
Computer Aptitude — different skill, different prep
Number systems (binary/decimal/hex), computer terminology,
basic networking, MS Office — FACTUAL RECALL, not pattern-based.
Needs dedicated content study, not repetition puzzle practice.
Error log — review as a SET, not individually
Entry template:
Puzzle type: _______
Specific error: _______ (be precise — e.g., "off-by-one in
'third to the right' counting")
Recurrence check: has this exact error type appeared before
across other log entries?
Practice discipline
Solve ≥1 full puzzle daily under a 6-8 min timer, from day one
Daily spaced practice > occasional long cram sessions
(builds transferable pattern recognition more reliably)