@Jerson - I agree completely, at the end of the day the client has the last say, no matter what I advise them to do.
@Karen - here's an example of my point...
Once or twice a year, my family and I hire a cottage. Each time we talk to the owners they say "There is a key in a keysafe that gives you access to the cottage, here's the code, give me a ring if you have any problems". Never have they had to explain that a key has a handle, then a long shank, is usually made of metal, the direction that it gets put into the lock, and what purpose the lock has.
This is very similar to a piece of eLearning, IMHO. I have taken many hundreds of online courses, and I think that on every one I have pretty much figured out for myself what > and the various other navigation symbols and words mean, that "Resources" (for example) might have some useful things in it, and that "Exit" means I can leave the course that way.
I think there is a huge case for the user exploring the course, however, if there is (for example) there is a menu on the left-hand side, do we really need to explain what it is?
For me, Navigation is like "...a quiz at the end of a course..." - we should ask whether it REALLY has any point, and whether it is required. I think in many cases that Navigation can probably be replaced by other things, such as good and obvious design principles combined with the intelligence of our users.