| Here's a brief outline of
the process used by us to design a CBT/WBT.
We have taken the case of a software demo/ tutorial for
the example.
1. We would begin by getting a detailed requirement list
from the client.
It would essentially be an exercise
to familiarize ourselves with the purpose, intent of the
CBT (to determine for instance, if the CBT would cover
all software tools thoroughly or if certain topics can
be just skimmed through), who the end users are ; what
their expectations are (to enable us to mark areas we
need to lay special emphasis on). For instance, in the
case of a software CBT, the skill level of the end users
would govern the content of the CBT.
The comfort level of the end users would also influence
the navigation and basic design of the CBT.
Is the CBT to be used on the web or
intranet for online training or for offline training?
While in almost all the cases a CBT is used for one-on-one
training, we still need to confirm if it is going to be
used on a large screen for a group of people or if it
is going to be a one-on-one training module? Is it going
to be used for instructor led training or independent
training?
The screen resolution of the computers
on which the CBT would be used.
Whether it would be completely auto-flow
or whether it would be interactive allowing the user to
move both among and within sections. Or would it be part
auto-flow and part interactive. The brief intro about
the software could for example be auto-flow requiring
the user to sit back and listen. The actual lessons on
usage of software however, would be interactive.
Is voice over required?
Is professional copywriting required?
Is professional technical writing required?
2. Collect existing manuals, documentation
and any in-house training material developed.
3. Identification of the tools which
are most often required to be used. Identification of
areas of special focus.
The usage of these tools would be demonstrated through
screenshots and autoplay demos, accompanied by either
voice over or tool tips with arrows. Autoplay demos would
be created using screen capturing software. If it is not
possible to get a copy of the software, we would use screenshots
and create demos using flash.
4. Deciding on a navigation system,
flow of presentation between sections, skip buttons to
skip sections a user may have familiarity with.
For instance, we could decide on the
following format or flow of the presentation:
It could start off with the software
title and other details followed by Benefit statements.
This would form part of the intro, which
would be skippable if the user wants to directly reach
the training part.
The actual training module’s navigation
system and content would be decided upon based on 1, 2
and 3.
In the end, there would be a synopsis.
A basic bulleted list, mentioning the key features and
benefits vis-à-vis the relevance of the software
to the end-users.
A small ‘Take a test’ option
could be given where an action would be required from
the user after each question is put to him. The user would
be required to click on a particular tool on the software
screenshot in response to the question. If the right area
of the screenshot (tool) is clicked, it would take him
to the next screenshot and so on.
FAQ section: to answer users questions
on how to use the CBT.
Copyright information, References, Contact
email and any other useful data. : On exit screen.
5. Get clients approval on storyboard.
6. Develop a prototype to finalize the
look and feel of the cbt.
7. Commence work on the design and development
of cbt. |
