Friday, March 20, 2009

Conducting a Sucessful Rapid Task Analysis

Rapid Task Analysis Checklist

Thirty years ago I took my first instructional design course. At some point during that class I learned about task analysis. Since then, I have grown to realize that it is a most vital skill. If you get this wrong, learning and performance support spirals out of control. It becomes unwieldy and murky. Of all the skills, in our profession that we need to get right, we certainly need to get this one. Yet, my sense is we need to do better in this area. As a start, we need to figure out how to be more consistent and efficient in our approach. The practice of performance support especially cries out for a Rapid Task Analysis process. After all, how can we ever expect to develop an effective performance support solution, if we haven’t determined what those performances are. Fundamental to any Performance Support strategy is the identification of the performance tasks the strategy needs to support. In addition, since tasks don't stand alone but actually orchestrate into higher work-flow processes, a solid strategy also requires the determination of those processes.
In an earlier blog, I provided a detailed written description of Rapid Task Analysis. Below is a job aid “Checklist” for this process. We’ve also embedded several links to video clips within the checklist to provide added elaboration on critical parts of the process.

1. Prepare for the Task Analysis

Note: For your first few task analysis sessions, you should invite someone to help you during your session. You will find it helpful to have this person help make sure you are successful in conducting your session. You may also benefit by having your helper take notes on a computer while you facilitate the discussion from the whiteboard.

- Develop and validate the preliminary Scope Objective

- Identify primary SMEs (those who should attend the task analysis.)

- Identify backup and secondary SMEs
This can be helpful in case the response is less than 100% with your primary SMEs.

- Schedule date and place for task analysis.
When you reserve the meeting room:

  • Make sure it has at least one large whiteboard.
  • Include at least 30 minutes before and after your task analysis session for setup and cleanup time.
  • Make sure an easel and easel paper (flip chart paper) will be available for the date and time of the session
  • If you are using the voice conferencing, try to choose a room with extra microphones so that people on the phone can hear all the people in the room more clearly.
  • Be sure to send “Meeting Details” email to your coach and other writers who will be observing or helping with your task analysis.

    Note: You might find it helpful to create posters of your agenda and scope, and the definitions of a task, step, process, and concept to post on the walls of the meeting room for participants to reference during the task analysis session.

- Invite SMEs

  • Has a sufficient representation of SMEs confirmed they will attend?
  • Send “Meeting Invitation” email to SMEs: Include the general purpose of your task analysis session and what is expected of them.
  • Send “Meeting Details” email to SMEs: Include meeting date, time, location, and web meeting information (if necessary). Also include the scope and agenda for the task analysis session.

- Review Existing Performance Support Content

  • Review any existing performance support tools relating to your task analysis scope objective. Notice the length of the section or chapter. Were the tasks based on the user’s job performance?
  • Try to create your own list of concepts and tasks for this topic to help guide you through your task analysis session.
  • Generate an outline of tasks and related concepts if possible.
  • Create a handout containing this list. Use this list during your task analysis session to prompt SMEs about tasks they might be forgetting.
  • Email handout(s) to remote participants.
  • Photocopy handout(s) for participants attending the meeting in person.
  • View:

2. Conduct the Task Analysis

The following are things you should consider bringing to the task analysis session.
(Note: All bullets might not apply to your particular task analysis session depending on whether you have participants that are all remote, all attending in person, or a mixture of both.)

  • Easel, Easel pad, Office supplies (scissors, tape, several colors of dry erase pens, ballpoint pens, pad of
    paper), Posters (Scope, Agenda, Definitions of Terms), Your meeting notes and reference material, Copies of appropriate existing TOCs, Handouts (if applicable), Conferencing dial-in and ID numbers,
    List of participants, Web Meeting instructions (if applicable), Snacks for meeting participants, Computer w/mouse, mouse pad, power cord, and Ethernet cable or appropriate wireless equipment), Recording equipment (optional)
  • The following are set-up requirements for the session:
    - Set up computer
    - Tape posters (agenda, definitions of task, concept, etc.)to wall
    - Set up easel & easel pad
    - Rearrange furniture
    - Set up NetMeeting (if applicable)
    - Call into audio conferencing center (if applicable)

