As a Scrum coach I know of impediments as obstacles in IT development that hinder progress. The idea is to identify these quickly and to address them effectively so that greater progress can be made. Identification, doing a root cause analysis
(as in 5 Why's) and determination of impact are logical steps to follow.
After resolution of one or more impediments we measure what is the effect of resolving them to encourage further impediment removal.
Beware it's more of a philosophy then a process, an active challenging of the status quo, a quick identification and resolution of that which is blocking and measurement of the results.
It is strongly tied to the empowerment of employees
and specifically teams.