Prototype would be quicker, 'cause I know almost nothing about computers.
Hi Karen,
Do you think that using a design specification document is preferable to having the designer create a prototype, which would be improved through multiple communication with you? Which would be quicker?
:)
Jane
With design specifications, you give the whole picture to the vendor: analysis, design strategies including instruction goals,media for all learning styles, activities to help students practice, and testing. The vendor would translate the ideas to workable expression on the internet.
I'm going through that process now, so I may be able to answer that question better after we complete the process.
You make a very appropriate distinction between first-time users and experienced users. Too often course designers assume that all learners are the same.
Some argue that the time it takes preparing the Design Specification document could be better spent developing a prototype. Do you agree? Why or why not?
No one knows your audience better than you. A Course Design Specification provides the outsourcer with a methodology that fits your audience needs. As a simple example, think of how differntly one might present navigation of a Windows-based product to a group of first time users versus a group of experienced users. Personally, I would probably present more graphics and animations in my training to first-time users, whereas I may be able to present more menu paths in text format to experienced users. A design specification should make this distinction and allow your outsourcer to present to your audience appropriately.
Needs assessment is definately a necessary step in creating a Design Specification. I also agree that the person developing the course should be able to offer advice as to the feasiblity of many aspects of the design. Do you feel that performing a needs assessment and creating a design specification document will be less costly and time consuming than taking a prototyping approach? Thanks for your input :) Jane
When I create my course design specifications, I create them from needs assessment. When I give my specifications to the company developing the online course, the company should be able look through the specifics and then tell me from experience what will work and what will not work. This will save my company money and time. And also make me a repeat costumer.
Isaac
Kelli,
As a communication tool, a Design Specification Document is invaluable. As with any communication tool, however, there is always the risk of miscommunication. Can you think of some steps to follow in order to ensure that both parties are indeed speaking the same lanugage? Thanks for your input.
Jane
It is a clear communication tool. It would save time and ultimately money. It would make sure that both parties were speaking the same language and keep ideas clear and orgnized.
You make two really good points in your post. Taking the time to create a design specification can save on development time as well as address the feasibility of the project up front.
Some developers, however, prefer to use a prototype approach because it allows design and development to happen simultaneously which, in turn, saves time. The best approach really depends on the dynamic of the course, customer, and development team.
Good post!
It would lead to clear cut requirements for the course and make the developement of that course much quicker since the design specifications were a know from the beginning. The vendor would know up front what pieces needed to be developed into this course and if they were capable of developing all the required elements, for me there would be less adjusting since the fundaments elements were already pre-requested.
