NOTES / FROM LINKEDIN
NOTES / FROM LINKEDIN
NOTES / FROM LINKEDIN
Test where users look before you test if they can use it
Test where users look before you test if they can use it
Test where users look before you test if they can use it
MOSTAFA ESMAEILI · OCT 30, 2026 · 2 MIN READ
MOSTAFA ESMAEILI · OCT 30, 2026 · 2 MIN READ
Most teams test whether users can use a new feature. Almost nobody tests whether they’d look for it.
Most teams test whether users can use a new feature. Almost nobody tests whether they’d look for it.
Most teams test whether users can use a new feature. Almost nobody tests whether they’d look for it.
THE SHORT ANSWER
THE SHORT ANSWER
THE SHORT ANSWER
Test findability before usability. A feature people can use but never find does as little as a feature you never built.
Test findability before usability. A feature people can use but never find does as little as a feature you never built.
Test findability before usability. A feature people can use but never find does as little as a feature you never built.
THE NOTE
THE NOTE
THE NOTE
What went wrong with our bank account feature?
What went wrong with our bank account feature?
What went wrong with our bank account feature?
At walllet.com we merged a bank account into the Deposit flow. Users could not find it. In their heads, we were a crypto wallet, so nobody went looking for a bank account inside Deposit.
At walllet.com we merged a bank account into the Deposit flow. Users could not find it. In their heads, we were a crypto wallet, so nobody went looking for a bank account inside Deposit.
At walllet.com we merged a bank account into the Deposit flow. Users could not find it. In their heads, we were a crypto wallet, so nobody went looking for a bank account inside Deposit.
We learned it from support tickets.
We learned it from support tickets.
“In their heads, we were a crypto wallet.”
“In their heads, we were a crypto wallet.”
“In their heads, we were a crypto wallet.”
Why don’t usability tests catch this?
Why don’t usability tests catch this?
Why don’t usability tests catch this?
A usability test usually starts by pointing the participant at the feature: “Open Deposit and add your bank account.” From there, people can often finish. The test tells you whether the flow works. It never asks whether anyone would open it on their own.
A usability test usually starts by pointing the participant at the feature: “Open Deposit and add your bank account.” From there, people can often finish. The test tells you whether the flow works. It never asks whether anyone would open it on their own.
A usability test usually starts by pointing the participant at the feature: “Open Deposit and add your bank account.” From there, people can often finish. The test tells you whether the flow works. It never asks whether anyone would open it on their own.
Findability depends on the mental model people bring to the product. If they think they’re using a crypto wallet, they won’t look for banking under Deposit, however good the flow behind it is.
Findability depends on the mental model people bring to the product. If they think they’re using a crypto wallet, they won’t look for banking under Deposit, however good the flow behind it is.
How do you test where users look?
How do you test where users look?
A cheap version I’d use: show someone the home screen, name the task, and ask where they’d tap first. No working flow needed, just the navigation.
A cheap version I’d use: show someone the home screen, name the task, and ask where they’d tap first. No working flow needed, just the navigation.
Run it before design starts, and again after the first build. If people tap somewhere else, fix where the feature lives before you polish the flow.
Run it before design starts, and again after the first build. If people tap somewhere else, fix where the feature lives before you polish the flow.
DESIGN RULE
DESIGN RULE
Test where people look first. Then test if they can use it.
Test where people look first. Then test if they can use it.
Test where people look first. Then test if they can use it.
FAQ
FAQ
Questions people ask
Questions people ask
What is findability testing?
What is findability testing?
A test of whether people can locate a feature on their own, before anyone shows them where it is. It checks the navigation and the user’s mental model of the product, not the flow itself.
A test of whether people can locate a feature on their own, before anyone shows them where it is. It checks the navigation and the user’s mental model of the product, not the flow itself.
How is findability testing different from usability testing?
How is findability testing different from usability testing?
Usability testing asks whether people can complete a task once they’re in the right place. Findability testing asks whether they’d get to that place at all.
Usability testing asks whether people can complete a task once they’re in the right place. Findability testing asks whether they’d get to that place at all.
What is the cheapest way to test findability?
What is the cheapest way to test findability?
Show someone the home screen, describe a task, and ask where they’d tap first. It needs no working build, so you can run it before design starts.
Show someone the home screen, describe a task, and ask where they’d tap first. It needs no working build, so you can run it before design starts.
ORIGINALLY ON LINKEDIN