Aptitude skill lesson
Perceptual speed: skill lesson
Perceptual speed is how quickly you can decide whether two visual strings, symbols or records are the same, and how quickly you can find a target among visually similar distractors. It is measured with deliberately trivial content (the items are easy, the clock is not), and it appears in clerical checking, numeric keypad, dispatch, security screening and several of the short commercial cognitive batteries. Nothing here rewards thinking harder, which is why candidates who are strong at reasoning often score below their expectation: the winning behaviours are chunking, a fixed scan path and knowing when to stop. Practice is stored on this device only, with no account and no upload unless you export it.
Published · last reviewed
Applies to Novus Learn 0.1.0
What changed, and when
- , Replaced the body of all 27 non-judgement lessons with construct-specific material: six worked examples each, carrying the actual arithmetic, the actual inference or the actual procedure, plus expanded objectives, practice tips and glossary. Every 'Related Learn topics' link now points at a real page on this site rather than a generic search. The eight workplace-judgement lessons are unchanged.
- , Rebuilt the lesson page around a sticky contents rail, per-section links, previous/next lesson navigation, and two graded checkpoints drawn from the open practice bank.
- , Repaired the aptitude integrations behind the lessons so each one links to skill-specific practice instead of the unscoped fixture engine.
- , Published one lesson for each of the 35 aptitude skill constructs: objectives, worked examples, practice tips, glossary, Learn topic links, and sources.
These 35 skill lessons are authored and revised as one set, so they share one revision history rather than 35 identical dates.
Objectives
Copy link- Tell a perceptual speed item apart from a reasoning item within the first two seconds, and switch off the analytical approach that costs time here.
- Compare long strings in fixed chunks of three or four characters rather than as a single run, and stop at the first mismatch when the instruction permits it.
- Identify homoglyph pairs (0 and O, 1 and I and l, 5 and S, 2 and Z) and slow down deliberately on mixed alphanumeric strings where they appear.
- Memorise a small lookup key in the opening seconds of a speeded section so the item rate is not limited by re-reading the key.
- Scan a grid or column in a consistent raster order so no cell is visited twice and none is skipped.
- Read a speeded score as correct-per-minute rather than percent-correct, and work out which of two performances wins under the section's actual scoring rule.
Checkpoint: does the idea land?
Copy linkBefore the worked examples, check that the objectives above actually landed.
Two questions from the open practice bank, answered here and scored on this device. Untimed, ungraded, and not added to your practice history, the full bank is where attempts are recorded.
Examples
Copy linkChunk the string, stop at the first mismatch
Compare 4820 6193 5507 with 4820 6913 5507. Read them as three blocks, not as twelve digits. Block 1 matches, 4820 against 4820. Block 2 does not: 6193 against 6913, where the 1 and the 9 have swapped. You are done. On a same-or-different item there is no reason to check block 3, and checking it anyway costs you about a second on every item, which over eighty items is more than a minute of pure waste. The reason chunking works is capacity: a twelve-digit run exceeds what most people can hold for a comparison, so reading it whole forces you back to the source repeatedly, while a four-digit block fits in one go. The instruction wording decides whether early stopping is allowed. 'Are these identical?' permits it. 'How many of the five fields differ?' does not, and stopping early there converts a correct three into an incorrect one. Read the instruction once, classify the section, then run the matching procedure without re-deciding it per item.
Homoglyphs: 0 and O are where the time goes
Three pairs to judge. Nguyen, Thi-Hoa against Nguyen, Thi-Hoa: identical. Muller, Jorg against Mueller, Jorg: different, and the difference is in the surname spelling rather than anywhere in the given name, which is where most candidates look first. RN0O1I5 against RNO01I5: different, because positions three and four hold zero-then-letter-O in the first string and letter-O-then-zero in the second. That last pair is the killer, and it is deliberate. In most screen and print faces, a zero and a capital O differ by a few pixels, and the digit one, capital I and lower-case L can be visually identical. Production systems avoid these characters in generated references for exactly this reason; test writers include them for exactly the opposite one. The practical rule: whenever a string mixes letters and digits, drop your rate for that item, and use context to disambiguate. If a field is described as numeric, an O in it is a zero, and if it is a postcode you can often tell from the format which positions are letters. Guessing on a homoglyph is not a speed decision, it is a coin flip you can avoid by spending half a second.
Memorise the key, then never look at it again
A routing section supplies two small tables. Region: NW = 12, NE = 14, SW = 21, SE = 23, CE = 31. Priority: A = 1, B = 4, C = 7. Each item names a region and a priority and asks for the combined code, so 'SE, priority B' is 23-4 and 'NE, priority C' is 14-7. There are only eight mappings. If the section holds forty items in three minutes, you have 180 / 40 = 4.5 seconds per item, and a candidate who glances back at the key twice per item (once for the region, once for the priority) spends around two seconds of that on lookup alone, which is roughly eighty seconds of the section, or nearly half of it. Twenty seconds spent memorising eight pairs before the first item pays for itself about ten items in and then keeps paying. The general principle for speeded sections: any fixed information that appears in every item should be moved into memory as early as the format allows, because per-item costs multiply by the item count and one-off costs do not.
Cancellation drills and mirror-image distractors
Build your own cancellation drill rather than reusing a published one. Write twenty rows of forty characters drawn only from b, d, p and q, each carrying zero, one or two tick marks above or below. Define the target as 'b with exactly two marks' and cross out every occurrence, timed. What the drill teaches is feature overlap: a p with two marks is a vertical mirror of the target and a d with two marks is a horizontal mirror, and both take measurably longer to reject than an obviously different character would, because they share every feature except orientation. The same effect is why 6 and 9, and M and W, are expensive in real checking work. Two things improve with practice on this drill and neither is eyesight. The first is that you stop re-deriving the target on each row and start rejecting non-targets pre-attentively. The second is that you learn your own decay point, the row at which misses start appearing, which is the information you actually need in order to pace a real section.
Raster order on a scanning grid
A ten-by-ten grid of two-digit numbers, and the task is to mark every value ending in 7. Scan strictly left to right, top to bottom, one row at a time, keeping a finger or the cursor on the current row. The reason is not neatness. Free-roaming the eye over a hundred cells means some cells get visited twice and others not at all, and there is no way to know which is which, so you finish with no idea whether you are done. If you re-visit even fifteen percent of the grid, that is fifteen wasted fixations, and at roughly a quarter of a second each that is close to four seconds on one grid: often the difference between completing the section and leaving items blank. On a two-column layout, treat each column as its own raster and finish it before moving; jumping between columns doubles the re-visit rate. The same discipline transfers directly to real work: scanning a picking list, a passenger manifest or a stock count row by row is slower per glance and faster per document.
Correct per minute, not percent correct
Two candidates, four minutes each. A attempts 62, gets 60 right: 15.0 correct per minute at 96.8 percent accuracy. B attempts 96, gets 84 right: 21.0 correct per minute at 87.5 percent accuracy. Under raw scoring, count the correct answers, B wins, 84 to 60. Under correct minus incorrect, A scores 60 - 2 = 58 and B scores 84 - 12 = 72, so B still wins. Under correct minus three times incorrect, A scores 60 - 6 = 54 and B scores 84 - 36 = 48, and A wins. The same two performances rank three different ways depending on a single line in the instructions. This is why percent-correct is close to useless as a self-assessment on a speeded test: it ignores the rate, and the rate is the whole construct. Log both numbers after every practice session (attempts and correct, from which rate and accuracy both fall out), and compare sessions on rate. A session where accuracy improved but the rate fell is not necessarily progress.
Checkpoint: can you apply it?
Copy linkNow apply it. These come from a later section of the bank, so they are not more of the same.
Two questions from the open practice bank, answered here and scored on this device. Untimed, ungraded, and not added to your practice history, the full bank is where attempts are recorded.
Practice tips
Copy link- Practise in short, intense blocks of two to four minutes rather than long sessions. The construct is a rate under pressure, and a relaxed twenty-minute session trains a different behaviour from the one being measured.
- Never sub-vocalise a string you are comparing. Saying '4820' in your head takes about as long as saying it aloud and caps your rate; comparing the shapes of the blocks does not.
- Deliberately vary the drill format between name checking, number checking, symbol cancellation and table lookup. Speed built on one format transfers less than candidates expect, and real sections mix them.
- Slow down on purpose for mixed alphanumeric strings and speed back up on pure numeric ones. A uniform pace is the wrong strategy when the items have unequal difficulty.
- Fix your scan path before starting (chunk size, direction, whether you finish a column before moving), and do not change it mid-section. Changing procedure under time pressure costs more than the procedure was ever going to save.
- Record attempts and correct answers separately for every session so you can plot rate over time. Scores stay on this device unless you export them, so the log is yours and is worth keeping across weeks rather than days.
Glossary
Copy link- Speeded test
- A test whose items are easy enough that nearly everyone could answer them given unlimited time, so the score reflects how many were completed. Contrasted with a power test, where difficulty rather than the clock is the limiting factor.
- Cancellation task
- A format in which a target character or symbol must be marked wherever it appears in a dense field of similar non-targets, scored on hits, misses and false marks within a fixed time.
- Distractor (perceptual)
- A non-target that shares visual features with the target. The more features shared, the longer the rejection takes, which is why mirror-image pairs such as b and d are the most expensive distractors of all.
- Homoglyph
- A character that looks nearly identical to another in a given typeface: 0 and O, 1 and I and l, 5 and S. The commonest single cause of unavoidable errors in alphanumeric checking.
- Chunking
- Grouping a long string into units of three or four characters so each comparison fits within working memory. It is the difference between one pass over a reference number and several.
- Raster scan
- Covering a field in a fixed order, row by row in one direction, so that every cell is visited exactly once. Its value is not tidiness but the guarantee that the search is complete.
- Rate measure
- Performance expressed per unit of time, such as correct answers per minute. It is the only fair basis for comparing two speeded sessions of different lengths.
- Ceiling effect
- What happens when a test is easy enough that many candidates reach the maximum score, destroying its ability to discriminate. Speeded sections are deliberately long enough that almost nobody finishes, which is why an unfinished section is normal rather than a failure.
Sources
Copy link- All strings, code tables, grids and drills above were written for this lesson. The rate and score comparisons were computed and checked, including the three different orderings produced by the three scoring rules.
- Timing figures given for fixations, lookups and per-item costs are illustrative arithmetic showing the shape of the trade-off, not measured research findings; use your own logged times in their place.
- Terminology (speeded versus power tests, cancellation tasks, chunking, homoglyphs) cross-checked against standard public references such as the Wikipedia articles 'Speed test (psychometrics)', 'Chunking (psychology)' and 'Homoglyph'.
- Novus Learn aptitude construct registry (catalog seed) for construct scope and suite mapping.
- Public educational framing only: not affiliated with any official exam board, publisher or employer, and no copyrighted test item is reproduced.
Your notebook for this lesson
Saved sections and notes are kept in this browser, on this device. No account is required, and nothing is sent to us unless you create one and switch on backup. They travel with your backup file from My Learning, and they are lost if you clear this site’s data.
Saved sections
None yet. Use Save beside any section heading above to keep it here.
4000 characters left
Your own words, so you can find this again from any other lesson. Up to 12.