ie keep asking your boss for the long term goal/strategy plan, give constructive suggestions to your boss (Boss, it would really help if you could define what our long term goal is ...) etc. You can also lead by reverse example - if you boss fails to set an agenda/goal, then go ahead and define one yourself and publicise it ... your boss will either agree with it, or if he disagrees, will hopefully come up with his own - either way, you have the long term goal. Other things you can do is coach (constructively) your team mates, recognise the work they do etc.
When reading through the article, employees should realise that their 'motivation' is not dependent solely on the boss - almost all of what the article describes can and should be practised by employees as well.
Sometimes I email the whole team, sometimes two or three people, sometimes just him. Sometimes I want him to learn something, but instead I ask on my email, based on his extensive experience in general areas of life and stuff, what he thinks about the article. Sometimes I say "hey boss I've been reading articles about management tonight here's a dump of them", sometimes I say "hey boss remember last week when we mentioned X, well here's more, what do you think?".
Actually that's a pretty good strategy, asking "what do you think, please share your wisdom and enlighten me", or "a friend passed me this article saying it's good but I'm not sure yet, what do you think". You get the idea. This is good because the boss likes to be seen as a reference, a bastion of smartness, but it's bad because he might see you as someone who doesn't know stuff, and worse, someone who constantly admits that (some realpolitikal companies don't like this behaviour).
Anyway, just always send stuff.
If main developers go away you are busted, dear boss. I busted mine some months ago. And now I am boss of myself and very happy of it :)