How do I tell what users really need from what they say?
You can run discovery now, but the gap between what users say and what they need still trips you. That gap trips everyone, because people are honest and still wrong about themselves. They describe a solution when what they have is a problem. Reading past their words is the real craft. When someone asks for a faster horse, they do not want a horse. They want to get somewhere sooner. The words point at the need without naming it. Your job is not to take the request at face value or to ignore it, but to keep asking why until the actual problem shows itself. Next interview, when a user asks for a feature, do not write it down yet. Ask what they were trying to do when they wished for it. Ask what they did instead. The need lives in the story around the request, not in the request itself. Chase the story and you will find it.