Instructional Analysis

Here is my image depiction of an instructional analysis.

Project charter – This should not be confused with the project charter in the PM process. However this may contain much of the same information. This should contain the problem, project managers, contact info, background to the problem, ROI information, Project goals, budget and schedule summary. This document will be filled in and modified throughout the whole ISD process. It is usually a 1-2 document.

Learner analysis – Who are the learners? What is their level of education? Can they use computers? smart phones? What is their age? Motivations? What are their work conditions like? What is their job like? Do they prefer a certain kind of training or are they used to a certain kind? (remember if they are not used to it then you need to go through a change process which might involve training and communication on the new process) *Note here do NOT look for learning styles as there is much research against them and they do not help with curriculum development. Learning preferences are NOT the same as learning styles.

Context analysis – What kind of conditions will the learners use these new skills? What are those skills? What kind of conditions will these learners be trained in? Computer labs? Classrooms? On the job? Really answers two questions – where/how will they use these new skills and what are the learning environments like?

Technology analysis – What technology is available? What technology are the users used to? Computer labs? Projectors? ipads? etc. This information may be included in the other analysis sections however I really like to break it down and have this section separate so that developers looking at this document do not need to read between the lines to help give input on technology solutions.

Knowledge of performance analysis (*performance analysis should be completed prior to needs analysis in the front end analysis not described here) – Is there anything else we can add to this? Document analysis? Prior project lessons learned? Results from front end analysis such as surveys/observations? All of that can go here. And if there was no front end analysis done (which is why I include this section) then make sure you have data to add here. If a front end analysis (a good thorough one was completed) then this section may be omitted.

Gap analysis – This is the section where we analysis the problem and analysis to come up with a solution.

Current state – What is the current state that needs to fixed?

Desired state – What is the end desired state? What were the companies goals and what are the new ones for this project?

Potential solutions – What are all of the potential solutions? How long will each take/cost?

Impact of those solutions – How will those solution impact the company? Which departments will those solutions impact? Are any department already doing this? What is the ROI for each of those solutions? How much will each cost? How long will each take?

Solution selected – What solution is recommended to the client?

Goals – What are the goals of this project with this solution? Can you classify them using something like Gagnes categories of learning? (this will help with your task analysis). Do learners have the skills required to complete each of these goals?

Here is a high level view of the Instructional Design process to see where analysis fits in:

To see the sections on Design and Development click the links


Posted in Instructional Design and tagged , , , .

Leave a Reply