The everyday problem
A recurring blocker can become routine when each team sees only its own queue. The provider waits for information; the internal team sees repeated requests. A joint review can reveal why the same issue returns and which part of the process should change.
A practical approach
Group blockers by cause and trace a few examples across the organizational boundary. Assign a shared action with a clear owner on each side. Review whether the action reduced recurrence rather than closing the discussion when an individual case is resolved.
Try this with your team
Choose the most common blocker from a sample report. Draw the information path and identify the earliest point where the missing input could be supplied.