What is Abstract & Pattern Reasoning?

Signs it is missing

Competencies are easier to spot by their absence. These are observable behaviours, not personality judgements — each one is something a colleague could describe from memory.

• —Needs the rule written down before starting, and stalls on work where the rule has to be worked out from what is in front of them.
• —Learns a new system by memorising the click path rather than the model behind it, so the first unfamiliar screen stops them.
• —Repeats a diagnostic sequence on a fault that has already failed it twice, because the pattern across incidents was never named.

Evidence to look for

You cannot interview for an ability. Asking somebody whether they are good with numbers, or careful with detail, measures their self-image and their confidence, and both are poor proxies. What an interview can do is send you to the work. Each prompt below points at something the person actually produced — the evidence is in the artefact, not in the answer.

1. Their first week on an unfamiliar system: how much of it they worked out themselves, and what they had to be told twice.
2. A recurring fault they investigated — did they name the pattern across incidents, or handle each one fresh?
3. A process they inherited with no documentation, and how much of its logic they were able to reconstruct before asking.

These are work-sample and observation prompts written for this page. They are deliberately not items from a live AssessAll instrument — published items stop measuring anything.

How to develop it

The development moves AssessAll puts in a growth plan when this competency is a person's priority area. Each is small enough to start this week.

• →Practise matrix puzzles daily; always name every changing attribute (shape, count, rotation, shading) before answering.
• →When stuck, test one attribute at a time instead of staring at the whole figure.
• →Review misses by writing the rule in one sentence — build a personal catalogue of transformation types.

What measures abstract & pattern reasoning on AssessAll

Every form below reports a band for this competency. Item counts and time limits are the configured values, published here because they are the two numbers that decide what a score means and the two that vendors most often leave off a product page — a form with 20 items in 10 minutes and a form with 20 items in 25 minutes are not measuring the same thing.

Seconds per item is arithmetic on the two published columns, not a separate claim. Read it as the working pace the form assumes: under about 45 seconds an item, pace is part of what is being measured whether or not the product says so. See speeded test for why that distinction changes how the score should be read.

Often confused with Logical Reasoning

How AssessAll measures it

Abstract & Pattern Reasoning is not measured by a single question. Responses across an assessment map to the competency, roll up into a 0–100 score, and are interpreted against the four anchors above. Because every AssessAll assessment speaks the same competency language, results from different instruments accumulate into one profile rather than a pile of unrelated scores.

Aptitude items are multiple-choice and machine-scored against a key, so the band is reproducible and the whole form can be sat in under half an hour. That is the trade: an ability score is cheap, fast and comparable, and it tells you what somebody can work out — not what they will choose to do, which is what the behavioural competencies are for. Read one band beside the other rather than either alone, and browse the assessment catalogue or the store for the forms above.