To pace a deductive reasoning test, work out your average time per question before you start, answer the quick questions first, mark anything that stalls you and come back to it. Speed should come from a reliable method, not from rushing, because hurried answers are exactly where the classic mistakes live.
Set your budget, and resist rushing
Work out your budget before you start
Look for two numbers in the test instructions: how many questions there are and how much time you have. Divide one by the other. Take an invented paper with 20 questions and 8 minutes: 480 seconds divided by 20 is 24 seconds per question. That figure is a budget, not a target for each item.
Some questions will take 15 seconds and some will take two minutes. Knowing the average tells you when you are behind and when you can afford to think.
Why rushing costs more than it saves
The trade between speed and accuracy is a familiar idea in experimental psychology. Richard Heitz has reviewed its history, physiology, methodology and behavior, and the everyday version is simple: respond faster and you risk giving up accuracy.
Reasoning adds a twist. Jonathan Evans and Jodie Curtis-Holmes ran a study titled "Rapid responding increases belief bias". When people were pushed to respond quickly, they leaned harder on what sounded believable and less on what followed.
So the aim is not to read faster. It is to waste less time on the moves that do not need to be slow.
Triage and shortcuts
Triage: three kinds of question
On a first pass through the test, sort each question in a few seconds.
- Quick: one rule, one fact, one step. A plain "all A are B" syllogism or a modus ponens question belongs here. Answer immediately.
- Medium: a short ordering puzzle, a rule with a negative, or a "some" statement mixed with an "all". Draw it once and answer.
- Slow: a long set of statements with several conclusions, or a ranking with five or more people. Mark it and move on.
Banking the quick marks first gives you the time to handle the slow ones on a second pass.
Cheap time savers that do not cost accuracy
- Read the question line first. Knowing whether you are hunting for "must be true" or "could be true" tells you what to look for in the statements.
- Use neutral shorthand. Single letters and arrows are faster to write than sentences, and they keep the topic from tempting you. The method is in how to solve deductive reasoning questions.
- Draw once. Make a single picture of the statements and test every option against it, instead of re-deriving the situation for each option.
- Stop at the first counterexample. The moment you find a case where the statements hold and the option fails, the option is dead. You do not need to find a second one.
- Ignore the story. Couriers, engineers and parcels are decoration. Only the logical words matter.
Skipping and guessing
When to skip, and what to do on the way back
A reasonable rule is to give a question a fair first attempt, then mark it and move on if you have no clear route after roughly your average budget. The sunk-cost feeling is strong, because the more time you have spent, the more it seems wrong to leave. Resist it. The marks on the next question are worth just as much as the marks on this one.
When you return, start from scratch instead of from your half-finished drawing. A fresh look often finds in seconds what the first attempt missed in minutes.
Guessing: read the rules first
Whether a blank, a wrong answer and a right answer score differently depends on the test, so check the instructions. If wrong answers carry no penalty, never leave a question empty. If they do carry a penalty, guess only after you have eliminated at least one option.
Elimination is easier than it sounds on deductive items. Options that use "all" or "none" need strong premises, so they often fall to a counterexample first.
Practise accuracy first, then speed
Train the two skills one after the other. Start with untimed practice where the only goal is to give the right reason for every answer. If you cannot state the reason in a sentence, you are not ready to speed up.
Then add a clock. The worked problems in deductive reasoning examples with answers are a good bank for this, because each one has a stated reason you can check against. After each timed session, note which questions ran long and which mistake type caused errors. The list in common deductive reasoning mistakes helps you label them.
Researchers describe a fast intuitive route and a slower deliberate one; Jonathan Evans and Keith Stanovich survey that work in their review of dual-process theories of higher cognition. For a test-taker, the lesson is practical. Deliberate checking is slow by nature, so save it for the questions that need it.
A short routine for test day
- Check the number of questions and the time, and work out the average per question.
- Do a first pass: answer the quick ones, draw the medium ones, mark the slow ones.
- Glance at the clock after each handful of questions, not after every question.
- Use the second pass for the marked questions, starting fresh.
- Keep the last moments for any unanswered question, subject to the penalty rules.
Try it under realistic conditions
The JobCannon Deductive Reasoning Test is built around "follows / does not follow" conclusions from a set of statements, using syllogisms, if-then rules and ranking puzzles, so it is a fair place to rehearse triage. Check the on-screen instructions for the time rules before you begin.
For a wider mix that also includes analytical puzzles, there is JobCannon's older logical reasoning test. The questions in both are written in-house, so treat your result as practice feedback and not as a formal score.