Jeppesen_Jan_2001_web
Download
Report
Transcript Jeppesen_Jan_2001_web
Creating Award-Winning
Products
Multimedia Strategies
We’ve Always Done It This Way
Keep up with the “Joneses”
• Competition moving to online delivery
• Upper management dictate: we will keep up
with technology
– CD products
– Web products
We’ve Always Done It This Way
Multimedia is not the be-all and end-all
• Not always appropriate
• Start small
• Add features later
We’ve Always Done It This Way
Multimedia is not paper
• Cannot simply copy existing materials and add
multimedia “pizzazz”
• Requires special skills to be developed or
added to department
• Requires new processes to manage and
complete development
• Can cost a lot more to develop
We’ve Always Done It This Way
Web-based products are not CD products
• Cannot simply convert to web format
• Multimedia on the web
– What technology can we assume that user has?
– What level of performance will highly motivated
users tolerate?
Creating and Meeting Design
Objectives
Objectives same as our paper-based
products:
• Improve understanding and retention and
maintain student interest in the material
Tools are different:
•
•
•
•
Interactivity
Animation
Video
Audio
Creating and Meeting Design
Objectives
Put navigation and content control into the
hands of the users
• Adult learners want to be in control of their
own learning
• Improves users’ understanding and retention
as they follow links that make sense to them
• Design elements
– Ball flags
– Pop-ups
– Discovery points
Creating and Meeting Design
Objectives
Provide users plenty of opportunities to
ensure they learned what they were
expected to learn
• Vary types of questions to ensure users able to
apply knowledge
• Design elements
– Pre-tests
– Practice
– Exercises
– Tests
Creating and Meeting Design
Objectives
Use video, animations, and audio to
redirect or recapture users’ attention
• Constant use of such features makes users
“immune” to their effects and you can lose
their focus
• “Unexpected” keeps users guessing and
“wakes them up” at key points
• Judicious use improves overall internet
performance
Creating and Meeting Design
Objectives
Make the interface a tool, not an obstacle,
to learning
• Users should be able to learn the interface
(how to navigate, where to find information) in
moments
• Since audience is the same on so many of our
products, should we design one Jeppesen
standard for all products?
Creating and Meeting Design
Objectives
Creating and Meeting Design
Objectives
Make the interface a tool, not an obstacle,
to learning
• Three products:
– Three development tools
– Three interfaces
– Three purposes
• Better to ensure the interface meets the goals
of the individual product and audience, than
force a standard, as long as the interface
meets the stated objective
Hiring the Right Expertise
Required skills for team
•
•
•
•
•
•
•
•
Project management
Instructional design
Writing
Multimedia
Interface design
Graphic development
Back-end programming
Testing/Quality Assurance
Hiring the Right Expertise
Retrain some existing personnel
• Writing for online presentations
• Designing graphics for online presentations
• “Programming” in HTML, Flash
Hiring the Right Expertise
Instructional Designers
•
•
•
•
•
•
Write objectives
Define lesson structure
Identify building blocks
Add motivators
Design learning activities
Create effective test questions
Hiring the Right Expertise
Multimedia Specialists
• Interface design
– Look and feel
– Buttons
– Navigation
• Authoring tools
• Templates
Hiring the Right Expertise
Web Programmers
• “Backend” programming
– Ordering
– Tracking
– Scripting (JavaScript, PHP, etc.)
Hiring the Right Expertise
Building the Team and Defining Roles
• Quite a bit of overlap between what each team
member thought he/she should be doing
• Where do you draw the lines between roles?
– Can writers change text without going through
programmers?
– Can writers change HTML?
– Where do “programming standards” cross the line
into instructional design?
Establishing a Quality Process
Planning Documents
• Training plans
• Interface design
• Programming specifications
Establishing a Quality Process
Prototyping
• Sample lesson as soon as possible
• Usability testing on “real” users
• Redesign before proceeding
Establishing a Quality Process
Editing and Testing
• SME edits
• Quality assurance tests
– Technical accuracy
– Functional integrity
• Performance testing:
– Browsers
– Access speeds
• Usability testing (yes, again)
Establishing a Quality Process
Maintenance
• Needs to be part of process from the beginning
• Plan for frequency and logistics of
maintenance
• Updateability of web does not give permission
to forego process
Results
Maneuvers
JeppChart Training
CFI Renewal