09 July 2017
Embedded Files
Here, this is a simple yet practical methodology suitable for approaching many types of ID projects. It is called "Graded Decomposition". Although this methodology is simple to follow, it is actually based on many design and learning principles. I don't go through them all to avoid any unnecessary details. It consists of 4 main steps:
1- Set the goal:
1- Set the goal:
What is the goal of this course? Clarify and "prune" your goal: Make it as clear, simple, targeted yet solid as possible. Think of who are the audiences, what they are going to get out of the course, what they would be able to do after finishing the course (that they can't do now) and so forth. It is best for the course title to be a statement that reflects this vision.
2- Slice it:
2- Slice it:
Start with decomposing the top level goal topic and divide it into smaller topics hierarchically. This is actually about dividing into independent topics (independent modules) rather than dividing by complexity level of one subject. We will get back to the level of complexity in the next step: Goal (level G or zero) > High level chapters (Level 1 Modules) > Sections (Level 2 Modules) > ...
How far you should go? Well based on design principles, there is a rule of thumb: As far as you reach a level in which topics (modules) can no more be divided into two or more self-contained and independent topics. We call these "Index Modules" (as these are in fact the topics that can be listed under index)
3- Dig for the desired level of complexity:
3- Dig for the desired level of complexity:
Now it is time to decide what level of complexity is desirable for each "Index Module". This is where you decide how much important this specific topic is and how deep you need to dig. Sometimes it is just an introduction, sometimes it needs much more details or it might need a "skill" that you like to tag for repetition later. Obviously different Index Modules will need different complexity levels based on the goal of the course itself.
The above set of dots will be the body of your course. Try keeping them short and clear. Again, another rule of thumb (which is challenging!) says each block should be no longer than a 4 minutes learning experience (lecture, reading, video, audio, exercise or anything else). A general old rule: the shorter the very much better! if you need more than this you probably need to consider going back to the step 2 and dividing it again (decomposition).
4- Plan the path:
4- Plan the path:
This step looks obvious however here is where the flexibility of this methodology becomes very handy. You can be creative on taking any path to cover all these dots.
Some of the benefits:
1. Very easy to follow and organise for the designer, educator and learners.
2. It provides the designer with many options to adjust the learning experience based on the situation. For example, you may decide to give the audiences the choice to select their desired complexity level of each module so they can tolerate the learning path to match their specific needs. which is awesome! or you can implement "repetition" for more complex levels or skills using a spinal path. These features make the methodology very flexible and powerful,
3. Because of the modules being independent (as much as possible), they can be developed in a parallel way. This can suit both Agile and Waterfall Methodologies.
Google Sites
Report abuse