Link to Newsletter No. 17.

JAD and FAST

Introduction

We are frequently asked if we train "JAD." There also see posts on the facilitator news group by facilitators asking for information on "JAD." As a result, we thought that we'd clarify distinguishing characteristics of JAD, FAST, and other brands of facilitation.

"JAD"

JAD is an acronym for "Joint Application Design." Chuck Morris and Tony Crawford of IBM developed JAD. They developed JAD from 1977 through 1980. JAD was originally used to design computer systems - screens, reports, etc. Later, Tony Crawford added a process called "JAD Plan" to help develop the scope of work. JAD is an IBM branded technique for facilitation.

FAST

FAST is our technique. FAST was developed in 1985. It grew out of our experience conducting JAD workshops (we were trained by Chuck Morris). FAST originally was an acronym for "Facilitated Application Specification Technique." Quite a mouthful, so we dropped the acronym and it is now just a name. FAST originally focused on workshops to develop computer systems, like JAD, but quickly expanded to include planning, problem-solving, re-engineering, ideation, group analysis, prioritization, and many other purposes. FAST is an MG RUSH branded technique for facilitation. FAST goes far beyond JAD as a technique and set of tools for structured facilitation.

Now for the Misconceptions

The misconceptions about "JAD" are based on its becoming a brand name used to describe a class of product - such as "Kleenex" or "Xerox." The most common incorrect uses that we hear are:

• There is a meeting and someone has labeled the meeting a "JAD session."
• JAD is used only in information technology projects.
• Some of the facilitators who we have trained call the process - "JAD," (even though they really learned the "FAST" technique).

All of these are incorrect. The first is because, unless the meeting is properly facilitated, it is just another meeting. The second is based on the origin of JAD and missing the fact that IBM has used its facilitators for more than information systems design. The third misuse is simply because "JAD" has become the "Keenex" of the industry. JAD, FAST, and most others are based on similar facilitation principles. All can be used in many types of workshops. The workshop agenda and the participants vary.

Here is what differentiates each approach to training in a particular branded technique:

• Who teaches
• How comprehensive the class is
• Which workshop agendas are taught and how they are used
• How complete the preparation is
• Who owns the brand

"Want to Know JAD?"

We include in our FAST class the original JAD agenda that was developed in 1977 (it is now public domain) - plus a lot more. To learn how to facilitate workshops related to developing systems, learn FAST - you will also learn how to facilitate planning, problem solving, re-engineering, group decision-making, group behavior, and much more.

Summary

So, to be correct, instead of calling a workshop "JAD," we suggest calling it a facilitated workshop or structured workshop. If the workshop is related to an IT project and is facilitated using JAD principles, it is fair to call it a "JAD workshop." Generally speaking, however, our FAST technique is more likely the technique being used because it has been modernized, expanded, and refined through broad use.