Scrum assumes impediments get raised, typically in the Daily Scrum. In practice, a substantial share of real impediments never get explicitly raised at all, which makes the discovery problem at least as important as the solving problem.
Why impediments go unreported
Normalization. An impediment present for months stops registering as "an impediment" and starts registering as simply "how things are here."
Perceived unsolvability. Team members sometimes correctly judge that raising something beyond the Scrum Master's power to fix isn't worth the effort.
Attribution to self rather than system. A team member struggling with unclear requirements sometimes attributes the difficulty to their own inadequate skill, rather than a legitimate systemic impediment.
Social cost of raising blame-adjacent impediments. An impediment caused by another team or individual carries real social risk to name directly.
Better discovery mechanisms than waiting for the Daily Scrum
Direct observation: watching for hesitation, frustration, or quiet workarounds, rather than relying entirely on people to proactively announce problems.
Explicitly asking about normalized friction: a periodic "what's become 'how things are' that's actually still a real problem?" surfaces impediments that won't come up through passive listening.
Making it explicitly safe to name organizationally-caused impediments, framed as system problems rather than individual failures.
Solving what gets found
Impediments split into those solvable within the team and those requiring organizational-level intervention. The second category requires the Scrum Master to actually escalate and advocate outside the team, often where the most consequential, longest-standing impediments actually get resolved.