You probably have a vision statement don't you? Do you? A strong vision statement is required before you'll be able to drive towards any goals. So how do you write a vision statement? What content do you need that makes it useful? How do you write one that IS useful? I always found this article from Joel on Software to be helpful. Particularly this part:

This product vision model helps team members pass the elevator test -- the ability to explain the project to someone within two minutes. It comes from Geoffrey Moore's book Crossing the Chasm. It follows the form: