You cannot test it on yourself, for a reason you already know
You know what the design says, so you will always be able to find the message in it. The curse of knowledge applies to pictures exactly as it applies to sentences. The only instrument available is somebody who does not already know.
The good news is that the tests that work are cheap, fast, and need no software.
The five-second test
Show the design for five seconds. Take it away. Ask two questions:
- What was that about?
- What did it want you to do?
That is the whole test, and it directly measures the thing hierarchy exists for. If three people give three different answers, you do not have a hierarchy problem to investigate: you have the answer already.
Five seconds is generous. A poster gets less, a feed gets a second and a half. Use five because it produces an answer rather than a shrug, and remember you are grading against a harder standard than the one you tested at.
The explain-back test
For anything longer (a video, a page, a brochure) hand it over, say nothing, and afterwards ask them to explain it to you as though you had not seen it.
The gap between their account and your intention is the measurement. Three specific gaps are common:
- They get the subject and miss the point. The piece is clear and says nothing.
- They repeat your words back without content. They have absorbed the phrasing and not the claim.
- They fixate on a detail. Something in the piece is louder than the message, and now you know which thing.
The first-click test
For anything with an action in it: where would you tap to do X?
This one is worth knowing because the first click is unusually predictive. People who begin a task by going the right way finish it far more often than people who begin wrongly, and recovery from a wrong first move is much rarer than designers expect. If the first click is wrong, nothing downstream saves it.
How to run it for nothing
- A family member who is not in your field. The requirement is not expertise, it is ignorance of this particular project.
- A neighbour, a shopkeeper, the person next to you in a queue. Ten seconds of somebody’s time is not a big ask and most people are pleased to be asked.
- A group chat: post the image, ask the two questions, do not explain first.
- Public critique communities, which are free and mostly generous, provided you show the brief so people are critiquing against the right target.
Five people is a good first batch. You will read that five testers find 85 per cent of problems, and that figure comes from a model assuming every problem is independent and roughly equally likely to be noticed. Real problems are not equally likely, and distinct groups of users hit different ones, so the honest version is: five is enough to find the obvious failures, and not enough to conclude there are none.
The two things that ruin a test
Explaining the design first. The moment you say “so this is about the workshop’s new hours”, you have installed the answer in their head and the test is over. Hand it over in silence. This is much harder than it sounds and it is the single commonest way people waste a tester.
Asking whether they like it. Liking is not a measurement and people answer it socially: they will say yes to be kind, and they will say it about a design that told them nothing. Ask what it said, what they would do, what they noticed first. Never ask what they think of it.
Watch the hands and the face
What people do is more reliable than what they report. Somebody who pauses, squints, turns the page back, or scrolls past and returns has told you something they will not say out loud, often because they have already blamed themselves for not understanding.
That self-blame is worth knowing about: when a design fails, most people assume they were being slow. They will not report the failure, and it is still a failure.
The limitation
These tests measure comprehension, and comprehension is not the whole job. They will not tell you whether the piece is moving, whether it will be remembered next week, whether it suits the client’s standing, or whether it will work in a market you have not sampled. Five friends in one city are not your audience.
They are also blunt about degree. They reliably distinguish clear from unclear and are poor at distinguishing good from better, which means they are for catching failures rather than for choosing between two strong options. For that you need the brief, a judgement, and a willingness to decide.
Every lesson here is open. Your progress is recorded once you pass the Making Things with AI exam.
Check your understanding
Why does explaining the design before a five-second test invalidate it, rather than merely helping the tester get started?
Pick the one you would defend. Your answer stays private.
Stuck on something?Ask Meher, your AI tutor