Last week, client Xiaolin told me on a video call that the buttons "weren't smart enough," and I nearly rebuilt the page. I got stuck here too — only later did I realize he might not have been talking about the buttons.
Then I read Raymond Chen's Windows UX observations, posted August 25, 2003 from a Redmond developer's seat: same flow, some users call it bloated, others call it clear. People don't just see the interface — they project their own experiences, expectations, and worries onto it. Chinese doesn't carry the "Rorschach test" backstory, and that's fine — here it doesn't mean diagnosing from inkblots; it means one sentence often gets read differently by different people.
I started logging in four columns: client's exact words, what I observed as fact, possible preference or worry, next step to verify. For example, rewrite "not smart enough" into "Tuesday on mobile, the client tapped twice and couldn't find export," then ask what hits them hardest — speed, memory load, or fear of losing data. Money: $0. Time: ~15 min the first run, ~5 min each after. Tech barrier: copy-paste text and draw a 4-column table. First step: open your usual notes app, hit "New" in the top-right corner, and title it "Client words / Facts / Guesses / Verify."
This method isn't for everyone; if requirements aren't flip-flopping, you can skip it for now. If you're just starting and don't have many clients, I'd run it once before any major redesign to surface the worst worries. If you already have 1-2 clients, I'd keep one page open during every requirement review so misunderstandings don't snowball into delivery. If you're scaling, I'd have sales, delivery, and design share one sheet, and feed fresh phrasings into the FAQ.
