Myth #4: Design documents are not necessary
Design documents are fundamental to the success of training projects, helping define target audience, level of difficulty, training objectives, course structure, and instructional design strategies. Further, they serve as a reference point throughout the project, ensuring consistency, quality, and scope.
Reality
The design document defines the primary and secondary roles the training is intended for. It also clarifies the expected personas (prior knowledge, skillsets, vertical industries) of these different roles. Following are example target audience roles and personas:
Primary roles: Data Engineers, Data Architects
Secondary roles: Data Analysts, BI Engineers
Personas: Technical Beginners, Manufacturing Specialists
Target audience
The design document clarifies the difficulty or complexity of the knowledge and skills to be learned. This helps set expectations and assign prerequisite knowledge and skills. Following are example course levels:
100 - Fundamental
200 - Intermediate
300 - Advanced
400 - Expert
Level of difficulty
The design document ensures a business-aligned and performance-based learning experience by defining the business problem statement, terminal learning objective (TLO), and enabling learning objectives (ELOs).
Training objectives
-
A single statement clearly defining the customer opportunity or business problem we are trying to solve via a training solution.
Related questions:
What evidence (data/anecdotes) leads you to believe training is the right solution for this problem?
Are the current vs. desired business and performance goals and their measures clearly defined? (helps ensure we can show the impact of our work to the business)
-
A single statement of the desired observable behavior learners will start performing as a result of the training solution. A multi-course training program will have multiple TLOs.
Examples:
Deploy a custom implementation of solution X so that you can achieve benefit Y.
Perform task X so that you can achieve benefit Y.
Related questions:
What is the performance context? (Typically includes related workflows, people collaborations, tools/applications, and documentation/resources needed to properly perform the terminal behavior)
What is the degree of mastery? (A clear measure of how well the terminal behavior needs to be performed)
What assessment mechanism are we going to use to validate success? (Provides evidence that the learners have achieved the terminal behavior)
-
A collection of statements to define the supporting knowledge and skills critical to achieving the terminal learning objective.
Examples:
Recognize challenges a customer can have because they are not using solution X.
Identify the benefits and impact of implementing solution X.
Demonstrate performing the tasks and steps of solution X.
Related questions:
What does the target audience need to do and know to be able to properly perform the terminal behavior? (e.g., workflows, processes, tasks, steps, concepts, and guidelines)
What makes the behavior change difficult? What mistakes is the learner making when trying to take desired actions? (Helps identify the learners’ attitudes and potential difficulties preventing them from learning or performing)
Dr Philippa Hardman suggests the following elements of a well-written TLO:
-
The terminal learning objective makes it clear to the learner what they will DO. We don't yet care about what they need to know (knowledge) or feel (attitude).
-
The terminal learning objective is labeled with information on where it sits in the learner’s Zone of Proximal Development (entry, mid, or mastery level of difficulty). This enables us to sequence objectives with entry to mastery, which plays a key part in driving learner motivation.
-
It is clear to the learner that there is a concrete outcome achieved in less than an hour, which drives a sense of mastery.
-
The terminal learning objective makes it clear to the learner why they should do this, which drives intrinsic motivation. Make sure the “So what” or value proposition is always clear.
-
Define
Identify
Indicate
Label
List
Match
Name
Outline
Quote
Recall
Recite
Recognize
Record
Relate
Repeat
Select
State -
Classify
Compile
Conclude
Contrast
Discuss
Describe
Explain
Express
Give original examples of
Identify
Interpret
Paraphrase
Recognize
Restate
Summarize
Translate -
Apply
Calculate
Demonstrate
Develop
Illustrate
Interpret
Locate
Operate
Model
Perform
Practice
Predict
Present
Query
Report
Solve
Use -
Analyze
Consider
Explore
Associate
Break down
Calculate
Categorize
Classify
Criticize
Compare
Contrast
Determine
Diagram
Differentiate
Distinguish
Examine
Illustrate
Outline
Simplify
Test -
Argue
Assess
Choose
Compare
Contrast
Convince
Critique
Decide
Defend
Determine
Establish
Evaluate
Grade
Judge
Justify
Measure
Rate
Recommend
Relate
Select
Support -
Arrange
Assemble
Build
Compose
Configure
Construct
Create
Derive
Design
Develop
Diagnose
Formulate
Generate
Invent
Manage
Modify
Organize
Plan
Propose
Relate
Summarize
The following is a list of sample action verbs organized via the cognitive processing dimension of Bloom’s Revised Taxonomy.