Skip navigation.

Module 1: Goal and Task Analysis

Printer friendly version of this module

Apply

As with so many other skills, one of the best ways to learn how to build individualized instructional tutorials is to build one!

Choose an instructional outcome

The first step is to decide what you want to teach. This might seem a little backward—usually we like to start by finding out what people need to learn. But for your first foray into tutorial-building we'd like to keep the "overhead" low, and let you work with content with which you are already familiar.

So that's the first criteria:

If it is work-related, make sure no one is depending on getting it by a certain deadline, or in a particular format, that may conflict with course schedules and requirements. Better to choose something non-work related. It could be something you're learning from this or another EDTEC course. It might relate to a sport you play, a hobby, or some other interest you have.

That might seem obvious, but it's kind of important. You're going to need to work on this for several weeks, and if you lose interest in the content after just a few days, it'll be harder to stay excited about the work. If in doubt, choose something that has interested you for a long time—there's no reason to think that this project will suddenly kill a life-long interest.

"Useful" means valuable—to someone. Is there an audience who will use and appreciate your tutorial? No fun making something that no one will ever use. Your audience could be other EDTEC students, school teachers or pupils, military or other government personnel, or corporate workers or managers. They might be instructional designers, writers or editors, mathematicians, automobile mechanics, junior lifeguards, amateur equestrians, police officers, dieters, chefs, or biologists.

This next one is trickier, but vital.

If you decide to teach something too simple—remembering a single fact, for instance—your tutorial may be done almost before you've begun. Pick something that involves learning several facts, or several ways to discriminate a concept, or several steps in a procedure, or applying several rules, and so forth.

This leads naturally to the next step, which is to...

Conduct a task analysis

Outline the sub-tasks or sub-ideas involved in your topic.

The sample tutorial for this project illustrates nicely how to build in adequate richness. The sample tutorial is on ordering numbers—fractions in particular. It involves learning four different rules—one with two sub-rules—for ordering fractions:

  1. When the denominators are the same, the larger numerator indicates the larger fraction.
  2. When the numerators are the same, the smaller denominator indicates the larger fraction.
  3. When the numerator is larger AND the denominator is smaller, the fraction is larger.
  4. Round fractions to the closest "benchmark" fraction arranged on a number line.
    1. When two or more fractions have the same benchmark, see whether they are on opposite sides of it.
    2. If two or more fractions are on the same side of the benchmark, use rules 1, 2, and 3 above to compare their distances from the benchmark.

Each of these six rules and sub-rules involves at least one presentation frame and two or three practice frames. The whole lesson, including an introduction and close, consists of about 25 frames. This is on the high end of what you should be aiming for. As a rule of thumb, identify at least three sub-tasks or sub-ideas your learners will need to know and practice in order to accomplish the overall outcome.

This takes some careful thinking, but don't continue until you're comfortable you've got about the right scope for your project. If it's too big, you'll get bogged down in repetitive design and development. If it's too small, you won't have enough to really get a feel for the design and development process.

See the Extend section of this module for more information on conducting task analyses.

Feedback on your task analysis?

One important reason for doing a task analysis at this early stage is to ensure that you have scoped out your project appropriately -- not too small, not too large.

Your browser does not support web standards, including Cascading Style Sheets (CSS). This site (and many others) will look better if you upgrade your browser. We recommend Mozilla - it's free, standards-compliant, and fast.