Planning, Part II:
Produce a Style Manual
A Style Manual documents the standards required to ensure the consistent quality of the various elements of the project.
Look and feel
- Text styling
- Buttons and Navigation
- Page size and specifications
- Keyboard conventions and equivalents
Determine and Collect Resources
This reminds me of my style in cooking and baking. When I begin, I assemble the ingredients so I have them on hand. Gathering these resources serves to organize the project:
- Subject Matter Resources: for my project this would include online resources outlining altar server responsibilities, diagrams available from the parish, and the General Instructions on the Roman Missal (GIRM)
- Instructional Design Resources: I will be referring back to two of my textooks:
- Multimedia for Learning: Methods and Development (Alessi and Trollip)
- The Systematic Design of Instruction (Dick, Carey, and Carey)
- Delivery System Resources: I will be using Adobe Captivate 6, lynda.com, and YouTube in order to develop this training program
- Computer Tools to Facilitate the Use of Resources: If the project is large and detailed, a database or spreadsheet may be used to organize resources for easy reference.
Conduct Initial Brainstorming
Brainstorming involves the free sharing of ideas among a small group of people while suspending judgment. This facilitates a creative approach to the project. All ideas are gathered into a list of potential ideas and approaches for the project for future reference. We brainstormed during our first meeting in order to identify the training needs; I still feel more brainstorming would be useful until I am able to finalize the approach, but I’m not quite certain who would be best for this activity.
Define the Look and Feel of the Project
This may involve the writing of scripts, the creation of drawings or storyboards, and prototyping. A sample Fair Employment Practice prototype is provided for guidance.
Obtain Client Sign-off
Several areas of a project may require client sign-off to ensure effective communication and to prevent misunderstandings, wasted efforts, and project creep.
- Target platform
- Look and feel
- Learning methodology
- Graphics standards
- Content treatment
- Data Collection Requirements
- Privacy issues
- Target user characteristics
- Tools to be used for development
- Client and developer responsibilities