Once I heard that, I could redirect the conversation. We talked through why this particular path wouldn't get him relief on the timeline he needed, and then we shifted to what might. If I'd just answered the question he'd asked, I would have handed him a detailed, accurate plan for solving the wrong problem.
I've also been on the other side of this, where I missed the signal entirely. A direct report shared where they were on a development effort. Technically, the work looked sound, so I told them that and moved on. What I found out later is they weren't looking for technical validation — they wanted to know if there were better methods they hadn't considered, patterns they were missing. They needed a mentor and got a stamp of approval instead.
For a long time my instinct was to read between the lines and act on what I inferred, quietly, without checking. That felt efficient. It's actually a little arrogant — it assumes you've assessed correctly, and a lot of the time you haven't.
The fix I use now is three questions: What do you need from me? How can I help? What else do we need to talk about? Low stakes, direct, and they work whether or not you consider yourself someone who reads a room well. You don't have to read minds. You just have to stay curious long enough to ask.