[Stakeholders] How do you handle requirements conversations when stakeholders are describing symptoms instead of root causes?

I usually start by taking the symptom seriously without treating it as the whole problem. If a stakeholder says something like, "This process is too slow" or "We need another approval step," I want to understand what they are actually seeing underneath that statement. What is happening, how often, where in the process, and what consequence is it creating? Symptoms...