In this column I hope to foster communication
and support for 8-bit and ST computer owners... presenting a positive and
directive approach that will help to strengthen the users group base and
encourage the executive element.
|
I wrote last time that the users group is needed now more then ever.
Just because the product isn't being made any more is no reason to stop
supporting those who own it. When people sell an old Atari computer, someone
BUYS an old Atari computer. This person needs all the help and support
they can get. This is where the users group comes in. This is the niche.
|
The users group needs to be more then just a social gathering of fanatic
computer technicians. While it is logical for the code heads to congregate
at the meetings, the meeting must reach beyond those who already know how
to operate the omputer. It must reach the computer owner who wants to use
his computer. There is a large gap between technical computer people and
those who utilize computers. It is important to choose a meeting agenda
that targets the real needs of the members in your group. Also consider
the people you want to become members of your group.
|
The best meeting agenda is the one that works. This may sound largely
ambiguous yet it is true. One style of meeting will not fit all the needs
of every group. The meeting agenda will need to change occasionally to
keep the atmosphere of the meetings from becoming stale. The agenda is
your plan of attack. It is the plan for both the battle and the campaign.
Any group has some agenda, a plan or goal to accomplish. The adage "if
you fail to plan, you plan to fail" is very true when it comes to
a successful meeting. The battle is the monthly meeting. The campaign is
the year of meetings and activities.
|
While I cannot speak for the host of users groups, I can share my experience
in this area. For the past three years I have been planning meetings month
to month. Largely the burden of the meeting agenda was on the president
of our group. The executive members never met together except at the monthly
meeting. We conducted the users group's business at this meeting. We would
make decisions about what to cover in the next meeting at each meeting.
"Well, what do we want to do next month?" This question was the
general plan of attack. It worked well. We managed to reduce our membership
to six diehard Atari enthusiasts who were fanatical over their Atari computers.
The officers did their jobs. The treasurer handled the cash and payments
of the group. The president ran the meetings. The editor produced a meagre
newsletter.
|
The general attitude of the six was to blame the Atari Corporation.
Atari did not seem to be supporting Atari computers. Each assumed this
was what caused our membership to drop. Something had to change. The group
put it to a vote. We would either disband, dispersing the groups assets
among the remaining members, or stay together and do something to increase
the membership. This vote nearly ended this users group. By a narrow margin
(more then half), those who voted to "keep on keeping on" won
the day. That was a year and six months ago. Today this users group grows
steadily. The
membership is increasing by at least one member each month. The members
are getting involved with the group and contributing to some very successful
meetings.
|
What made the difference may not be just one thing. However, the element
of planning was definitely a major factor.
|
I read a very interesting book: HACKERS by Steven Levy. This book provides
a history of the computer revolution. Beginning in the early sixties, Steven
Levy writes about the hackers that shaped this world of computers we have
today. A portion of the book reflects on the role that users groups played
in the early days of home computers. In this section there is an explanation
of what users group meetings were like. In brief, the group opened with
what they called a "mapping session" where members of the group
could share ideas and ask questions. The questioners would be directed
to people who could help them (later in the meeting). This mapping session
set the tone and direction for the meeting. Then there was a DEMO session
in which computer vendors and programmers could show their wares. Finally,
there was the "Random Access" session. The group would break
up in small groups and chat, share programs, and answer questions raised
during the mapping session. I found this information interesting, so I
set up our users group meeting this way.
|
These three parts are necessary components to any users group meeting.
Whatever you call your sessions, these need to be done at some point in
your meeting. Since communications makes the community a community, the
first component is important. Some members need an structured outlet to
share what they are doing with their computers. Others need an opportunity
to ask questions of the entire group. Often it is far easier to ask a group
of people a question then to get the undivided attention of the resident
computer guru. The "mapping" session provides this.
|
The second component provides information. Demonstrations of hardware
components and software programs are interesting and entertaining. They
also provide buyer confidence. If you see how a program really works, you
are more apt to purchase it and use it. A demonstration will give your
members opportunities to see if that particular item is worth their money,
or not.
|
Finally, the last required component is open informal discussion. This
time develops strong alliances and friendships. The casual and informal
communication will help to develop a better group. This is one reason many
people show up to any type of meeting.
|
I began to run the meetings with these three elements. I found that
those who attended were enjoying the meetings more. The visitors that showed
up came back. The non-member Atari computer owners began to re-think their
decision to drop the membership. They got out their chequebooks and paid
the fee. Quite a few ex-members began coming back. I feel that these three
components were meeting a need that all computer owners have. As a result,
the group began to grow.
|
The real growth took more then just a three-part agenda. It took a
concerted effort. I called a meeting. Those invited were the executive
officers of the users group and the SysOp of a local Bulletin Board Service
that featured an All-Atari-Only BBS, the ROVER BBS. The plan for the meeting
was to come up with an overall agenda to provide a directed approach to
Atari support. Three major areas were included. These were the users group
meetings, the newsletter, and the BBS. We began our strategy by listing
the perceived needs of our membership. We came up with monthly topics of
items to cover at each meeting. The plan was to orchestrate these into
the ROVER BBS discussions and the newsletter's articles. The ROVER BBS
would be the hub of our communication during the month. Now that the plan
was in place, we had to work the plan.
|
Meetings have maintained the general structure. Each meeting has some
form of a structured sharing time, demos, and an informal time. Diversity
was provided by encouraging members of the group to participate. A programmer
that is knowledgeable about computers gave us a brief talk on how emulation
works. An electrician shared with us some tips on electrical care and precautions.
A technician will be sharing how to take apart the Atari properly, offering
tips from his experience with electrical components. A programmer will
show how to write a simple "hello world" program in C. The list
goes on. As more are getting involved, the group is getting more interesting.
This is like a snowball rolling downhill.
|
Another factor that infused this users group was what the newsletter
editor did during the year after that fateful vote... but that is another
story.
|
In the future we will cover Newsletters, Membership
(methods of increasing it), Demo (where and how), etc., and I will share
from my own exploits as a users group president; the frustration and the
elation. Stay tuned.
|