Most builders check their own work by asking, does this make sense to me? That question is broken from the start, because the person asking already knows the answer they’re hoping to hear. You can’t unsee what you built. Once the meaning is baked into your head, every ambiguous line, every awkward crop, every unclear icon reads as obvious, because your brain fills in the gaps automatically.
A Redditor going by u/Asteristix ran straight into that wall while building instructional images for an Android app. The images were made in a long ChatGPT and Codex session, so by the time they were finished, both the human and the AI already knew exactly what each picture was supposed to show. Every prompt, every revision, every back and forth had reinforced the same intended meaning until it felt self evident. Once you know the intended meaning, you physically can’t judge anymore whether the image communicates it on its own. So they built a workaround using a feature most people treat as a privacy setting: Temporary Chat.
The Key Idea
Open a fresh Temporary Chat, upload only the image with a neutral filename, and give the AI zero context. No prompt, no sequence order, no hint at the intended action. Then ask it to describe what it sees, cold. That first, uncontaminated reaction becomes your test. It’s not about whether the AI likes the image. It’s about whether a mind with no prior exposure lands on the same interpretation you intended, using nothing but what’s actually visible in the frame.
Old Way vs New Way
The old way: you or your dev team look at the finished asset inside the same conversation that built it, and every reviewer is already anchored to the intended meaning. Confirmation bias does the rest, since anyone who knows the answer will find a way to see it in the result. Even a second team member glancing at the file in Slack, after reading the surrounding thread, isn’t a clean test. Context leaks in from everywhere: filenames, folder names, the message right above the screenshot.
The new way: a Temporary Chat gets exactly what a real user gets and nothing more. No memory of the build process, no leftover context, no bias. It’s the closest thing to a stranger’s first look you can get without actually recruiting a stranger. It costs nothing, takes under a minute, and doesn’t require pulling a teammate off their own work just to eyeball a screenshot.
u/Asteristix used this to test two nearly identical images (removing a duvet from its cover vs. inserting one) where the real question wasn’t whether the image looked good, but whether a cold reader could tell the two opposite actions apart. That’s the sharpest version of this test: two visuals that are almost mirror images of each other, where a single misread arrow or misplaced highlight flips the entire instruction.
How To Run It Yourself 🔍
- Rename your image file to something neutral, no hints in the filename. Skip “duvet_insert_v3_final” and use something like “img_01.”
- Open a brand new Temporary Chat (context stays isolated, nothing carries over).
- Upload only the image. No prompt history, no explanation, no caption underneath it.
- Ask it to report: the objects it sees, the action and its direction, a confidence score, the strongest alternative interpretation, and which visual detail drove that reading.
- Write down that first answer before you reveal anything else. ✅ Resist the urge to correct it mid conversation, that first response is the whole point.
- If you revise the image, test the new version in another fresh Temporary Chat, never the same one. Reusing a chat means the AI remembers the earlier miss, and you lose the clean read all over again.
One caveat worth repeating: this isn’t user research, and it’s not proof real people will read the image the same way. It’s a bias-free first opinion, nothing more. But that’s exactly what’s missing once you’ve stared at your own draft for three hours straight. If the AI’s cold read matches your intent, that’s a green light, not a guarantee. If it doesn’t, that’s a real signal something needs fixing before it ever reaches a user.
The same trick works past images too. Instructions, forms, quiz questions, UI copy, small games, even full articles built through a long chat all pick up the same anchoring problem. Anywhere a marathon AI session left you too close to the material to judge it fairly, a Temporary Chat gives you back a stranger’s eyes. Next time you finish something in a marathon AI session, don’t proofread it yourself. Open Temporary Chat, upload it cold, and see what a stranger actually sees first.
Using Temporary Chat as a blind product tester
by u/Asteristix in ChatGPTPromptGenius