I've started reading Creating Successful E-learning by Michael Allen. It is an interesting read so far and Allen's thinking seems to be very pragmatic. A thought hit me while reading the book that maybe I've given too much attention to the storyboard in my course development process. I'm even thinking I don't need a separate storyboard step since the course itself serves as the storyboard. Because of this, I think I'll go back to the development process I'm writing and give more attention to the learning objectives than to the storyboard.
I'm using rapid development tools which make it easy to change the course on the fly. If I have to change a learning objective late in the process it is a bigger deal than changing the way a learning objective is presented to the learner.
The current training project I am working on has brought this to my attention because the learning objectives were a little fuzzy from the start. I am taking a brick and mortar classroom based course and putting it online in a self-paced format. It was decided that I would not cover everything in the course for the first release of the online version; however, as I was developing it I realized that I needed to cover some of the omitted objectives from the classroom based course after all. If we had spent more time on the objectives earlier, we might have caught this problem. I don't want learners to feel they are missing out when they take the online version of the class.
What's your experience with objectives in relation to the course development process?