"Smart push, warrior pull" to avoid information overload

I came across this phrase - "Smart push, warrior pull" recently, and looked it up online (for example here). It's a very useful military approach to maximising knowledge bandwidth. 

Information overload by SparkCBC on Flickr

The US Department of Defence operates a global broadcast system (GBS) which acts as a knowledge and information transfer system to troops. Like any such communication system it suffers from bandwidth issues, so the transfer of knowledge and innovation must be strictly prioritised. 

"Smart push, warrior pull", inevitably shortened to SP/WP, is a widely-applied principle to do this prioritisation. It represents the two following components;

• Intelligent transfer from central command to the troops on the ground, of the information and knowledge they need at that moment, and nothing more.
• The option for further requests for additional information and knowledge from the troops to the centre.

This is an excellent principle for a lean knowledge supply chain. 

It ensures that people get the right knowledge at the right time, with no waste.

The armed forces and intelligence units operate this way because of the bandwidth limitations of the GBS, but there is no reason why a similar principle cannot be used within organisations: "Smart Push, Front-line Pull" for example, where the customer facing staff, or staff conducting operations or projects, are provided centrally (or automatically) with the knowledge they need for that customer, or that operation, or that project, with the option to ask/search for more if needed. 

Although organisations are less likely to have infrastructure bandwidth limitations, there is definitely an attention bandwidth issue, also known as "information overload". A principle such as SP/FLP would improve the efficiency of the KM system by reducing "knowledge waste" and minimising information overload.