I think one good way is to talk about the value of a feature. What values does it add f.e.?
This is a good starting point to ask questions about what problem a feature is trying to solve and what the benefits are. It's more abstract, but if facilitated can encourage thoughts and discussions.
From there a team can start to refine the problem definition and start defining ways to solve the problem.
It mostly starts with how a feature is defined, it should be abstract enough, but also clear enough for whom it is valuable and why.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.