VISION User Guide

Characteristics of a Task

For purposes of performance analysis, a task should have these characteristics:

•A definite beginning and end

•Generally comprised of two or more steps or "elements"

•Normally performed within one specific period of time

•Performance of the task can usually be observed

•Results in a product, completion of a service or decision

Finding the relevant tasks is the most important part of the job analysis.  Tasks are the central part of any performance based training system.  In fact, the tasks represent the performance that the training will be designed to support.  What could be more important than that?

Position of Tasks in the Job Analysis Hierarchy

Steps or "Elements"

The term "step" implies a sequential set of operations, such as those comprising a procedural task. Not all tasks are procedural, and these exceptions are not comprised of sequential steps. For this reason, some instructional analysts use the term "element" rather than "step", because it does not imply sequential operations.

When Performance of a Task Cannot be Observed

There are exceptions. Some tasks involve analytical activities, such as an evaluation. Analysis, or decision making. While performance of these activities is not directly observable, they still comprise a task if the other characteristics are present.

Level of Detail-"Rightsizing" your Tasks

No matter how clear the definition of a task may seem, developing a good task list can be surprisingly tricky.  Often the difficulty arises in trying to determine the right level of detail for a task.    Here are some of the common questions about the level of a task, along with a few suggestions:

1.If two steps (elements) is the minimum size of a task, how many steps (elements) is too many?  

a.There is no hard rule, but 10 to 12 steps/elements is a reasonable target for the upper limit.  There will almost certainly be exceptions.  

2.How big can a step or element be?  What if it contains "substeps"?

a.There are complex tasks, and there are simple tasks.  In general, a step or element can be very small and simple, or big enough to contain substeps.  But if most or all of the steps are complex and contain multiple operations, your task may be too broad.  It might be better to consider each step a subtask.

3.How big can a task be in terms of time; what if it only takes a few minutes to perform?  How about if it takes all day?

a.Again, no firm rules.  But anything that can routinely be done in less than 10 minutes or so might be too small to be a task.  If it takes more than several hours, the task may be too broad.

Checking the Level of a Task

Sometimes a useful way to test the level of detail of a task is to ask:  "Does this task statement make sense as a separate requirement for qualification, where the trainee would perform the task under supervision, and then be "signed off" on the task upon doing it correctly?  

In other words, job qualification is often measured by observing the trainee's ability to perform every task to specified standards.  If your task seems inappropriate as a separate requirement for job qualification, perhaps it is not a task at all.  

Please remember that none of the rules (above) is the final answer to the issue of task levels.   Consider them together, simply as general guidelines.  

When a Task is Big Enough to Contain Substeps

For example, let's say you define the task, "Replace the unit blower motor", which involves the step, "Remove the cabinet front-cover".

Someone could argue that "remove the cabinet front-cover" is really the task since it does include several steps ("unscrew the front panel screws", "gently lift off the face cover", etc), but these steps are quite small and detailed. The first statement, "Replace the unit blower motor" is a more suitable level for a task. So in this case, the steps of the task will contain substeps.

Subtasks

Subtasks are defined as one of the following:

•An alternative method or procedure for performing its parent task

•An alternative set of conditions or instance of performing the task which requires substantially different skill, knowledge and experience

•A significant subset of a complex parent task and meeting all of the criteria for a task. The result of establishing this type of subtask is the classification of the parent task as an "organizer" of a group (at least more than one) of subtasks.

How to Write a Task Statement

To write a task statement, use these guidelines:

•Always begin with an action verb

•Include only one verb per task statement

•The verb should describe something observable or you should be able to observe or measure the outcome of the verb

•the statement should stand on its own

Exceptions to Observable or Measurable Outcomes

Remember, there are exceptions to this point. Not all tasks can be observed as they are being performed. Some tasks are decisions, involve mental analysis or evaluation. Still, you can observe and measure the results, even if the result is simply a decision or conclusion. "Select the best site for a parking structure" is an example of such a task.

Examples of Statements that Stand on Their Own

In other words, the reader should be able to tell exactly what the statement means, even if it appears on a list without reference to a particular job or function.

•Poor Example: "Configure the panel." This task does not stand on its own: What panel? Where?

•Good Example: "Configure the power control panel in the turbine room". This one is much better. There is no doubt or ambiguity about what it means. Two people reading this task statement on a list somewhere would both draw the same conclusion about its intent.

Examples: Good Tasks and Bad Tasks

Examples of  Good Tasks

Examples of Bad Tasks