- Make introductions and review the agenda

  • Introduce all participants. Thank them for coming.
  • Review the agenda for the meeting (posted for easy viewing during the session).
  • Make sure that remote participants have joined the session and that they can view the whiteboard.

- Introduce and refine, if necessary, the scope objective.

  • Is there consensus?
  • Is the scope objective posted for participants to view at any time?
  • Ask if there are any questions about why you are conducting the task analysis or the goals of the session (both presented by email prior to the meeting).

- Identify Tasks

  • Do SMEs understand what concepts are and that concepts will be identified later?
  • - Chunk and Label Tasks

    • Do SMEs understand the principle of chunking and the benefits of applying this principle?
    • Have participants received a listing of any tasks identified during the activity, Has each participant had an opportunity to add, modify, or delete tasks from the list?
    • Have the tasks been adequately grouped?
    • Have each of the groupings (chunks) been labeled?
    • Is there consensus regarding the labels for the tasks and the processes (chunks or groupings)?
    • Task groups ideally have 7 (plus or minus 2) tasks.
    • Each group of tasks is a business process (similar in scope to a chapter).
    • Keep business and “real world” situations in mind. Help attendees distinguish between describing the product/technology and providing information required to achieve a business goal.
    • The label needs to provide enough detail to convey the relationship used to establish the grouping.

    - Establish Ordered Relationships

    • Is there consensus regarding the order for the processes (chunksor groupings)?
    • Is there consensus regarding the order for the tasks within the processes (chunks or groupings)?
    • Have the unique order requirements for all audiences been addressed?
    • Usually the initial tasks have a typical order in which the customer performs them.
    • The order of some tasks may not matter, but assign them an order anyway.
    • You may have only one group if there are 10 or fewer tasks.

    - Identify Concepts

    • Are the concepts labeled with nonperformance labels?
    • Are the concepts chunked appropriately and assigned to a specific task group?

    3. Follow-up on the Task Analysis Results
    - Review results of the Task Analysis and discuss “next steps.”

    • Are participants leaving with positive feelings about their contribution to the results of the task analysis?
    • Do participants know when to expect a written summary of the results of the task analysis?
    • Do participants understand the amount of time they have to provide their feedback regarding the task analysis results?
    • Tell participants when to expect to receive a written outline of the results of your task analysis session.
    • Explain that you will be contacting them to help you identify the steps in each task and the purpose of that step. You will also be asking for comments about each step.

    Encourage participants to send you their feedback on what went well and what they feel could be improved during your task analysis session, and any suggestions on how to make future task analysis sessions more useful.

    Note: Consider the following tips while you are conducting your task analysis session:
    - You may want to consider having another person take the notes for your first RTA, since you will be writing on the whiteboard for “in person” attendees to view.
    - Monitor the TOC of the related documentation, if any existed, during your task analysis session. If the group gets stuck, use the TOC to prompt SMEs about tasks. You can also check to be sure SMEs cover all the tasks already documented. Be careful about leading the
    SMEs to duplicate the existing TOC.
    - If you get through your entire agenda of identifying, grouping, and labeling tasks and identifying concepts, you can use any time remaining to start filling in the actual steps of each task.

    - Summarize the results and distribute to primary and secondary level SMEs for review and feedback.
    The following is a list of what you should do as soon as possible after your task analysis session:

    • Write your outline of the process(es), tasks, and concepts that the participants identified.
    • Distribute the outline to primary and secondary level SMEs for review.

    - Integrate feedback from the SMEs and distribute for buyoff.
    Once you have obtained buyoff, you are ready to begin documenting the processes as well as producing your performance support solutions. You may find that as you continue this process that your listing of tasks and their groupings will continue to evolve as you uncover additional concepts and tasks. If you have done a thorough task analysis, however, these changes should be few unless there are implementation or business changes (which there likely will be.)

    No comments:

    Post a Comment