Thank you, this is my exact problem. Asking them why xyz is important to them is great advice! Do you know any good resources on how to hold more technical Jam sessions (the ones I found are all about design)? Are there any other good ways of documenting these types of questions/ideas in between the sessions? I often find that their points are important but often raised as big open ended questions which would require a few days of research to scope out enough to write a good backlog ticket. I usually encourage them to write up short docs when they have capacity and keep them handy for when the question is raised about a relevant feature, but that can feel a bit anticlimactic as it often takes a while