A quick
60-second usability test can show where a new user hesitates—without a lab, analytics dashboard, or formal study.
Ask someone who hasn’t used your game or tool before to try one small task for one minute. Watch quietly. Can they tell what it does, where to begin, and what happens after their first action?
Set up a fair first tryChoose one small task that shows your product’s main value. For example:
•
For a game: move around and collect one item.
•
For an AI tool: type one sentence and create a first result.
Start from the screen a new user would normally see, on the device you want to check. If sign-up, installation, or permissions are part of the usual first-time experience, include those steps too. Don’t coach the tester or point out buttons they haven’t found. If you plan to record the screen, ask permission first.
The goal isn’t to catch someone out—it’s to notice what feels clear and where they have to guess.The 60-second test0–15 seconds: What is this, and where do I begin? Notice what the tester looks at and what they try first.
15–40 seconds: Can they take one meaningful action? For a game, watch whether they can start moving and try a simple action. For an AI tool, see whether they can enter an input and start creating.
40–60 seconds: Do they understand the response? Look for a result, feedback, or clear status—and whether the tester can tell what to do next. If an AI result takes longer than a minute, can they tell that it’s working and where to find the preview?
Watch what happens, not what you assumeUse a timer and jot down the first action, pauses, misclicks, questions, and feedback the tester sees. A sign-in or setup step isn’t automatically a usability problem; note whether it was expected and clear for the people your product is for.
Try not to explain the interface while they’re using it. You’re looking for clues about the experience, not asking them to perform perfectly.
Ask two questions, then try one improvementAfter the minute, ask:
“What do you think this is for?” “What would you do next?”Their answers can show whether the first screen explains the product well. Pick one confusing part to improve, then ask someone else to try it again. If your product needs to work on phones and computers, test both. One person’s test is a useful clue—not proof that the whole product is easy to use.
What’s the one small task that best shows what your game or AI tool is for? Share it in the comments, and tell us what you’d watch for in a first-minute test.