We have clients who consider their organization to be technologically advanced and yet they are shocked to find that their desired eLearning strategy is, even today, infeasible for a large percentage of their learning community. Bandwidth limitations to some locations make the eLearning products fail. For that reason, we offer multiple delivery methods from the same codestream. In other words, we create the courseware once and from that we post-process into two deliverables: (1) a version which runs on the client, and (2) a version which runs on the intranet. This is not an HTML course with limited graphics and limited interaction, content only as good as it can be while still downloading acceptably. These courses are graphically rich and highly interactive. The trick was making them "thin" enough to run well on the vast majority of intranets. We put in everything that we want the user to have and then we make it perform.
Everyone gets exactly the same training, graphically rich and highly interactive. The only difference is when the content is downloaded. Take the example of one of our 3-hour courses. The intranet user downloads the 6MB content to their browser in segments over the 3 hours. The client user downloads the 6MB initially. As your bandwidth improves to those locations where it is currently poor, you can switch those locations to the intranet version. What matters most is that the training is accessible. Put both versions on your intranet. Fundamentally the only difference is the size of the "chunks" that get sent over the network to the user.